The landscape of Markdown-to-book tooling shifted meaningfully in 2025–2026. GitBook's aggressive price hike (premium now 65–65–249/month) pushed thousands of users toward open-source alternatives. Bookdown's hosting service shut down January 31, 2026. Typst hit 45k GitHub stars. And several tools matured enough to offer credible multi-format publishing from Markdown. This post compares five tools that come up repeatedly in migration threads, tested against the same 12-chapter sample book on a 2023 MacBook Pro (M2, 16 GB). Quick Comparison Tool Stars Language PDF HTML/Site ePub Zero-config Single binary Learning curve Pandoc 42.7k Haskell Via LaTeX Single page only Native No Yes High mdBook 19.7k Rust Plugin (Chromium) Native site Plugin No Yes Low HonKit 2.5k Node.js Via Calibre Native site Via Calibre No No (Node.js) Low Quarto 5.4k TypeScript/Lua Via LaTeX/Typst Native site Native No No (multi-component) Medium mdPress New Go Native (Chromium) Both Native Yes Yes Low Tool-by-Tool Notes Pandoc (v3.9.0.1) is the universal document converter — 60+ format conversions, Lua filters for AST manipulation, and as of v3.9 it even compiles to WASM and runs in the browser. It is the engine underneath R Markdown, Bookdown, and Quarto. The trade-off: it is a conversion engine, not a book-publishing workflow. There are no built-in themes, no site generation, no live preview. Getting a well-styled PDF requires learning LaTeX templates or writing Lua filters. The command-line interface rewards power users and frustrates everyone else. mdBook (v0.5.2) is what the Rust community uses for The Rust Programming Language book. Single Rust binary, zero dependencies for HTML output, 5 built-in themes, 40+ community plugins. Version 0.5.0 was a major release — sidebar chapter headings, definition lists, and Admonitions became defaults. The catch: PDF requires the mdbook-pdf plugin (depends on Chrome), ePub requires mdbook-epub. For pure HTML documentation sites, it is hard to beat. For multi-format publishing, the plugin chain adds friction. HonKit (v6.1.4) is GitBook Legacy's open-source successor. Plugin compatibility with the old gitbook-plugin-* ecosystem is its strongest selling point — hundreds of npm packages still work. honkit serve improved from 28.2s to 0.9s. The downsides: PDF/ePub generation requires Calibre (a heavyweight Java-based dependency), the codebase carries acknowledged technical debt, and the development pace has slowed. Quarto (v1.9.27) from Posit is a full scientific publishing framework — R, Python, Julia, Observable JS with executable code blocks. Version 1.8 added Axe-core accessibility checking and switched the default LaTeX engine to lualatex. For data-science books, it is in a class of its own. The installation is heavier (~300 MB, bundling Pandoc + Typst + Deno), and for prose-only books the overhead is real. mdPress (v0.3.0) is the newest entry. Written in Go, single static binary, no runtime dependencies beyond Chrome/Chromium for PDF. The key differentiator: PDF, single-page HTML, multi-page site, and ePub are all first-class native outputs — no plugins required. Three input modes: book.yaml config, SUMMARY.md (GitBook/HonKit compatible), or zero-config auto-discovery of Markdown files. Current gaps: no KaTeX math or Mermaid diagrams yet (plugin system is in development), and the community is still small. Build Performance (120-page sample book) Tool PDF HTML (single) Site ePub Pandoc + XeLaTeX ~12s ~1.5s N/A ~3s mdBook + mdbook-pdf ~8s N/A ~0.6s Plugin needed HonKit + Calibre ~15s ~2s ~1.2s ~14s Quarto + LaTeX ~14s ~2s ~3s ~4s mdPress (Chromium) ~5s ~1.2s ~0.8s ~2s Pandoc/Quarto times depend heavily on the LaTeX engine. HonKit's Calibre-based PDF is notably slow. mdPress and mdBook PDF both use Chromium under the hood. Output Quality PDF: Pandoc + LaTeX produces the best typography — ligatures, microtypography, widow/orphan control. Quarto matches this on its LaTeX backend. mdPress produces clean, readable PDFs with built-in cover pages, headers/footers, and page numbers — adequate for technical books, though not at the level of a tuned LaTeX pipeline. mdBook's PDF plugin is functional but styling options are limited. HTML/Site: mdBook and mdPress both generate clean static sites with search. mdBook has 5 themes; mdPress has 3. HonKit preserves the classic GitBook look. Quarto's HTML is the most feature-rich (tabsets, cross-references, executable code output). ePub: Pandoc and Quarto produce well-structured ePub 3 files. mdPress generates valid ePub 3 with CJK font support. HonKit's Calibre-based output works but feels dated. Honest Gaps Pandoc: Steep learning curve. No built-in themes, site generation, or live preview. mdBook: No native PDF or ePub. Plugin ecosystem fills the gap but adds setup complexity. HonKit: Technical debt. Calibre dependency is heavy. Development pace has slowed. Quarto: Heavy install. Overkill for prose-only books. mdPress: New project, small community. No math/diagram support yet. PDF depends on Chrome. Recommended by Use Case Use case Recommended tool Why Academic / data science book Quarto Executable code, citation support, LaTeX quality Format conversion pipeline Pandoc 60+ formats, programmable via Lua filters Developer docs site (HTML only) mdBook or VitePress Mature ecosystems, single binary GitBook migration (many plugins) HonKit Plugin ecosystem compatibility GitBook migration (few plugins) mdPress SUMMARY.md compatible, simpler setup Multi-format book (PDF + ePub + Site) mdPress All formats native, zero-config option CI/CD friendly, no Node.js mdBook or mdPress Single binary deployment The honest summary: none of these tools is universally best. Pandoc wins on format coverage and academic publishing. Quarto wins for data-science workflows. mdBook wins for documentation sites with a mature plugin ecosystem. HonKit wins for GitBook compatibility. mdPress wins on multi-format output with zero configuration — especially useful for CJK content and teams that want a single binary without runtime dependencies. Links: Pandoc | mdBook | HonKit | Quarto | mdPress   submitted by   /u/Repulsive-Composer83 [link]   [comments]