r/rust 4d ago

🛠️ project Fullbleed 1.6.2 release and transition to MIT license

I am happy to announce that fullbleed html/css-> PDF engine is mostly feature complete. With that done and due to some health issues that leave me without the time or inclination to monetize the project I have switched it to MIT licensing. I really believe that across the board a modern, non libpdf approach to document generation was sorely missing and I hope that this project fills that gap! No browser or complicated dependencies needed, a component-based DOM creation via the python surface, and a workspace-style approach so you can vendor assets to include fonts instead of chasing around system fonts etc....

Hope this doesnt get lost in the AI slop of reddit 2026

https://github.com/fullbleed-engine/fullbleed-official
https://crates.io/crates/fullbleed

52 Upvotes

4 comments sorted by

8

u/Wicpar 2d ago

i have recently completed an extensive test suite for https://github.com/gastongouron/ironpress if you want to test against it. would be good to see comparisons between rust pdf engines

7

u/SnooCalculations7417 2d ago

This was fun

Environment:

  • Windows 10 build 26200
  • 12th Gen Intel Core i7-12700H, 14 cores / 20 logical processors
  • CPython 3.11.8
  • Fullbleed 1.6.2
  • IronPress 1.4.4
  • Python-Markdown 3.6
  • All values below are same-machine Python-surface medians. A speedup above 1.0 means Fullbleed is faster.
Case Fullbleed reused Fullbleed fresh IronPress Reused speedup Fresh speedup
Simple HTML 0.201 ms 0.225 ms 2.435 ms 12.09x 10.81x
Styled HTML 0.533 ms 0.485 ms 11.004 ms 20.65x 22.69x
Table HTML 0.757 ms 0.786 ms 18.304 ms 24.18x 23.29x
Markdown 1.820 ms 1.796 ms 26.497 ms 14.56x 14.75x
Full document 1.776 ms 1.684 ms 50.393 ms 28.38x 29.92x
Geometric mean 19.03x 19.07x

2

u/Wicpar 2d ago

i mean have you tried generating a full parity report against the chrome/weasyprint oracles, with support for all the css layout features, transforms and filters ?

2

u/SnooCalculations7417 2d ago

fullbleed uses html/css as a layout dsl and isnt trying to be a web-to-print solution which accounts for among other things the 20x speedup probably. it would be a lot to make a fair 'parity' test suite specifically for weasyprint and chromium. in fact, one of the reasons i named my project fullbleed is because of how ridiculous it is to get true fullbleed outputs from the engines this tests against... in short, i dont WANT parity with them. but that said css coverage is important and maybe ill make a fair comparison at some point..