printpdf

Rust / WASM library for reading, writing and rendering PDF

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

0Explicit recommenders

1.2KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Rust / WASM library for reading, writing and rendering PDF

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

yfedoseev/pdf_oxide · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-10-26 09:23:59 UTC to 2026-10-26 11:22:53 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Oct 26, 09:00	2026-10-26 09:00:00 UTC	2026-10-26 10:00:00 UTC	1	1
Oct 26, 10:00	2026-10-26 10:00:00 UTC	2026-10-26 11:00:00 UTC	0	0
Oct 26, 11:00	2026-10-26 11:00:00 UTC	2026-10-26 12:00:00 UTC	1	1

What Hacker News says

2 sources

tchalla·Oct 26, 2026

> https://github.com/yfedoseev/pdf_oxide which this project builds on completely misses https://github.com/fschutt/printpdf which was already developed with tons of fixes over years (both with and without AI). MIT license and also builds on WASM with a demo running on https://fschutt.github.io/printpdf/ It seems like fschutt/printpdf is your project. You should definitely at least disclose it in your comment, if that's the case.

In PaperPilot – Zero-Cloud, Pure-Rust PDF Engine with WASM and MCP

fschuett·Oct 26, 2026

Why do people try to vibecode PDF engines that already exist in Rust? https://github.com/yfedoseev/pdf_oxide which this project builds on completely misses https://github.com/fschutt/printpdf which was already developed with tons of fixes over years (both with and without AI). MIT license and also builds on WASM with a demo running on https://fschutt.github.io/printpdf/ One Google search (yeah I'm old, sorry, nobody "Googles" anymore) for "rust pdf library" shows this. Yet people now redo and redo and redo everything again just to have "their" semi-broken copy of a HTML -> PDF renderer (and then run into the same edge cases that were already fixed before). There are lots of edge cases in typography especially, I recently had a lot of fixes as I was trying to ocr-and-cleanup a 1732 scan of some books with Claude auto-extracting the font. T

Read the rest

here were a ton of edge cases in the layout, esp. related to column, footnote and sidebar handling, or things like "Hebrew RTL text accidentally disappears if text breaks weirdly", "1-bit image compression", etc. I have nothing against AI, I use it heavily myself, but what is annoying is people completely ignoring the years of work of existing projects that do the exact same thing - instead of just forking, but instead re-tokenizing the exact same work again. Most likely the author didn't research "does this already exist" and that's annoying, then you get 100 of similar projects reinventing the world with tokens again and again. Sometimes its beneficial and can lead to faster exploration of new approaches, but in most cases its not and misses edge cases that were solved before.

In PaperPilot – Zero-Cloud, Pure-Rust PDF Engine with WASM and MCP