Alternative to Gotenberg

Gotenberg vs TemplateFox

Gotenberg is a well-maintained, Docker-based API that wraps headless Chromium and LibreOffice for PDF conversion. If you're looking for a managed alternative with a visual template editor, built-in data binding, and no-code integrations — here's how TemplateFox compares.

Gotenberg logo About Gotenberg

What is Gotenberg?

Gotenberg is an open-source, Docker-based API for converting documents to PDF. Written in Go and maintained by Julien Neuhart, it bundles headless Chromium and LibreOffice inside a single container and exposes them through a clean HTTP API. You POST your files as multipart/form-data and get a PDF back.

It's built for developers who want a self-hosted conversion service. The Chromium routes turn URLs, HTML and Markdown into PDFs with modern CSS, Flexbox, Grid and JavaScript support. The LibreOffice routes handle Word, Excel, PowerPoint and 100+ other Office formats. On top of that, QPDF, pdfcpu and ExifTool cover merge, split, encrypt and metadata operations. Most teams deploy it on Cloud Run, Kubernetes, or a plain Docker host.

The project is actively developed — the repository passed 11k stars on GitHub and ships frequent minor releases on the 8.x line. It's under the MIT license and has a healthy contributor base. Where it deliberately stops is at conversion: Gotenberg is a converter, not a template platform — there's no editor, no template store, no data-binding engine. That's a design choice, and it keeps the project focused.

Pricing

Gotenberg is free and open source under the MIT license — no license fee, no usage limits. The real cost is operational: you host the Docker image yourself, size the container for Chromium memory, package the fonts your templates need, and scale workers as traffic grows. For a few PDFs per day on a small VM, that's fine. For production workloads with bursty traffic and Office-format conversions, the bill for compute, monitoring and engineering time typically adds up faster than people expect.

Feature comparison

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

1. Project health & rendering

Feature
Gotenberg
TemplateFox
Project status
Actively maintained (Julien Neuhart)
Actively maintained
Rendering engine
Headless Chromium + LibreOffice
Modern CSS engine
CSS Flexbox & Grid
Supported (Chromium)
Supported
PDF/A, PDF/X, PDF/UA
PDF/A via LibreOffice & pdfcpu
PDF/A-1b, A-2b, A-3b, PDF/X, PDF/UA

Gotenberg and TemplateFox are close on rendering: both are actively maintained and both use modern Chromium-class engines, so Flexbox, Grid and current CSS specs work out of the box. The PDF/A story is slightly different — Gotenberg routes PDF/A through LibreOffice and pdfcpu, while TemplateFox exposes PDF/A, PDF/X and PDF/UA as direct API parameters on every PDF.

2. Developer experience

Feature
Gotenberg
TemplateFox
Setup
Run the Docker image on your infra
API key, nothing to install
Template editor
None (raw HTML files sent as multipart)
Visual drag-and-drop editor
API
HTTP API (self-hosted)
REST API + SDKs (7 languages)
No-code platforms
None
Zapier, Make, n8n, Airtable, Bubble

Gotenberg's HTTP API is a genuine strength compared to CLI-only tools, and the Docker image makes it straightforward to spin up locally. The work starts once you run it in production: sizing the container for Chromium, packaging fonts, scaling horizontally, and wiring up observability. TemplateFox calls out to a REST API (or an official SDK in seven languages), and non-developers can edit templates in a visual editor — nothing to deploy, nothing to scale.

3. Features & data

Feature
Gotenberg
TemplateFox
Dynamic data binding
Bring your own (render HTML upstream)
Variables, loops, conditions
Multi-page tables
Manual CSS tuning
Automatic page breaks
Barcodes & QR codes
External libs required
Built-in (Code128, EAN-13, QR…)
Office formats (.docx, .xlsx)
Supported via LibreOffice
Not supported (HTML + CSS only)
Template management
None (stateless converter)
Versioned templates with a UI

This is where the tools diverge by design. Gotenberg is a conversion pipeline: you render your HTML upstream (with your own templating engine), add barcodes as images you've generated elsewhere, and POST the result. Office-format support via LibreOffice is where Gotenberg clearly wins — TemplateFox doesn't convert .docx or .xlsx. Going the other way, TemplateFox packages templates, variables, loops, conditions, barcodes and headers/footers into the editor, so there's no glue code between your data and the final PDF.

4. Hosting, compliance & pricing

Feature
Gotenberg
TemplateFox
Self-hosted
Yes (only option — Docker)
No (managed cloud)
Data handling
Your infrastructure, your rules
GDPR principles, privacy by design
Maintenance
You own it (image upgrades, scaling, fonts, Chromium memory)
Handled by us
Cost
Free OSS + your hosting & engineering time
Free tier (60/mo), then paid

