PagedPDF vs DocRaptor
Checked: prices and features from docraptor.com on 2026-11-11. DocRaptor tested the same day with its public test key, on its default pipeline, and PagedPDF with the keyless demo.
Both are APIs that turn HTML into a PDF. The main difference is the engine. DocRaptor runs Prince, a commercial renderer built for print. PagedPDF runs current Chrome, so a document prints the way it looks in a browser. That one choice explains most of the rows below, including the price.
This page is written by PagedPDF, so check anything that matters to you against DocRaptor's own pricing page.
Cost per document
Monthly prices, and the price divided by the documents included:
| Documents a month | DocRaptor plan | Each | PagedPDF plan | Each |
|---|---|---|---|---|
| 5 | Free, $0 | |||
| 50 | Free, $0 | |||
| 125 | Basic, $15 | $0.12 | ||
| 325 | Professional, $29 | $0.089 | ||
| 1,250 | Premium, $75 | $0.06 | ||
| 2,000 | Starter, $15 | $0.0075 | ||
| 5,000 | Max, $149 | $0.030 | ||
| 10,000 | Growth, $49 | $0.0049 | ||
| 15,000 | Bronze, $399 | $0.027 | ||
| 40,000 | Silver, $1,000 | $0.025 | ||
| 50,000 | Scale, $149 | $0.0030 |
The same $15 buys 125 documents from DocRaptor and 2,000 from PagedPDF.
What a month costs at a few volumes, taking the cheapest route on each, overage included:
| Documents a month | DocRaptor | PagedPDF |
|---|---|---|
| 500 | $44.75 (Professional plus 175 extra at 9¢) | $15 |
| 2,000 | $120 (Premium plus 750 extra at 6¢) | $15 |
| 10,000 | $299 (Max plus 5,000 extra at 3¢) | $49 |
| 50,000 | $1,250 (Silver plus 10,000 extra at 2.5¢) | $149 |
Going over your limit
DocRaptor keeps making documents and bills each extra one at your plan's rate: 12¢ on Basic, 9¢ on Professional, 6¢ on Premium and 3¢ on Max. Your documents never stop, and the bill can grow.
PagedPDF stops instead. The API returns 429 quota_exceeded until the 1st of the next month or until you upgrade, and there's never an overage charge. Your bill can't grow, and your documents can stop.
Pick the failure you'd rather have.
The same invoice through both
We sent one HTML document to each: three boxes in a flex row, three in a CSS grid, a line of emoji and Chinese, Japanese and Korean text, and a 60-row table of three-line rows with a CSS page number footer. Neither request set any options.
| DocRaptor (Prince) | PagedPDF (Chrome) | |
|---|---|---|
| Table header on every page | Yes | Yes |
| Table rows | Split across pages, until we added tr { break-inside: avoid } |
Kept whole |
"Page 1 of 5" from CSS @page |
Yes | Yes |
| Flexbox | Side by side | Side by side |
| CSS grid | Stacked vertically | Laid out |
| Emoji and CJK text | Printed | Printed |
| Background colours | Printed | Printed |
| Scripts | Off unless you send "javascript": true |
Off unless you send "javascript": true |
Three things to know before you move a template to DocRaptor. Rows split across pages unless your CSS stops them, which is also what Chrome does on its own. PagedPDF adds that rule for you. Our grid boxes came out stacked, so a layout built on CSS grid needs rewriting with flexbox or tables. And scripts need older syntax. With "javascript": true, DocRaptor rejected a script that used an arrow function, with a 422 and this message:
[Javascript Error] SyntaxError: Unexpected token '>'
A template literal failed the same way. Rewritten with function and string concatenation, the same script ran. DocRaptor has older and newer engine settings (pipeline), and we only tested the default. PagedPDF runs scripts in current Chrome, so modern syntax is fine.
Going the other way, Prince does things Chrome can't. See the next section.
Where DocRaptor is the better choice
- Print features. Prince supports more of CSS Paged Media than Chrome: footnotes, cross-references that print a page number, and running headers taken from the document's headings. Chrome has no
target-counter, so a table of contents with page numbers can't be done in CSS on PagedPDF. - Accessible PDFs. DocRaptor says its tagging helps meet WCAG 2.0, Section 508 and ISO 14289 (PDF/UA).
- Excel output. It also makes XLS and XLSX files.
- Compliance paperwork. DocRaptor says it's SOC2 and HIPAA compliant and guarantees 99.99% uptime. PagedPDF is a new service with neither.
- Long jobs. Asynchronous documents get up to 600 seconds. PagedPDF stops a render at 30 seconds.
- Hosted documents. DocRaptor can host the PDF at a URL for you. PagedPDF returns the file and keeps nothing.
- Free testing. Test documents are unlimited and free, with a watermark.
If you need any of those, use DocRaptor.
Where PagedPDF is the better choice
- Price. A third to an eighth of the monthly cost at the volumes above.
- It prints what your browser shows. If the template already looks right in Chrome's print preview, including grid layouts and modern JavaScript, it prints the same way here.
- No surprise bill. The API stops at your limit instead of charging overage.
- It tells you what went wrong. Every response lists the fonts and images that failed to load, in an
X-PagedPDF-Warningsheader.
The same request on each
DocRaptor, run as written with its public test key:
curl https://YOUR_API_KEY_HERE@api.docraptor.com/docs \
-H "Content-Type: application/json" \
-d '{"test": true, "type": "pdf", "document_content": "<h1>Invoice 1042</h1>"}' \
-o invoice.pdf
Page numbers on DocRaptor go in your CSS, as an @page rule with counter(page) and counter(pages).
PagedPDF:
curl https://api.pagedpdf.com/v1/pdf \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"html": "<h1>Invoice 1042</h1>", "footer": "Page {page} of {pages}"}' \
-o invoice.pdf