Why this tool is different
Application portals routinely demand a PDF under 100KB and then reject yours at 104KB with no explanation. This works backwards from the limit: we budget the available bytes across your pages, compress each image to fit, build the PDF, measure it, and refine until it is genuinely under the target.
How it works
- 1
Add the images that should become pages.
- 2
Choose a target — 100KB by default.
- 3
We estimate the PDF overhead, share the remaining bytes across the pages, and compress to fit.
- 4
The finished size is shown before you download.
What to watch out for
Fewer pages means better pages
The byte budget is shared across every page. Five pages under 100KB means roughly 18KB of image each, which will look rough. Two pages at the same target look far better.
When a target is impossible
Some combinations simply cannot fit. Rather than producing an oversized file and calling it done, we explain the trade-off: fewer pages, grayscale, lower resolution, or a larger target.
Text scans need more room
Handwriting and small print degrade badly under heavy compression. For a document that has to stay readable, 200KB is a much safer target than 50KB.
Frequently asked questions
Will the PDF be exactly 100KB?
It will be at or under 100KB. Portals check that a file is not larger than the limit, so under is what matters — and we never pad a file to hit a number.
Can I use a different limit?
Yes. 50KB, 150KB, 200KB, 500KB and 1MB are one tap away, and you can type any custom target.
Why does my scan look blurry at 100KB?
Because 100KB is a very small budget for a photograph. Reduce the number of pages, or raise the target if the portal allows it.
Are my files uploaded to a server?
No. The conversion runs in JavaScript and WebAssembly inside your own browser. Open your devtools, switch to the Network tab and run a conversion — there is no upload request to see. Closing the tab clears the working session.