Alternative to wkhtmltopdf

wkhtmltopdf vs TemplateFox

wkhtmltopdf served the community well, but the project is no longer maintained. If you're looking for an alternative with a visual template editor, a REST API, and PDF/A compliance — here's how TemplateFox compares.

wkhtmltopdf logoAbout wkhtmltopdf

What is wkhtmltopdf?

wkhtmltopdf is a command-line tool that converts HTML pages into PDF files. Released in 2008 by Jakob Truelsen, it wraps the Qt WebKit rendering engine and runs as a standalone binary on Linux, macOS and Windows. For years, it was the go-to open-source option for developers who needed to generate PDFs from HTML without running a full browser.

It was built for developers. You install the binary, feed it an HTML file or a URL, and get a PDF. There's no editor, no API server, no template management — just a CLI that you wire into your stack through a language wrapper (pdfkit for Ruby, pdfkit for Python, wkhtmltopdf-binary for Node, and so on).

The project was archived on GitHub in 2023. The last release (0.12.6) dates from January 2020, and the underlying WebKit fork is from 2016. No new features, no security patches, and no bug fixes are planned. A few community forks exist, but none have reached the maturity or ecosystem size of the original.

Pricing

wkhtmltopdf is free and open source under LGPLv3 — no license fee, no usage limits. The real cost is operational: you host the binary yourself, package it with the right fonts and dependencies, and maintain it over time. For a few PDFs per day, that's fine. For production workloads, engineering time spent on setup, deploys, monitoring and patching typically exceeds the cost of a managed API.

Feature comparison

An honest, section-by-section look at what each tool does and doesn't do.

1. Project health & rendering

wkhtmltopdf
TemplateFox
Project status
Archived (last release Jan 2020)
Actively maintained
Rendering engine
Qt WebKit fork from 2016
Modern CSS engine
CSS Flexbox & Grid
Not supported
Supported
PDF/A, PDF/X, PDF/UA
Not supported
PDF/A-1b, A-2b, A-3b, PDF/X, PDF/UA

wkhtmltopdf served the open-source community well, but its rendering engine dates from 2016 — no Flexbox, no Grid, and no archival PDF standards. For new templates or compliance-bound documents (PDF/A for archiving, PDF/UA for accessibility), that's a hard ceiling. TemplateFox uses a maintained engine and supports the main PDF standards natively.

2. Developer experience

wkhtmltopdf
TemplateFox
Setup
Install binary + system fonts + Xvfb
API key, nothing to install
Template editor
None (raw HTML files)
Visual drag-and-drop editor
API
CLI (requires wrapper)
REST API + SDKs (7 languages)
No-code platforms
None
Zapier, Make, n8n, Airtable, Bubble

Integrating wkhtmltopdf into a real project means a language wrapper, a binary packaged with the right fonts, and often Xvfb to render without a display. That's typically a few days of engineering up front — and the same work again at every OS upgrade. TemplateFox calls out to a REST API (or an official SDK), and non-developers can edit templates visually without touching code.

3. Features & data

wkhtmltopdf
TemplateFox
Dynamic data binding
Manual (templating library)
Variables, loops, conditions
Multi-page tables
Manual CSS tricks
Automatic page breaks
Barcodes & QR codes
External libraries required
Built-in (Code128, EAN-13, QR…)
Headers & footers
Supported via CLI flags
Supported via editor

Both tools cover the basics of PDF generation. The difference is the distance to the result: with wkhtmltopdf, data binding, barcodes, and multi-page layouts are wired by hand in the template. With TemplateFox, these primitives are available directly in the editor.

4. Hosting, compliance & pricing

wkhtmltopdf
TemplateFox
Self-hosted
Yes (only option)
No (managed cloud)
Data handling
Your infrastructure, your rules
GDPR principles, privacy by design
Maintenance
You own it (OS upgrades, fonts, patches)
Handled by us
Cost
Free OSS + your engineering time
Free tier (60/mo), then paid

