Measured, not marketed.
1-page A4 invoice, 12 line items, QR + logo. Median of 1000 PDF generations. Lower is better.
gPdf is not an HTML-to-PDF engine. These numbers compare structured document generation for invoices, labels, and API-generated PDFs — not browser-rendered web pages.
Methodology: 1-page A4 invoice · 12 line items · 1 QR + 1 logo · 1K invocations · median (p50) and p99 reported. Sampled 2026-04-29 from a workstation in EU-WEST. PDFShift, DocRaptor, Puppeteer and LaTeX numbers are reproduced from each vendor's published quickstart sample with the same input — re-run on your own workload before deciding. Read the head-to-head comparisons
gPdf Comparisons
gPdf vs PDFMonkey: JSON-native edge PDF API vs HTML templates
PDFMonkey is strong for HTML/CSS templates and no-code automation. gPdf is stronger for structured invoices, labels, e-invoices, edge latency, and high-volume pricing.
ReadgPdf vs QuestPDF for .NET document generation
QuestPDF is an excellent C# PDF library. gPdf is a hosted edge API. Compare licensing, runtime ownership, template workflow, compliance, barcodes, and when each product is the better fit.
ReadgPdf vs WeasyPrint: visual PDF design-to-delivery vs Python HTML-to-PDF
WeasyPrint is an excellent open-source Python HTML/CSS-to-PDF library. gPdf adds Studio visual design, reusable templates, edge delivery, and $5 / 100K-page API pricing.
Read