It's definitely far easier to emit a controlled, useful subset of PDF than it is to parse PDF documents. I wrote a small PDF library for the Decker ecosystem that just focuses on bitmaps and page layout; roughly 4kb and 135 LoC.
I’m working on one rn. It takes arbitrary PDFs and builds composable dynamic pandoc pipelines to match the source byte for byte output. It’s very very complex. But if I can get it finished it will fuck over Adobe so worth it.
While not quite as small as 3kb, I recently found this incredible library called html-to-image that's only 300kb. It clones whatever subtree of your document you want to a <foreignObject> inside an svg which then allows it to output canvas, png, svg, pdf, blob, jpeg, etc. Even more impressively is that it handles custom fonts, pseudo-elements, computed styles and more.
Only supports ASCII characters, which is part of the trick here. As soon as you need more Unicode (even just typographic quote characters and such), you’ll need significantly more logic. Also no bold, italics, etc.
Back in the day I needed PDF export for some client thing. I can't remember if I was using pdfjs or jspdf. I do however remember that it was many thousands of lines of code, and yet, I had to lay out the lines of text on the page manually.
My page layout code was like 50 lines of code. And I remember thinking... OK they already wrote 8,000 lines of code... They couldn't have added 50 more?!
400 lines though. Respect. I will take a proper look at this when I recover from burnout :)
Great exercize, but for most use cases - people will continue reaching for jsPDF.
I think if you have a markdown->PDF function included, where I can send in markdown and get PDF, that would solve quite many needs, and would be useful.
Was Typst falling short in any particular area that made you not want to use it? (If it was on your radar at all). I think it would work for your use case and could also run client side if needed.
Nice work! I'm curious though, what was your use case for needing a smaller library? Since you're running this on a server, what difference does an extra 226KB make?
That makes sense. I was mostly curious about what explicit trade-offs the author chose beyond “generation only” — e.g. fonts, Unicode, images, compression, etc.
Would be interesting to see a concrete “not supported” list from the author.
I still have a tiny DOS binary (x86 Asm) that I wrote decades ago for turning plaintext ASCII files into PDFs, for those annoying use-cases where the former isn't accepted but the latter is. It's only a few hundred bytes, with the majority being data to be copied verbatim into the output file.
It's definitely far easier to emit a controlled, useful subset of PDF than it is to parse PDF documents. I wrote a small PDF library for the Decker ecosystem that just focuses on bitmaps and page layout; roughly 4kb and 135 LoC.
docs/demos: https://beyondloom.com/decker/pdf.html
browsable source: https://github.com/JohnEarnest/Decker/blob/main/examples/dec...
This decker stuff is pretty nifty too
I’m working on one rn. It takes arbitrary PDFs and builds composable dynamic pandoc pipelines to match the source byte for byte output. It’s very very complex. But if I can get it finished it will fuck over Adobe so worth it.
While not quite as small as 3kb, I recently found this incredible library called html-to-image that's only 300kb. It clones whatever subtree of your document you want to a <foreignObject> inside an svg which then allows it to output canvas, png, svg, pdf, blob, jpeg, etc. Even more impressively is that it handles custom fonts, pseudo-elements, computed styles and more.
https://github.com/bubkoo/html-to-image
It's probably the most impressive and seamless experience I've had with converting HTML to pdfs/images so I just wanted to sing its praises here
It does sound very cool, but I don't think it exports to PDF: https://github.com/bubkoo/html-to-image/issues/327
Oh my, you're right. I've actually only tried it for exporting to images. Sorry for the misleading comment!
Only supports ASCII characters, which is part of the trick here. As soon as you need more Unicode (even just typographic quote characters and such), you’ll need significantly more logic. Also no bold, italics, etc.
Back in the day I needed PDF export for some client thing. I can't remember if I was using pdfjs or jspdf. I do however remember that it was many thousands of lines of code, and yet, I had to lay out the lines of text on the page manually.
My page layout code was like 50 lines of code. And I remember thinking... OK they already wrote 8,000 lines of code... They couldn't have added 50 more?!
400 lines though. Respect. I will take a proper look at this when I recover from burnout :)
Great exercize, but for most use cases - people will continue reaching for jsPDF.
I think if you have a markdown->PDF function included, where I can send in markdown and get PDF, that would solve quite many needs, and would be useful.
I have added it!
Wow you’re not kidding. That was fast.
https://github.com/Lulzx/tinypdf/commit/961e6b602f19e125f210...
HTML -> PDF was also a use case I've used previously FYI
Was Typst falling short in any particular area that made you not want to use it? (If it was on your radar at all). I think it would work for your use case and could also run client side if needed.
Here's the TS library: https://github.com/Myriad-Dreamin/typst.ts
So essentially - it only works with Latin script? Because without fonts, every other script is NOT going to render.
Agree, the lack of support for TTF fonts is a bummer for most non-english use cases:-/
Nice work! I'm curious though, what was your use case for needing a smaller library? Since you're running this on a server, what difference does an extra 226KB make?
on cloudflare workers, the bundle limit makes 226KB massive.
FWIW, the limit these days is 10MB (after compression).
https://developers.cloudflare.com/workers/platform/limits/
That said, thank you for fighting library bloat! Small libraries tend to perform better (not just on Workers but in general).
3KB is wild. What features did you intentionally leave out to get this small?
Not the author, but generating PDFs is much, much simpler than parsing PDFs
That makes sense. I was mostly curious about what explicit trade-offs the author chose beyond “generation only” — e.g. fonts, Unicode, images, compression, etc.
Would be interesting to see a concrete “not supported” list from the author.
Support for more than 7-bit ASCII characters. :)
It only supports Helvetica!
utf-8
I still have a tiny DOS binary (x86 Asm) that I wrote decades ago for turning plaintext ASCII files into PDFs, for those annoying use-cases where the former isn't accepted but the latter is. It's only a few hundred bytes, with the majority being data to be copied verbatim into the output file.
I actually was battling jsPDF the other day so definitely need to give this a try, thanks!
HTML + CSS works great for this kind of thing. Once you get the print scope correct, you really never need to think about it again.
Heh, no stars when I first looked and though "hey I'll star this" and now 300 ;-)
Great work thanks for sharing. I've been looking for something like this for generating invoice PDFs without bloat.
Well ain’t that a useful 400 lines of code eh! Good work
is it related to one of the other 10 products called TinyPDF?
Yes, obviously: it's a tiny PDF library.