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.
About 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.
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.
An honest, section-by-section look at what each tool does and doesn't do.
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.
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.
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.
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.
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 freeTwo honest answers, depending on what you're optimizing for.
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.
Companies generating PDFs in production.
Growing every day on a scalable infrastructure.
Complete documentation, no-code integrations, and a powerful API to help you generate PDFs at scale. Let us handle the boring stuff.