This is where Gotenberg keeps a real edge: if your data can't leave your servers, a self-hosted Docker image 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 and infrastructure time saved on running Chromium + LibreOffice containers in production.

Want PDF generation without the Docker image?

No container to size, no fonts to package, no Chromium memory to tune. Just an API call. 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

  • Non-technical teammates need to edit templates without touching code
  • You're writing glue code to render HTML upstream before POSTing it to Gotenberg
  • Sizing Chromium memory, scaling workers, and packaging fonts is eating engineering time
  • You want versioned templates with a UI, not files in a repo
  • Barcodes, QR codes and data binding shouldn't be separate libraries anymore
  • You want to plug PDF generation into Zapier, Make, n8n or Airtable

Browse 30+ ready-made templates →

Stay with Gotenberg

When it can still be the right call

  • Self-hosting is a hard requirement — data must never leave your servers
  • You need to convert Office formats (.docx, .xlsx, .pptx) as well as HTML
  • You already render templates upstream and just need a reliable conversion endpoint
  • You're comfortable running Chromium + LibreOffice on your own infra

Gotenberg is one of the best-designed open-source PDF conversion APIs around. If self-hosting is your baseline and you need Office-format support alongside HTML, it's a strong long-term choice.

Used by 100+ Developers

Companies generating PDFs in production.

Uptime 99.997% Last 90 days

Measured live on our public status page.

Rendered 100k+ PDFs generated

Growing every day on a scalable infrastructure.

Frequently asked questions

Is Gotenberg still maintained?

Yes. Gotenberg is actively maintained by Julien Neuhart and contributors. The project is on its 8.x line, ships frequent releases on GitHub under the MIT license, and is one of the most active open-source Docker-based PDF projects.

What rendering engine does Gotenberg use?

Gotenberg wraps two engines inside a single Docker image. Headless Chromium handles URL, HTML and Markdown to PDF — so you get modern CSS, Flexbox, Grid and JavaScript. LibreOffice handles Office formats (.docx, .xlsx, .pptx and 100+ others). On top of that, QPDF, pdfcpu and ExifTool cover merge, split, encrypt and metadata operations.

What are the main limitations of Gotenberg?

Gotenberg is a converter, not a template platform. There's no visual editor, no template storage, no data-binding syntax — you render your HTML upstream (in your own app, with your own templating engine) and send the finished file to Gotenberg over multipart/form-data. Barcodes and QR codes need a separate library that produces an image you embed in the HTML. Operationally, you run the Docker image yourself: sizing the container for Chromium memory, packaging fonts, scaling workers, and upgrading LibreOffice and Chromium are all on your plate.

How does TemplateFox compare?

TemplateFox is a managed cloud PDF generation API. You design templates in a visual editor (still HTML and CSS under the hood), bind data with variables, loops and conditions, and generate PDFs via REST API or no-code platforms. Barcodes, QR codes, headers, footers and multi-page tables are built in, and you can output PDF/A, PDF/X, and PDF/UA without running any infrastructure yourself. The tradeoff: TemplateFox focuses on HTML + CSS — it doesn't convert .docx or .xlsx like Gotenberg does.

Can I reuse my HTML from Gotenberg?

Yes. TemplateFox uses a modern Chromium-class rendering engine, so any HTML and CSS you were sending to Gotenberg's Chromium route will work as a starting point. The parts that change are upstream: instead of rendering your HTML with a templating engine in your own app, you paste it into the template editor and move your variables into TemplateFox's data-binding syntax.

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 (air-gapped networks, strict data residency, regulated environments), Gotenberg's Docker image is a strong choice and keeps data in your environment. For most teams, the tradeoff of not maintaining a Chromium + LibreOffice container, its fonts, and its scaling 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 by passing the standard as a parameter in your API call. Gotenberg also supports PDF/A through its LibreOffice and pdfcpu routes — so if PDF/A is your only concern, that's not a reason to switch. The difference is in the developer experience around it and in the template workflow.

How does Gotenberg's cost compare to TemplateFox?

Gotenberg is free and open source under the MIT license — no license fee, no per-PDF cost. The real cost is operational: hosting the Docker image (Cloud Run, Kubernetes, a VM), sizing it for Chromium memory, packaging fonts, scaling workers, and keeping Chromium and LibreOffice up to date. TemplateFox has a free tier with 60 PDFs per month, no credit card required, and paid plans starting at $19/month. For low to medium volume, the subscription is usually lower than what a production-ready Gotenberg deployment costs once you factor in infra and engineering hours. See pricing.

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.