HTML to PDF API that gets the fonts right
Send an HTML string or a URL, get a pixel-perfect PDF back — with correct fonts, including CJK (Japanese, Chinese, Korean) and emoji that other APIs mangle. No file uploads. Flat, predictable pricing.
Fonts that actually render
The #1 complaint about HTML→PDF APIs is broken fonts and ignored web fonts. We wait for web fonts to load and ship CJK + emoji font coverage on the render servers.
Made for code, not uploads
Your app generates HTML — it doesn't have a file. Send a raw html string or a url and get the PDF inline. No temp files, no multipart dance.
Flat, predictable pricing
No "1 credit per 5 MB" surprises, no enterprise print-engine premium. A flat number of conversions per month you can actually forecast.
Why teams switch to us
| Capability | SayPDF | Typical Chromium API | Prince-based API |
|---|---|---|---|
| Send raw HTML string (no file) | Yes | Varies | Yes |
| CJK + emoji fonts out of the box | Yes | Often broken | Varies |
| Stream PDF bytes back (no polling) | Yes | Varies | Yes |
| Flat, forecastable pricing | Yes | Credit/MB | Premium |
| Print control (margins, headers, page numbers) | Yes | Basic | Yes |
Built for the documents your app generates
Invoices & receipts
Including multi-currency and CJK layouts.
Reports & dashboards
Long tables with repeating headers.
Tickets & certificates
Pixel-perfect, on-brand output.
Contracts & statements
Consistent pagination and margins.
Flat, predictable pricing
Priced per render — not per megabyte, not per enterprise tier. All plans include every feature: CJK/emoji fonts, render options, inline & URL input, JSON output.
Save ~17% on annual billing (2 months free). A “render” is one HTML→PDF (or other to-PDF) conversion. OCR/scanned-document conversions are billed separately — see OCR pricing.
Start rendering in 30 seconds
Free API key, no credit card. One POST and you have a PDF.