Shipped · APIs and backends

What gotenberg/gotenberg shipped

The public repository of Gotenberg · github.com/gotenberg/gotenberg

Written by FoxPlug from the repository's own releases; not affiliated with Gotenberg. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/gotenberg/gotenberg; Gotenberg did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for gotenberg, free

Week of November 2, 2026

What shipped

Why it matters

Version 9 is now the latest release and replaces four PDF tools with a single engine, with an upgrade guide for every route, field, flag, metric and span from version 8. Version 8 users should stay pinned to version 8 until they upgrade, and version 8.40.0 is its final release. The new compose and extract-attachments routes add page composition and attachment extraction, and several security fixes harden how ExifTool and QPDF handle input.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Gotenberg 9 is released: litho replaces pdfcpu, QPDF, pdftk and ExifTool, with an upgrade guide mapping every version 8 route, field, flag, metric and span. Version 8.40.0 is the final version 8 release; pin version 8 until you upgrade. New: compose and extract-attachments routes

Post for LinkedIn

Gotenberg 9 is now the latest release. It replaces pdfcpu, QPDF, pdftk and ExifTool with litho as the single PDF engine, and includes an upgrade guide that maps every Gotenberg 8 route, field, flag, metric and span to its version 9 counterpart. Version 8.40.0 is the final version 8 release, so pin gotenberg/gotenberg:8 until you have upgraded. Version 9 also adds a compose route for drawing pages of uploaded PDFs onto new pages of a chosen size, and an extract-attachments route for returning files embedded in a PDF. Version 8 releases this week fixed passing encryption passwords to QPDF as option values and rejected ExifTool's j option alias and config file loading.

Week of October 26, 2026

What shipped

Why it matters

This week closes a security gap in ExifTool handling and fixes three conversion problems that affected merged PDFs and error responses. Users merging documents with images or with PDF/A, and users sending print parameters that Chromium rejects, get correct output and clearer failures.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Gotenberg 8.39.0 is out: security fix for ExifTool config loading and its j alias. Also fixed image matching in pdfcpu optimization, 400 responses for all Chromium print parameter errors, PDF formats applied after LibreOffice merges, and PDF/A-4 support.

Post for LinkedIn

Gotenberg 8.39.0 is available. This release includes a security fix that rejects ExifTool's j option alias and stops loading ExifTool config files. It also fixes image optimization so extracted images are matched by page, returns 400 for every Chromium print parameter it rejects, applies PDF formats after merging LibreOffice documents so PDF/A output is preserved, and adds PDF/A-4 support to the pdfa form field.

Week of October 19, 2026

What shipped

Why it matters

This week fixes several regressions that broke working configurations: absolute TLS paths that left the server with no listener, and empty stamp or watermark sources that started failing requests. It also makes OIDC auth accept valid tokens regardless of how the Bearer scheme is capitalized. Clients get a new way to record the version behind a result, and HTTP/2 connections should reset less often.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: a Gotenberg-Version header on authenticated responses, absolute TLS cert paths fixed, empty stamp and watermark sources treated as no entry, case-insensitive Bearer scheme for OIDC, and a 16 KiB HTTP/2 max frame size.

Post for LinkedIn

This week's changes to Gotenberg: authenticated API routes now set a Gotenberg-Version response header so clients can record which version produced a result without polling the version endpoint. TLS certificate and key files are read before the server starts, so absolute paths no longer leave Gotenberg running with no listener. An empty stampSource or watermarkSource is treated as no entry again. The OIDC Bearer scheme is matched case-insensitively, so valid tokens pass regardless of capitalization. The HTTP/2 server now advertises the protocol default 16 KiB maximum frame size instead of Go's 1 MiB default, which stops a class of sporadic connection resets.

More from gotenberg/gotenberg on GitHub

Merged pull requests

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-10.

Is this your repo? Ask us to remove this page.