Self-hosting Gotenberg vs a managed PDF API in n8n
Gotenberg is a free, open-source, self-hosted PDF API — Docker in, PDF out — and it is genuinely excellent: MIT-licensed, battle-tested, with native Office-file conversion pdfmill does not have. So this is not a “Gotenberg is worse” pitch; on price and privacy it wins outright. The honest question for an n8n builder is narrower — do you want to operate it? Gotenberg means running the Docker service yourself: budgeting RAM for Chromium, adding containers once you pass a handful of parallel renders, patching Chromium and LibreOffice. pdfmill is the managed alternative — generate a PDF in n8n without hosting Chrome, from a dedicated node. Here is the honest tradeoff, every Gotenberg fact sourced and dated.
We build pdfmill, so treat this as our honest case — not a neutral review. pdfmill is newly launched. Every Gotenberg fact below is linked to its public source and dated (checked July 28, 2026); pricing changes, so verify anything load-bearing on Gotenberg's own site, and tell us if something here is out of date.
| pdfmill | Self-hosted Gotenberg | |
|---|---|---|
| Cost model | Flat monthly plan, hard cap, no overage: Free 75/mo, then $9/500, $19/2,000, $49/10,000. | Free and open-source (MIT) — no license or per-document fee at any volume; you pay only for the servers you run it on[github.com/gotenberg · July 28, 2026]. |
| What you operate | Nothing — it is a hosted API. No Chromium, no containers, no OS to patch. | You run and maintain the Docker service: Chromium + LibreOffice, roughly 512 MiB–1 GiB of RAM per instance, plus updates[gotenberg.dev/docs · July 28, 2026]. |
| Scaling past light load | Handled for you; concurrency is pdfmill’s problem, not yours. | One Chromium handles up to 6 parallel operations (--chromium-max-concurrency, default 6); beyond that you add instances, a queue, and your own load balancer[gotenberg.dev/docs · July 28, 2026]. |
| Security patching | pdfmill pins and patches Chromium/LibreOffice; you do nothing. | You own Chromium + LibreOffice CVE patching and tracking issues like the reported Chromium-URL-route memory leak (since fixed)[github.com/gotenberg · July 28, 2026]. |
| n8n integration | A dedicated community node (install once), two operations (template / HTML); verification in progress. | No first-party node; a third-party community node last published ~a year ago, useless without a Gotenberg server you host — or call the multipart API via the HTTP Request node[npmjs.com/package · July 28, 2026]. |
| Office (DOCX/XLSX/PPTX) | Not supported — renders HTML and stored templates to PDF/PNG only. | Native, via LibreOffice — Word, Excel, PowerPoint and 100+ formats to PDF[gotenberg.dev · July 28, 2026]. |
| Where your data goes | Documents render on pdfmill’s servers, return to your workflow as a binary, then purge — so data does leave your infrastructure. | Runs inside your own infrastructure — documents never leave your network, the right call for strict compliance or PII[gotenberg.dev · July 28, 2026]. |
Where a managed API removes the work
- No Chromium to operate. That is the whole point: no Docker service, no RAM budget (Gotenberg suggests ~512 MiB–1 GiB per instance[gotenberg.dev/docs · July 28, 2026]), no Chromium/LibreOffice CVEs to chase, no memory-leak class to track down[github.com/gotenberg · July 28, 2026]. You POST data, you get a document.
- n8n Cloud has no Docker. On n8n Cloud you cannot run a Gotenberg container next to your workflow at all — you would stand up and maintain separate infrastructure. A managed API needs none.
- A real node plus stored, branded templates. pdfmill ships a dedicated node with two operations and keeps versioned templates with data-merge — invoice, quote, report, certificate, packing slip — so you send data and get a finished document. The Gotenberg community node is third-party, roughly a year stale, and does nothing without a Gotenberg server you host[npmjs.com/package · July 28, 2026].
- Honest flat billing. Free 75 documents a month, then
$9/500,$19/2,000,$49/10,000. At the cap pdfmill stops with a namedQUOTA_EXCEEDEDand an upgrade prompt — never a silent overage.
Where self-hosting Gotenberg wins
Being straight: for a lot of teams, self-hosting Gotenberg is the right answer, and pdfmill cannot beat it on these. It is a superb piece of software, not a fallback.
- Price at any volume. Gotenberg is MIT-licensed and free — no per-document fee, ever[github.com/gotenberg · July 28, 2026]. Once you have absorbed the ops cost, it is dramatically cheaper at high volume than any metered API, pdfmill included. We can remove the operating; we cannot beat free.
- Your data never leaves your infrastructure. Gotenberg runs inside your own network, so documents are generated in-house — the right call for strict compliance, PII, or air-gapped environments. pdfmill is a hosted API, so your HTML and data transit our servers (returned as a binary, then purged), which some environments simply cannot allow.
- Native Office conversion. Via LibreOffice, Gotenberg converts DOCX, XLSX, PPTX and 100+ formats to PDF[gotenberg.dev · July 28, 2026] — a capability pdfmill does not have at all. If your job is “turn this Word or Excel file into a PDF,” Gotenberg is the tool.
- Battle-tested, and yours. ~12.7k GitHub stars and 50M+ Docker pulls, MIT-licensed and self-owned — no vendor to depend on, and you can fork it[github.com/gotenberg · July 28, 2026][hub.docker.com/r · July 28, 2026].
If you have the ops capacity, the volume, or the data-residency requirement, self-host Gotenberg. pdfmill is for the n8n builder who would rather not run it.
FAQ
Is pdfmill better than Gotenberg?
Not “better” — different, and it depends on whether you want to run infrastructure. Gotenberg is free, open-source (MIT), and self-hosted: you run its Docker service, which means operating Chromium, budgeting RAM, patching, and scaling it yourself. pdfmill is a managed API — you host no Chromium and get a dedicated n8n node, but you pay per plan and can never beat free-at-scale. If you have the ops capacity and want zero per-document cost, self-host Gotenberg. If you build in n8n and would rather not operate a render engine, pdfmill fits better.
Can I generate a PDF in n8n without hosting Chrome?
Yes — that is exactly what pdfmill is for. Its community node renders a PDF or PNG from a stored template or your own HTML with no Chromium to run. Gotenberg can produce the same PDFs, but you host the Docker service (and the Chromium inside it) yourself. On n8n Cloud there is no Docker, so a self-hosted Gotenberg would have to run on separate infrastructure you stand up and maintain.
Is there an official Gotenberg node for n8n?
No first-party or n8n-verified Gotenberg node. A third-party community node, n8n-nodes-gotenberg-pdf, exists on npm but was last published in July 2025, and it does nothing without a Gotenberg server you host yourself. Because Gotenberg is a plain multipart HTTP API, many n8n builders skip the node entirely and call it with the built-in HTTP Request node. pdfmill ships its own dedicated node (n8n-nodes-generate-pdf) with two operations; note pdfmill’s node is a community node with verification in progress, not yet verified.
Does Gotenberg cost anything?
No. Gotenberg is MIT-licensed and free at any volume — there is no license fee and no per-document charge. The only cost is the infrastructure you run it on: RAM for Chromium (Gotenberg’s docs suggest roughly 512 MiB to 1 GiB per instance), containers, security patching, and uptime. pdfmill cannot beat free; what a managed plan removes is the operating, not the compute bill.
Can pdfmill convert Word, Excel, or PowerPoint files to PDF?
No. pdfmill renders HTML and its stored templates to PDF or PNG only. Gotenberg converts DOCX, XLSX, PPTX, and 100+ other formats to PDF natively via LibreOffice — a capability pdfmill does not have. If your job is turning Office files into PDFs, self-hosting Gotenberg (or another LibreOffice-backed tool) is the right choice.
Sources
- https://gotenberg.dev — accessed July 28, 2026Gotenberg: “A Docker-based API built for PDF conversion.” Self-hosted; headless Chromium for URL/HTML/Markdown → PDF; LibreOffice for Office documents (Word/Excel/PowerPoint and 100+ formats).
- https://github.com/gotenberg/gotenberg — accessed July 28, 2026MIT license; ~12.7k stars (12,743 at access); “A developer-friendly API for converting many document formats into PDF files, and more!”
- https://gotenberg.dev/docs/configuration — accessed July 28, 2026“A Chromium browser can handle up to 6 parallel operations” — flag --chromium-max-concurrency (default 6); --chromium-max-queue-size for the request queue; scale by increasing the number of Gotenberg instances.
- https://gotenberg.dev/docs/getting-started/installation — accessed July 28, 2026RAM guidance: Kubernetes “allocate at least 512Mi of memory and 0.2 CPU”; Cloud Run “allocate at least 1Gi of memory for a smooth experience”; the live demo runs on 512MB RAM.
- https://github.com/gotenberg/gotenberg/issues/987 — accessed July 28, 2026Issue #987 “Memory leak route POST /forms/chromium/convert/url” (41 comments; state: closed) — the memory-leak class illustrating the ops burden of self-hosting; cited as reported-and-fixed, not a current defect.
- https://www.npmjs.com/package/n8n-nodes-gotenberg-pdf — accessed July 28, 2026n8n-nodes-gotenberg-pdf — third-party community node, v1.2.1, last published 2025-07-02; “n8n community node for Gotenberg PDF conversion API,” requires a running (self-hosted) Gotenberg backend. Not first-party and not n8n-verified.
- https://hub.docker.com/r/gotenberg/gotenberg — accessed July 28, 2026Docker Hub gotenberg/gotenberg — 50M+ pulls at access.
See for yourself
Render your first PDF from an n8n workflow in about five minutes — the Free plan is 75 documents a month, no card required.