pdfrender vs PDFShift
PDFShift is a hosted Chrome-based HTML-to-PDF API; pdfrender is a WeasyPrint-based API with flat subscriptions and an MCP server. Honest comparison.
| PDFShift | hosted HTML→PDF conversion API, headless-Chrome-based rendering, usage-based paid tiers |
|---|---|
| pdfrender | hosted HTML→PDF API + MCP server, WeasyPrint (CSS Paged Media) rendering, free tier + two flat subscriptions |
Both are hosted APIs that turn HTML into PDF over one POST request.
The core difference is the rendering engine: PDFShift renders with headless
Chrome, so a document looks the way a browser would print it and client-side
JavaScript can run; pdfrender renders with WeasyPrint, a dedicated HTML+CSS
print engine implementing CSS Paged Media (@page margin boxes, page
counters), and deliberately executes no JavaScript and fetches no external
resources.
When PDFShift is the better fit
- Your document only reaches its final state after client-side JavaScript runs (charts drawn in JS, SPA-rendered views).
- You want to render existing live web pages by URL rather than submit HTML.
- You need browser-exact fidelity to what Chrome shows.
When pdfrender fits
- Print-first documents — invoices, reports, letters — where CSS Paged Media headers/footers and page numbers matter (guide).
- Predictable flat pricing: free tier of 100 renders/month, Essential €20/mo (10,000) and Scale €80/mo (100,000) — two SKUs, no usage surprises.
- Agent workflows: a built-in MCP server so LLM agents render PDFs as a tool call.
- A deliberately small attack surface: no JS execution, no external fetches — a design choice, not a limitation you pay to remove.
Try pdfrender free — no card, or use the browser tool with no signup at all.