Deprecated since January 2023

DocuQueue vs wkhtmltopdf modern Chromium meets zero maintenance

⚡ TL;DR Modern alternatives to deprecated tool

wkhtmltopdf vs DocuQueue — TL;DR by use case:

If you need a modern alternative: DocuQueue uses Chromium (2024). wkhtmltopdf uses WebKit (2020, deprecated).

If you need managed, no maintenance: DocuQueue is fully managed. wkhtmltopdf requires server setup and patches.

If you need DOCX templates: DocuQueue has built-in template engine. wkhtmltopdf is HTML-to-PDF only.

If you need auto-scaling: DocuQueue auto-scales. wkhtmltopdf is single-server, limited throughput.

DocuQueue

Chromium-based, modern CSS/JS support. wkhtmltopdf uses deprecated WebKit with known bugs.

Start free — 5 credits, no card →

DocuQueue

Fully managed. No servers to maintain, no security patches, no memory leaks.

Start free — 5 credits, no card →

DocuQueue

DOCX template engine with AI field detection. wkhtmltopdf is HTML-to-PDF only.

Start free — 5 credits, no card →

DocuQueue

Auto-scales with demand. wkhtmltopdf is single-server with limited throughput.

Start free — 5 credits, no card →

Replace deprecated wkhtmltopdf with a modern Chromium-based HTML to PDF API. Full CSS3, JavaScript support, form filling, batch processing, and zero security vulnerabilities. One API call, no binaries to install, no Docker to maintain.

wkhtmltopdf: a fair look

wkhtmltopdf has been a go-to HTML-to-PDF tool for over a decade. It's free, open source, and gets the job done for simple use cases. But it was deprecated in January 2023, and that matters for production systems.

What it does well

wkhtmltopdf is free and open source under the LGPL license. It uses WebKit-based rendering, has a simple command-line interface, and works well for basic HTML-to-PDF conversion. If you have a stable, low-volume setup, it still does the job.

Where it runs into trouble

The GitHub repository was archived in January 2023. No new releases, security patches, or bug fixes are planned. It requires self-hosting and server management. Memory leaks and concurrency issues are common at scale. There's no API access, no MCP/AI agent support, no form filling, and no visual template editor.

What wkhtmltopdf is actually good at

Before we talk about alternatives, it's worth acknowledging what wkhtmltopdf does well. These are real advantages that matter for certain use cases.

Free and open source — no licensing costs

wkhtmltopdf is licensed under LGPL. There are no per-document fees, no subscription costs, and no vendor lock-in. If you're cost-sensitive and can handle self-hosting, this matters.

WebKit-based rendering

For the HTML/CSS it supports, the rendering is solid. It handles basic layouts, tables, and images well enough for many document types.

Simple command-line interface

One binary, one command, one output file. No API keys, no authentication, no rate limits. The simplicity is genuine.

Good for basic HTML-to-PDF

If your HTML is simple and your volume is low, wkhtmltopdf works. It's been doing this for over a decade.

No API limits

Self-hosted means no one else sets your rate limits. Generate as many PDFs as your hardware can handle.

Where it stops

wkhtmltopdf served its purpose well, but here's where it falls short for modern document automation.

Deprecated — no longer maintained

The GitHub repository was archived in January 2023. No new releases, security patches, or bug fixes are planned. You're running software that will never improve.

No MCP/AI agent support

wkhtmltopdf is a command-line tool. There's no Model Context Protocol server, no API integration for AI agents like Claude or GPT. You'd have to build all of that yourself.

No form filling support

wkhtmltopdf generates PDFs from HTML. It cannot detect or fill form fields in existing PDFs. DocuQueue handles this natively.

No visual template editor

All templates must be hand-coded HTML/CSS. No visual editor, no drag-and-drop, no way for non-technical users to design templates.

Self-hosting burden

You manage the server, the binary, Docker containers, memory allocation, and security patches. That's DevOps time and ongoing maintenance cost.

Memory management issues

Verified memory leak of 20-60KB per call. Not thread-safe — concurrent requests can cause PDF cross-contamination. Processes hang indefinitely with no built-in timeout.

No API access

No REST API, no webhooks, no cloud deployment option. Everything runs locally on your infrastructure.

No modern features

No batch processing, no async job queues, no URL-to-PDF with JavaScript rendering, no DOCX templates. The feature set has been frozen since 2012.

DocuQueue vs wkhtmltopdf

Here's how DocuQueue compares to wkhtmltopdf on the features that matter for modern document automation.

Managed platform

No servers to manage. wkhtmltopdf requires self-hosting with Docker or bare metal setup.

MCP server for AI agents

Built-in Model Context Protocol server. Connect Claude, GPT, or any AI agent. wkhtmltopdf has none.

Form filling built-in

Detect and fill PDF form fields with JSON data. wkhtmltopdf has no form filling support.

URL-to-PDF conversion

Send a URL, get a PDF. Full JavaScript rendering. wkhtmltopdf has limited URL support with frozen WebKit.

Visual template editor

Design templates visually. wkhtmltopdf requires hand-coded HTML/CSS only.

No server management

REST API, no binaries, no Docker. wkhtmltopdf requires self-hosting and ongoing maintenance.

Start generating PDFs in 5 minutes — free tier

wkhtmltopdf vs DocuQueue

Feature wkhtmltopdf DocuQueue
Cost Free (self-hosted) Free tier (25 credits/mo), $9/mo starter
Infrastructure Self-hosted (Docker or bare metal) Managed platform
MCP Server None Built-in
Form Filling No support Auto-detect & fill
URL-to-PDF Limited (frozen WebKit) Full Chromium rendering
Visual Editor None Template editor
Maintenance Self-maintained (deprecated) Managed (actively maintained)
Status Deprecated (Jan 2023) Active development
Ready to switch? Start free — no card required

