Compare
PDFops vs the incumbents
Side-by-side against the three hosted PDF APIs most often considered for template-driven document generation — DocRaptor, PDFShift, PDFMonkey. Every pricing number, substrate claim, and feature-gap is cited to the vendor's own pricing page or docs as of 2026-05-19.
The shared wedge
All three incumbents render HTML to PDF. DocRaptor uses PrinceXML; PDFShift uses headless Chromium; PDFMonkey uses HTML + Liquid templating piped through Chromium. None of them accepts an existing PDF + a JSON of field values and returns the filled PDF.
PDFops does the opposite operation. It
takes a PDF you authored (in Acrobat, Mac Preview,
LibreOffice Draw, or pdftk) with AcroForm
fields baked in, plus a JSON map of field-name → value,
and returns the filled PDF. Plus /api/merge
for combining N PDFs into one. That's it — two operations,
neither of which any incumbent supports as a primitive.
The "10× cheaper" framing isn't "we render HTML cheaper than they do" — it's "we don't need to render HTML at all for the template-fill case, so the per-document cost falls to V8-isolate edge-runtime economics."
At a glance
| PDFops | DocRaptor | PDFShift | PDFMonkey | |
|---|---|---|---|---|
| Primitive | AcroForm fill + merge | HTML → PDF (Prince 15.1) | HTML → PDF (Chromium) | HTML + Liquid → PDF (Chromium) |
| Fill an existing PDF | Yes | No | No | No (emits empty forms only) |
| Merge PDFs | Yes | No | No | No |
| Free tier | 100 req/IP/month, no signup | 5 test docs/mo, watermarked | 50 credits/mo, 2 MB cap | 20 docs/mo, 1-day retention |
| Lowest paid tier | — | $15/mo (125 docs, 12¢/doc) | $9/mo Startup | €5/mo (300 docs, ~€0.017/doc) |
| Best per-doc rate | Free during beta | 2.5¢ at $1,000/mo Silver | $0.0040 at $99/mo Business | €0.005 at €300/mo Premium |
| Hosting | Vercel Edge (global, V8) | AWS (no region selection) | Chromium containers (single region) | Chromium pipeline + S3 |
| Last public update | Continuously | Sep 2023 | SDKs archived Dec 2020 | May 2025 (Engine v5) |
Which comparison should you read?
- If you're paying for DocRaptor or shopping for an HTML-to-PDF alternative: read PDFops vs DocRaptor. The killer specific is their dead changelog — no entry since September 2023, still on Prince 15.1 while Prince 16 has been out for 7+ months.
- If you're using PDFShift or evaluating Chromium-based PDF APIs: read PDFops vs PDFShift. Credit-system pricing breakdown ($0.0040–$0.0096/credit, $0.03 overage); 50-doc free tier; the archived-SDK signal (their PHP/Node/Python repos haven't been touched since December 2020).
- If you're on PDFMonkey or evaluating dashboard-led template editors: read PDFops vs PDFMonkey. Important correction inside: their "PDF Forms" feature emits empty fillable AcroForms; it doesn't fill them. The migration story is "rebuild your HTML+Liquid templates as AcroForm PDFs," not "rename your fields."
Deep-dives
-
PDFops vs DocRaptor
HTML→PDF on PrinceXML 15.1. Generation-only API — no fill-form, no merge. $15/mo (125 docs, 12¢/doc) → $1,000/mo (40k docs, 2.5¢/doc). Dead public changelog since Sep 2023.
-
PDFops vs PDFShift
HTML→PDF on Chromium. Credit-based pricing ($0.0040–$0.0096) with $0.03/credit overage. 50-doc/mo free tier. ~1.5s avg render. SDK repos archived since Dec 2020.
-
PDFops vs PDFMonkey
HTML + Liquid templating with a dashboard editor. €5/mo (300 docs) → €300/mo (60k docs); overage only above €60/mo. Their "PDF Forms" feature emits empty AcroForms — different operation from PDFops's fill.
How each comparison is structured
Each /vs/<vendor> page leads with an honest framing block — when the incumbent still fits better (HTML rendering, rich CSS, templated layouts), then when PDFops fits (fixed-layout AcroForm templates, merge-heavy flows, edge-deployed callers). The side-by-side table covers primitive, pricing, hosting substrate, free tier, SLA, and best-for. A migration-shaped curl example shows what the move actually looks like. The FAQ closes with 5 entries each: pricing math, primitive-fit, migration story, SLA posture, and one vendor-specific question.
Want the API contract before deciding? See the docs section — full reference for /api/fill-form (5 supported field types, 14-row error code table), /api/merge (multipart ordering semantics, page-level page-copy behavior), and /api/waitlist.
← PDFops home · Docs · Use Cases · Blog