SitePDF · HTML to PDF + Archive API
The journal
Long-form, practical pieces on HTML to PDF conversion, page capture and archives that hold up. No launch hype, no invented case studies.
7 October 2026 · 8 min read
DocuGenerate charges $19 to $199 a month for 500 to 10,000 documents and bills overage instead of stopping. For an advisory firm sending 10,100 documents a month that is about $2,014 a year, or $526 with portal packages moved to a render API.
Read the piece5 October 2026 · 7 min read
Docupilot charges $29 to $699 a month for 100 to 10,000 delivered documents, counts every delivery separately and stops at the limit. For a property software team sending 4,200 deliveries a month that is $4,788 a year, or about $2,076 with statements moved to a render API.
Read the piece2 October 2026 · 7 min read
Anvil charges $0.10 for every PDF generated or form filled over its API, $0.09 to $0.05 prepaid. For an HR platform with 4,000 W-4 and I-9 fills and 10,000 HTML documents a month, that is $13,250 a year on Anvil, or $4,288 with the forms on Anvil and the documents on a render API.
Read the piece30 September 2026 · 8 min read
Docmosis Cloud costs $49 a month for 4,000 pages up to $1,249 for 500,000, metered per page with no overage, and Tornado is a $3,795 to $17,145 perpetual license. For a US lender sending 6,900 documents (24,600 pages) a month, that is $239 to $299 a month, against $49 on a per document render API.
Read the piece29 September 2026 · 7 min read
Foxit sells its PDF SDK by quote only. Its cloud API publishes a price: $1,750 a year for 5,000 credits and $4,500 for 15,000, one credit per operation, no overage. For a staffing platform rendering 14,400 agreements and invoices a year, that is $4,500 before merging or signing, against $288 on a render API.
Read the piece28 September 2026 · 7 min read
HubSpot only makes quote PDFs natively. For a continuing education provider sending 2,000 certificates a month (9,000 in December), apps cost $504 to about €23,000 a year, a render API $288, and the custom code action needs Data Hub Professional from $720 a month.
Read the piece26 September 2026 · 7 min read
ServiceNow's built in PDFGenerationAPI is free and attaches the PDF to the record, but its engine does not run JavaScript, so chart heavy reports come out blank. For an MSP sending 400 service reviews a month, rendering just those documents through an external API costs $288 a year while the built in generator keeps the rest.
Read the piece25 September 2026 · 7 min read
PSPDFKit, now Nutrient, quotes every SDK license privately, but publishes one price list that covers PDF generation: the DWS Processor API at $67 to $399 a month billed yearly, half a credit per HTML to PDF conversion. For a payroll platform producing 8,000 statements a month that is $2,964 a year rendered in one step and $6,069.60 with a merge step, because the API counts operations, not documents.
Read the piece21 September 2026 · 8 min read
The same 600 PDFs a month cost $0 to $2,448 a year in Power Automate, and the biggest line is usually the Microsoft license, not the converter. Encodian, Plumsail and Nutrient are Standard connectors; the HTTP action, Adobe and Cloudmersive are Premium, so a button flow with 12 runners needs 12 seats. Changing the trigger to automated cuts that to one.
Read the piece8 September 2026 · 8 min read
Bannerbear prices images clearly and refuses to price PDFs at all, saying only that they "use more credits". For document workloads that gap is the whole decision. Here is what four competitors publish instead, the second meter hiding in Bannerbear plans, and how to tell whether switching pays back.
Read the piece17 August 2026 · 8 min read
The Syncfusion Community License has four conditions, not one, and the funding test catches funded startups that assume revenue is the only bar. Here is the exact wording, what happens when you outgrow it, and how the free tiers from QuestPDF, iText, PDFsharp and PDFBox differ in what they let you ship.
Read the piece11 August 2026 · 8 min read
Apache PDFBox has no HTML parser and no CSS engine, so it cannot convert HTML to PDF, and no version of it will. Here is what PDFBox is genuinely good at, why the gap exists, and which Java library to reach for when your document starts as markup.
Read the piece20 October 2026 · 9 min read
A .NET PDF library is one of the few dependencies where the license, not the feature list, decides whether you can ship. iText is AGPL unless you buy a quote-only commercial license. QuestPDF is free under 1M USD revenue, then 1,999 USD. IronPDF starts at 999 USD. PDFsharp is MIT with no conditions at all. Here is what each one actually costs a closed source commercial application, read from the vendors own sites on 9 August 2026.
Read the piece3 August 2026 · 8 min read
Your Django template looks perfect in the browser and the PDF comes out with a blank rectangle where the chart should be. That is not a bug and no configuration flag will fix it: WeasyPrint runs no JavaScript at all, deliberately. Here is what the documentation actually says, why the decision was made, the four ways to get a chart into the PDF anyway, and the point at which you should stop fighting it.
Read the piece3 August 2026 · 8 min read
Blank PDFs, text sliced at a page boundary, blurry output, vanishing backgrounds, and an error the moment you try to run it in Node. Almost every html2pdf.js complaint traces back to one design decision: it rasterizes your page into an image rather than converting it. Here is what that causes and what to do about each symptom.
Read the piece1 August 2026 · 9 min read
An HTML to PDF API is almost always a data processor under GDPR, which makes a written DPA, a sub-processor list, a lawful transfer basis and a stated retention period mandatory rather than optional. Here is where the data actually goes, what the Data Privacy Framework status is in August 2026, and the seven questions to put to a vendor before you integrate.
Read the piece31 July 2026 · 9 min read
Your public website is a retail communication, so the rules that cover email cover it too. Retention is three years, the first two in an easily accessible place, and since the 2022 amendments WORM storage is no longer the only compliant format. Here is what the rule text actually says and where firms fail an exam on it.
Read the piece24 July 2026 · 8 min read
Zapier, Make and n8n move data between apps; none of them turn that data into a document. There are three ways to add the missing step, they suit different teams, and the one you pick decides how much of the work lands on an engineer. Here is the honest comparison, plus the four things that break in every route.
Read the piece19 July 2026 · 9 min read
The page looks perfect in Chrome and the PDF comes out looking like 1996: no colors, no layout, everything stacked in one column. CSS loss is the single most reported HTML to PDF problem, and it has six distinct causes with six different fixes. Here is how to tell which one you have hit.
Read the piece19 July 2026 · 8 min read
Your logo is missing, the product photos are empty boxes, and the chart image never appears. Images fail in HTML to PDF for four specific reasons, and lazy loading is the one almost nobody expects. Here is how to diagnose each and the fixes that make images render every time.
Read the piece24 July 2026 · 8 min read
Most teams go shopping for a renderer first. That is the wrong first question. There are four ways a document gets generated automatically, they fail in different ways, and picking the pattern before the vendor is what keeps a document pipeline from quietly dropping files on its first busy day.
Read the piece19 July 2026 · 9 min read
Someone on your team rebuilds the same report by hand every Monday. Automating it takes four moving parts: a scheduler, a report URL with an explicit date range, a render call that waits for the charts, and delivery that stores what it sent. Here is how each should work, and the failures that make automated reports look homemade.
Read the piece19 July 2026 · 9 min read
A PDF renderer is a browser running inside your network, loading HTML that a user influenced. That is the exact shape of a server-side request forgery bug, and PDF generators have been a reliable place to find one for years. Here are the two attacks, the controls that stop them, and the eight questions that decide a vendor security review.
Read the piece19 July 2026 · 8 min read
You set a brand font, it looks perfect in the browser, and the PDF comes out in Times New Roman. Web fonts are one of the most common HTML to PDF failures, and it is almost always a timing or reachability problem, not a bug. Here is why the font falls back and the three fixes that make it embed every time.
Read the piece19 July 2026 · 9 min read
A 200-row report renders fine, a 20,000-row one times out or kills the browser with an out-of-memory error. Large HTML to PDF jobs fail for a handful of specific reasons, and each has a clean fix. Here is why big pages time out, why the renderer crashes, and how to render heavy reports reliably.
Read the piece19 July 2026 · 8 min read
A header that only shows on page one, a footer that overlaps the content, page numbers that will not appear: margins and running headers are the second most common HTML to PDF headache after page breaks. Here is the CSS that sets margins and the two reliable ways to get a header and footer that repeat on every page.
Read the piece19 July 2026 · 8 min read
A US invoice that comes out A4, a wide financial table crammed into portrait, a page size that changes depending on who opens the file: page size and orientation trip up almost every HTML to PDF setup. Here is how to pin A4 or Letter, switch to landscape for wide content, and why the size sometimes gets ignored.
Read the piece19 July 2026 · 8 min read
A row cut in half, a card sliced across two pages, a heading stranded at the bottom: page breaks are the most common complaint about HTML to PDF. Here is the CSS that controls them, why it sometimes gets ignored, and how to get clean breaks on invoices, reports and tables.
Read the piece19 July 2026 · 8 min read
An empty box where the chart should be is the classic HTML to PDF bug: the PDF was captured before the JavaScript finished. Here is why it happens, the wait signals that actually work (and the one that does not), and how to make dashboards and font-heavy pages render every time.
Read the piece19 July 2026 · 9 min read
Go has no built in HTML to PDF, and half the packages people find are archived. Here is the current map: chromedp for real Chromium output, why gofpdf and the wkhtmltopdf wrappers are dead ends, and when to reach for Gotenberg or a hosted API instead, with code.
Read the piece13 October 2026 · 9 min read
Two very different jobs get called "invoice PDF API": fetching the PDF a billing platform already made, and generating your own from an HTML template. Here is when to use each, with the Stripe and QuickBooks endpoints and the render call, plus how to keep a record every finance team eventually needs.
Read the piece14 July 2026 · 9 min read
Printing is not screenshotting. The renderer swaps your stylesheet, drops your backgrounds, paginates a layout built to scroll, and often fires before your content lands.
Read the piece6 July 2026 · 9 min read
The library is free until you own the headless Chrome fleet behind it. Here is the real bill: memory leaks, font drift, on-call pages, and the point where an API wins.
Read the pieceGet started
A pixel perfect PDF and a dated copy of the page from the same request. Plans from $49 a month, half price billed yearly.
HTML to PDF, in your browser
One PDF free, then $24 a month billed yearly