Compare · wkhtmltopdf
The modern wkhtmltopdf alternative
wkhtmltopdf was archived in 2023. Its last release predates modern CSS, and it ships with an unpatched critical vulnerability (CVE-2022-35583) — its own maintainers warn against running it on untrusted HTML.
If you still generate PDFs with it, you're on a dead, insecure dependency built on a 2014-era WebKit fork. This API renders on current headless Chrome — the same engine your users' browsers run — so flexbox, grid, web fonts and print styles simply work.
01Rendral vs wkhtmltopdf
wkhtmltopdf pricing at a glance: Free, but unmaintained since 2023.
| Feature | wkhtmltopdf | Rendral |
|---|---|---|
| Rendering engine | Qt WebKit fork (~2014) | Headless Chrome (current) |
| Maintenance | Archived | Actively maintained |
| Security | Unpatched CVE-2022-35583 | Sandboxed, isolated renders |
| Modern CSS (grid/flex) | Partial / broken | Full |
| You run the infra | Yes — install & patch | No — hosted API |
02Why teams switch
- Current Chrome rendering — the CSS your designers actually write.
- No archived binary and no CVE to explain to your security team.
- Nothing to install, sandbox, or keep alive on your servers.
- Screenshots, OG images, merge and watermark on the same key.
Frequently asked
Is wkhtmltopdf still maintained?
No. The project was archived in 2023; the last stable release is from 2020 and it carries an unpatched critical CVE. It is not recommended for new projects or untrusted input.
Can I keep my existing HTML templates?
Yes. Send the same HTML you already produce; modern Chrome rendering typically improves fidelity versus wkhtmltopdf's dated engine.
How do I migrate?
Replace the wkhtmltopdf CLI/library call with a single POST to /api/v1/pdf containing your HTML. No binaries, no system dependencies.
A free tier, five endpoints, and SDKs for Node and Python.