WeasyPrint
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
0warn against
Nov 10, 2025first mention
Aug 17, 2026latest mention
Why people recommend it
“I used Weasyprint so I could give them self-contained PDF as a keepsake.”
“built by own markdown to HTML to PDF/X-1a processor using Python, WeasyPrint, and ghostscript”
publishing print and ebooks since 2015switched from Microsoft Wordon “I Bypassed Adobe and Microsoft to Build a Git-Tracke…”
Show 2 more
“Weasyprint [0] is OSS and supports CSS Paged media”
“Uses weasyprint instead of wkhtmltopdf”
switched from wkhtmltopdfon “Show HN: MarkdowntoCV”
Caveats and dissent
No one in these comments warned against it.
Often compared with
Who recommends it in their own words
Threads where it came up
- How I Over-Engineered My Book 1 mention
- I Bypassed Adobe and Microsoft to Build a Git-Tracked Book Production Pipeline 1 mention
- item 47206082 1 mention
- Ask HN: What Are You Working On? (December 2025) 1 mention
- Show HN: MarkdowntoCV 1 mention
Data: weasyprint.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 5
“I used Weasyprint so I could give them self-contained PDF as a keepsake.”
“built by own markdown to HTML to PDF/X-1a processor using Python, WeasyPrint, and ghostscript”
“Weasyprint [0] is OSS and supports CSS Paged media”
“WeasyPrint was deadlocking a single-worker setup because it fetched the logo via HTTP.”
“Uses weasyprint instead of wkhtmltopdf”