# comparison
Posts tagged "comparison"
gpdf vs wkhtmltopdf vs Chromium-based PDF generation
wkhtmltopdf is archived. Chromium ships a 170 MB browser per request. gpdf renders a page in 13 µs with no browser. Here's the honest 2026 comparison.
Tables in Go PDFs: column widths, striped rows, page breaks
Tables are the hardest part of a Go PDF. gpdf collapses widths, stripes, and multi-page header repeat into one Table call — here is the whole API and what it costs.
From signintech/gopdf to gpdf: less coordinate math
signintech/gopdf works, but every cell, line, and header is an (x, y) calculation. This guide maps the gopdf API to gpdf — same Go, no coordinate math.
unipdf is AGPL or paid. Here's how to migrate to gpdf.
UniDoc's unipdf forces AGPL v3 or a per-developer commercial license. This guide maps the unipdf creator API to gpdf — MIT, zero deps, no license key.
Bootstrap thinking for PDF: gpdf's 12-column grid
gpdf borrows the 12-column grid from Bootstrap, but PDFs aren't web pages. Here's why 12 still works, and what we threw out: breakpoints, gutters, order.
Why gpdf is 10–30× faster than other Go PDF libraries
gpdf generates a single PDF page in 13 µs and a 100-page report in 683 µs. Not a tuning trick — three architectural choices that compound. Here's the code path.
go-pdf/fpdf is archived too. Here's the modern Go PDF stack.
jung-kurt/gofpdf archived in 2021. go-pdf/fpdf followed in 2025. Here's the Go PDF stack we actually use in 2026 — gpdf, the trade-offs, and why.
Go PDF Library Showdown 2026
The Go PDF library landscape in 2026: every active and archived library, benchmarked on 4 workloads, with license and dependency details.
gofpdf is archived. Here's how to migrate to gpdf.
jung-kurt/gofpdf was archived in 2021. This guide maps every gofpdf API to gpdf — a pure-Go replacement with native CJK support and zero dependencies.