Application packets with a photo
A form, a photo and a signature in one file is the classic 200 KB case. The text stays vector-sharp while the photo is downscaled to a sensible resolution.
200 KB is the sweet spot for multi-page text documents: small enough for strict portals, large enough to keep images sharp.
document.pdf
——Analysing…
Your file stays in this browser tab. Closing it deletes everything.
Compressing your PDF…
0%Preparing…
Large files can take a minute. The interface stays responsive — you can keep scrolling while it works.
No uploadNo sign-upNo watermarkWorks offline
The realistic picture
At 200 KB you can usually keep text intact and still have room for a couple of photographs or a scanned signature. That makes this the best default for application packets, reports and forms that mix text with a few images.
The compressor starts with the least destructive option and only escalates when the measured file is still above the limit. For a text-based file that means you often get a result that looks identical to the original, with metadata removed and the internal structure rebuilt.
Where this limit shows up
A form, a photo and a signature in one file is the classic 200 KB case. The text stays vector-sharp while the photo is downscaled to a sensible resolution.
Assignments and project reports of 10–20 pages usually fit after the structural pass, especially when exported from Word or Google Docs.
A short proposal with a logo and a few charts fits comfortably, and the recipient can still select and search the text.
Two or three scanned pages at 200 KB are noticeably clearer than at 100 KB, which matters for stamps and handwritten notes.
Honest expectations
These are typical outcomes from real documents, not promises. The compressor reports the measured result for your specific file.
| Document type | Outlook |
|---|---|
| 10–20 pages of text | Reliable, often without touching images. |
| Text plus 2–4 photos | Reliable; photos downscaled moderately. |
| 3–5 scanned pages | Good legibility at moderate resolution. |
| Photo-heavy brochure | Possible, with visible softening of large images. |
The file is read in your tab and never transmitted.
Text and vectors survive unless rasterising is the only option.
A target is only marked met when the measured bytes fit.
Specific answers for this size limit, including when it is the wrong choice.
Yes, if the portal allows it. Doubling the budget lets the compressor keep roughly twice the image data, which is the difference between a stamp that is readable and one that is a grey smudge. Use the smallest limit the portal accepts.
No. Fonts are never substituted or re-subset by this tool. The text is rendered by the same font programs as the original; only the surrounding file structure and embedded images change.
It is already under 200 KB, so the tool returns it untouched and says so. Compressing further would only reduce quality with no benefit.
Yes. The tool uses standard browser APIs and picks a Web Worker when the browser supports OffscreenCanvas, otherwise it processes in smaller chunks on the main thread so the interface stays responsive. Safari 16.4 and newer is fully supported.
This tool compresses one file at a time by design, which keeps memory predictable on phones. Once a file is done you can start another without reloading the page.
No. There is no backend for file processing anywhere in this project. You can prove it by loading the page, switching off your network, and compressing a file — it still works.
Other limits