This is where wkhtmltopdf keeps a real edge: if your data can't leave your servers, a self-hosted tool is the right answer. For everything else, TemplateFox is a managed service built on GDPR principles (data minimization, right to erasure, 72-hour breach notification). The subscription cost is usually lower than the engineering time saved on maintaining a binary in production.

Ready to move past an archived project?

wkhtmltopdf is no longer maintained. Switch to an actively developed API with modern CSS, PDF/A, and a visual editor. No credit card, 60 free PDFs per month.

Try TemplateFox for free

When it might be time to switch

Two honest answers, depending on what you're optimizing for.

Switch to TemplateFox

Signs you'll gain from moving

  • Your templates need CSS Flexbox, Grid, or other modern CSS that wkhtmltopdf can't render
  • You need PDF/A, PDF/X or PDF/UA output for compliance or archival
  • Maintaining the wkhtmltopdf binary (fonts, Xvfb, OS patches) is eating engineering time
  • Non-technical teammates need to edit templates without touching code
  • You want to plug PDF generation into Zapier, Make, n8n or Airtable
  • Future security patches matter to your organization

Browse 30+ ready-made templates →

Stay with wkhtmltopdf

When it can still be the right call

  • Self-hosting is a hard requirement — data must never leave your servers
  • You're happy with your current setup and templates render fine as-is
  • You don't need modern CSS, PDF/A, or new features
  • You have in-house expertise to maintain the binary long-term

Open source is a real advantage when you need full control over your infrastructure. The tradeoff is maintenance, and an aging rendering engine that won't catch up.

Used by100+Developers

Indie devs and companies shipping PDFs in production.

Uptime99.997%Last 90 days

Measured live on our public status page.

Rendered50k+PDFs generated

Growing every day on a scalable infrastructure.

Frequently asked questions

Is wkhtmltopdf still maintained?

No. The project was archived on GitHub in 2023. The last release (0.12.6) dates from January 2020. There are no planned updates, security patches, or bug fixes.

What are the main limitations of wkhtmltopdf?

wkhtmltopdf relies on a legacy WebKit engine that doesn't support modern CSS features like Flexbox or Grid. It also has no built-in API, no template management, and no support for PDF standards like PDF/A. Setting it up on servers — especially in containers — can be tricky because of its binary dependencies.

How does TemplateFox compare?

TemplateFox is a cloud-based PDF generation API. You design templates in a visual editor, then generate PDFs via REST API or no-code platforms. It uses a modern rendering engine with full CSS support, and can output PDFs in PDF/A, PDF/X, and PDF/UA formats.

Can I reuse my wkhtmltopdf HTML templates?

Yes. TemplateFox templates are HTML and CSS, so your existing markup is a good starting point. You can import it into the template editor and update the layout to use modern CSS — no more float workarounds.

What if I need to self-host?

TemplateFox is a managed service — you don't run any infrastructure. If self-hosting is a hard requirement for your organization, wkhtmltopdf (or a fork) may still be the right choice. For most teams, the tradeoff of not managing servers is worth it.

Does TemplateFox support PDF/A?

Yes. You can generate PDF/A-1b, PDF/A-2b, PDF/A-3b, PDF/X, and PDF/UA compliant documents — something wkhtmltopdf never supported. Just pass the desired standard as a parameter in your API call.

How much does TemplateFox cost?

There's a free tier with 60 PDFs per month, no credit card required. Paid plans start at $19/month. wkhtmltopdf is free to use, but maintaining an archived binary — packaging it into containers, managing fonts, handling breaking OS updates — costs real engineering hours. See pricing.

What's the easiest way to migrate from wkhtmltopdf?

Your existing HTML templates are a great starting point — paste them into the template editor, swap float hacks for Flexbox or Grid, and bind dynamic data with TemplateFox's variable syntax. Most migrations take under an hour per template.

Automate your PDF generation

Complete documentation, no-code integrations, and a powerful API to help you generate PDFs at scale. Let us handle the boring stuff.