Guides and comparisons
Every content page on the site, on one page: what the field charges, which engine renders your page correctly, and how to migrate off the archived tools. The API reference lives on the docs page.
Guides
- Free HTML to PDF APIs compared: nine free tiers side by side: volume, resets, and the catch each vendor buries.
- Best HTML to PDF APIs compared: thirteen APIs, engines disclosed or not, prices stated, catches printed.
- HTML to PDF API: the head page: engine, pricing, and quick start on one page.
- HTML to PDF without losing formatting: why converted pages break, and the browser-rendering fixes that keep layout, fonts, and backgrounds intact.
- Open source HTML to PDF APIs, compared: Gotenberg, self-run Playwright, and hosted routes, with the hosted prices one click away.
- wkhtmltopdf alternatives: the archived tool mapped flag by flag to headless Chromium.
- wkhtmltopdf alternative for Python: swap pdfkit for Playwright's page.pdf(), option by option.
- wkhtmltopdf alternative for PHP: swap snappy for Browsershot or headless Chromium.
- wkhtmltopdf alternative for C#: swap DinkToPdf for Playwright for .NET.
- wkhtmltopdf alternative for Java: swap the wkhtmltopdf wrappers and openhtmltopdf for Playwright for Java.
- wkhtmltopdf alternative for Go: swap go-wkhtmltopdf for chromedp or a Gotenberg container.
Comparisons
- Gotenberg vs Puppeteer: same Chromium output, so the choice is a REST container or a Node library: ops, control, ownership.
- Gotenberg vs WeasyPrint: browser rendering for live web pages against print-CSS layout for authored documents.
- Gotenberg vs LibreOffice: Chromium for HTML pages against LibreOffice import filters for office documents.
- Puppeteer vs wkhtmltopdf: the archived WebKit binary against a maintained Chromium, with the flag-by-flag migration.
- webcapture vs PDFShift: one render per document against one credit per 5Mb, with formats, timeouts, and the async contract printed.
- The HTML to PDF field, compared honestly: eight vendors on fourteen capability rows, each cell read from the vendor's own docs, with webcapture's own gaps named.
Going deeper
- The automations hub: one worked integration page per platform (n8n, Zapier, Make, Bubble, Clay, FlowMattic, Lovable, Base44), every sample the same real POST /v1/convert call written in the platform's own step format.
- The recipes hub: fourteen complete programs for the same call in curl, Python, Node, and TypeScript, one runnable file per page with the Bearer header on both the convert POST and the download GET.
- Migrate from PDFShift: the drop-in switchover manual for their request shape, one parameter at a time.
- The free URL to PDF tool: run one render in the browser before you wire any integration.