Replace wkhtmltopdf with one API call

Whether you use Python with pdfkit or Node.js with puppeteer, switching to DocuQueue is straightforward. Here's how to migrate your HTML to PDF code.

python-pdfkit (requires wkhtmltopdf)
import pdfkit

# Requires wkhtmltopdf binary on system
html = "<h1>Invoice #1042</h1>"

options = {
    'page-size': 'A4',
    'margin-top': '20mm',
    'margin-bottom': '20mm',
}

pdfkit.from_string(
    html, 
    'invoice.pdf', 
    options=options
)
DocuQueue Python (no binary needed)
import requests

html_content = "<h1>Invoice #1042</h1>"

response = requests.post(
    "https://docuqueue.com/api/v1/convert-html",
    headers={"api-key": "YOUR_KEY"},
    json={
        "html": html_content,
        "format": "A4",
        "margin": {
            "top": "20mm",
            "bottom": "20mm"
        }
    }
)

# Save PDF
open("invoice.pdf", "wb").write(response.content)
DocuQueue Node.js (no puppeteer needed)
const response = await fetch(
  "https://docuqueue.com/api/v1/convert-html",
  {
    method: "POST",
    headers: {
      "api-key": "YOUR_KEY",
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      html: "<h1>Invoice #1042</h1>",
      format: "A4",
      margin: { top: "20mm", bottom: "20mm" },
    }),
  }
);

// Save PDF
const buffer = await response.arrayBuffer();
fs.writeFileSync("invoice.pdf",
  Buffer.from(buffer));

When to choose which

Stay on wkhtmltopdf if...

  • You have DevOps resources to manage servers and deployments
  • You need free software with no licensing costs
  • You want full control over your infrastructure
  • You have low volume and simple HTML templates
  • Your current integration works and you don't need modern features

Switch to DocuQueue if...

  • You want a managed platform with no server management
  • You need MCP/AI agent support for document generation
  • You need PDF form filling with AI-powered field detection
  • You want a visual template editor for non-technical users
  • You don't want to worry about deprecated software and security patches
Get started with DocuQueue — 5 free credits

Frequently asked questions

Common questions about wkhtmltopdf and DocuQueue for HTML-to-PDF conversion.

Is wkhtmltopdf better than DocuQueue?
wkhtmltopdf is free and open source, which is its main advantage. It works well for simple HTML-to-PDF conversion with basic templates. DocuQueue offers a managed platform with MCP/AI agent support, form filling, a visual template editor, and no server management. The best choice depends on your needs: wkhtmltopdf if you have DevOps resources and want free software, DocuQueue if you want a managed platform with modern features.
How much does wkhtmltopdf cost compared to DocuQueue?
wkhtmltopdf is free and open source under the LGPL license. There are no licensing costs. DocuQueue offers a free tier with 25 credits per month, with paid plans starting at $9/month. While wkhtmltopdf has no direct cost, it requires server infrastructure, DevOps time, and ongoing maintenance. DocuQueue eliminates those costs with a managed platform.
Does DocuQueue work like wkhtmltopdf?
Both convert HTML to PDF, but they work differently. wkhtmltopdf is a command-line tool you run on your own server. DocuQueue is a REST API — you send HTML or a URL and get a PDF back. DocuQueue also adds features wkhtmltopdf doesn't have: form filling, MCP server for AI agents, a visual template editor, and batch processing. The HTML/CSS is similar, but DocuQueue uses a modern Chromium engine instead of frozen WebKit.
Can I migrate from wkhtmltopdf to DocuQueue?
Yes. Migration is straightforward: (1) Sign up for a free account, (2) Replace your wkhtmltopdf command-line calls with a REST API POST request, (3) Pass your HTML or URL in the request body, (4) Remove the wkhtmltopdf binary from your server. Most migrations take 15-30 minutes. See the code examples above for Python and Node.js.
Which has better form filling: DocuQueue or wkhtmltopdf?
DocuQueue has built-in form filling with AI-powered field detection. You can detect form fields in existing PDFs, fill them with JSON data, and return the completed PDF. wkhtmltopdf has no form filling capability at all — it only generates PDFs from HTML. If you need to fill PDF forms, DocuQueue is the only option between the two.
Does DocuQueue have a free tier?
Yes. DocuQueue offers a free tier with 25 credits per month, no credit card required. Each credit generates one document. This is enough for testing, prototyping, and low-volume use cases. Paid plans start at $9/month for higher volume.

4 steps to replace wkhtmltopdf

A step-by-step guide to migrate your wkhtmltopdf integration to DocuQueue's modern HTML to PDF API.

1

Sign up

Create a free account and get your API key from the dashboard.

2

Replace code

Swap wkhtmltopdf calls for a single REST API POST request.

3

Test output

Verify formatting matches your requirements with modern CSS rendering.

4

Remove binaries

Delete wkhtmltopdf and Docker from your server. Done.

See how DocuQueue compares

vs Gotenberg

Self-hosted Chromium PDF engine. DocuQueue gives you the same quality without Docker or infrastructure.

vs Puppeteer

Headless Chrome library for PDF generation. DocuQueue wraps it in a managed API with templates and batch processing.

vs DocRaptor

HTML-to-PDF API at $49/mo. DocuQueue offers more features including URL conversion, templates, and form filling at a lower price.

PDF Form Filling

Fill PDF form fields programmatically. Auto-detect fields, fill with JSON data, and return completed PDFs.

Start generating PDFs in 2 minutes

5 free credits to start. No credit card required.

Get Started Free