Benchmarks · sampled 2026-04-29

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

0 105ms 210ms 315ms 420ms
01 gPdf ours
3.8ms
02 PDFShift
95ms
03 DocRaptor (Prince)
180ms
04 Puppeteer (headless)
312ms
05 LaTeX (local)
420ms
Comparisons

gPdf Comparisons

All comparisons
  1. Hosted HTML-to-PDF and template APIvs PDFMonkey

    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.

    Read
  2. PDF SDK (.NET / C#)vs QuestPDF

    gPdf 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.

    Read
  3. Python HTML/CSS-to-PDF libraryvs WeasyPrint

    gPdf 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