How to Automate PDF Invoice Generation in Your SaaS (Without the Headaches)

At some point in every SaaS, you hit the invoice wall. Your users want a PDF. Not a print-this-page link. Not a screenshot. A proper, downloadable, email-attachable PDF invoice with your branding on it.

This is the story of how that "quick feature" turns into a week of suffering — and how to avoid it entirely.

The naive path (and why it hurts)

Most developers start with one of these:

1. A PDF library (PDFKit, jsPDF, pdfmake) — you build the document in code using a proprietary layout API. Pixel-pushing hell. No designer can touch it. Tables are painful.
2. Puppeteer — spin up a headless browser, load your HTML, call page.pdf(). Works great until you deploy to AWS Lambda and Chromium is 300 MB and everything breaks.
3. A SaaS PDF service — fine until you see $0.015/page, $49/month minimums, and a sales call to go over your "usage tier."

Every option has a cost: either your time or your money. Usually both.

The right architecture for invoice PDF generation

Here's the pattern that actually scales without drama:

1. Keep your invoice template as HTML (React, Jinja, Handlebars, whatever your stack uses).
2. Server-side render it with real data when a user requests a PDF.
3. POST the HTML to an API. Get a PDF URL back.
4. Either redirect the user to that URL or stream it into your own storage (S3, Cloudflare R2, etc.).

Step 3 is where htmltopdfconverter.com.au lives. One endpoint. Auth via API key. No SDK to install.

// Node.js example
const html = renderInvoiceTemplate(invoiceData);

const response = await fetch(
  'https://htmltopdfconverter.com.au/api/programmatic/pdf/generate',
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${process.env.PDF_API_KEY}`,
      'Content-Type': 'text/html',
    },
    body: html,
  }
);

const { pdfs } = await response.json();
const pdfUrl = pdfs[0].url;

// Store it, email it, redirect to it — you decide.

What you actually get for $5/year

• Unlimited PDF conversions (subject to rate limit — 10 req/min, more than enough for invoice generation)
• Real Chromium rendering — CSS, fonts, images, backgrounds, all of it
• Up to 10 files per request, 50 MB per file
• No per-page charges. No tiers. No overage fees.
• Actual support — not a chatbot, not a ticket queue that goes cold
• We're open to feature requests. If you need something specific, ask.

$5 AUD per year is the cheapest option available for a managed HTML-to-PDF API. Most competitors charge more per page than we charge per year.

Tips for great invoice PDFs

• Use @media print in your CSS to hide nav bars, buttons, and anything that doesn't belong in a document.
• Set an explicit page size and margins via @page.
• Use break-inside: avoid on your totals block to prevent it splitting across pages.
• Inline critical CSS or use a single <style> block — don't rely on external stylesheets the renderer might not fetch.
• Test with your longest possible invoice (many line items, long descriptions) before going live.

Ship it

Invoice PDF generation is not a differentiator for your SaaS. It's a commodity feature that users expect. Don't spend a week on it. Sign up, generate an API key, and have your first PDF in production today. The docs cover everything — request format, response shape, error codes, and examples in Node, Python, and PHP.

FAQ