The forgiving limit.
500 KB is one of the most common upload limits across government portals, job applications, and university admission forms. It's also the most forgiving — for a typical single-page scanned certificate (3–4 MB at 300 DPI), compressing to 500 KB means keeping roughly 14% of the original data.
At this ratio, compression artifacts are minimal. Text is sharp, seals retain fine detail, photographs look clean, and even light watermarks survive. Most people viewing a 500 KB compressed certificate side-by-side with the original at screen resolution would struggle to spot the difference.
Where 500 KB excels.
500 KB is generous enough for most document types that struggle at tighter limits:
• Multi-page documents: A 2–3 page scanned document can compress to 500 KB with each page retaining good quality. Compare this to 100 KB, where even single-page documents show visible degradation.
• Colour-heavy certificates: Certificates with coloured seals, stamps, or decorative borders preserve their appearance at 500 KB. At 100–200 KB, colour gradients often show banding.
• Documents with photographs: ID proofs and certificates with embedded passport photos retain enough detail for clear identification. The photo may show slight softening but no visible block artifacts.
• Presentation slides: If your portal requires uploading a PDF of presentation slides, 500 KB handles a 5–10 slide deck reasonably well.
Contrast with tighter limits.
The quality difference between 500 KB and the tighter 100–200 KB range is substantial. If your portal gives you a choice or mentions 'up to 500 KB', always use the full allowance. There's no advantage to compressing more aggressively than your portal requires — it only reduces quality.
That said, if your original PDF is already under 500 KB (which happens with digitally-created PDFs, not scanned ones), there's no need to compress at all. Zcompressor won't re-encode a file that already meets your target.
Your files stay on your device.
Your document never leaves your browser. Compression runs 100% client-side using browser APIs — no server uploads, no data collection, no account required.