Get bank and university documents under 200 KB without handing them to a server — every compression pass runs on your own computer.
Two hundred kilobytes is the middle tier of upload limits — common on bank KYC flows, brokerage onboarding, and university application systems that collect transcripts, address proofs, and identity documents one slot at a time. It is a friendlier budget than the 100 KB caps on some government sites: most single documents can get under it without visible damage.
After re-encoding, a typical scanned page settles between 50 and 90 KB, so a two-page certificate or a short statement usually lands below 200 KB with text that reads cleanly. The tool takes repeated passes, lowering resolution and image quality a step at a time, and stops the moment the output is smaller than your target — deliberately under it rather than on it, so strict validators do not reject a borderline file. If four dense pages refuse to fit at readable quality, the result is the closest smaller file plus an honest message about the gap.
Under the hood, each page is redrawn using Mozilla's pdf.js — the renderer built into Firefox — then saved back as a compact JPEG and stitched into a fresh PDF. Every step executes in a Web Worker on your computer; KYC paperwork is exactly the kind of file that should not pass through anyone's server, and here it does not. Encrypted PDFs are refused with an explanation rather than a cryptic error, and there is no signup, no daily allowance, and no stamp on the output.
No. Rendering, re-encoding, and rebuilding all happen on your own computer inside the browser, so KYC paperwork is never transmitted to anyone.
No — compressed pages are stored as images. For scanned statements and certificates that changes nothing; for a digitally created PDF, keep the selectable original and treat the compressed file as upload-only.
Two to four scanned pages typically fit with clean, readable text. Digitally created documents often start below this size and may not need compression at all.
The tool stops at the first pass that lands below the target, and finishing under the number keeps strict upload validators from bouncing a borderline file.