Compress a PDF to 500KB
500KB is easy to reach for text-based documents. Scanned files can usually reach it too, at the cost of image resolution — still readable, but detail softens. OlimPDF removes redundant objects first and only then reduces image sampling, so text is never rasterised.
Where the 500KB limit comes from
Mostly university application portals, older government platforms, and corporate intranet upload endpoints. These systems tend to restrict both format (PDF only) and size, and 500KB is a common compromise between storage cost and usability.
How to reach 500KB
- Enter 500KB as the target size. For scanned files, choose the scanned-document mode as well.
- In the preview, check stamps, signatures and table rules — those break first after downsampling.
- Still slightly over? Remove cover and instruction pages; that alone often saves 50–200KB.
Feasibility at 500KB
| File type | Feasibility | Recommendation |
|---|---|---|
| Transcripts, certificates, notarised copies | High | Set 500KB directly; usually one pass |
| Papers and reports with charts | Medium-high | Charts are lightly resampled; body text is untouched |
| A4 scan at 300dpi | Medium | Rescan at 200dpi first — compression then does less damage |
| Image-heavy portfolios | Low | At this size, preserving layout beats preserving detail |
When 500KB is not reachable
Documents that are full-page photographs or large gradients have only a few dozen KB per page at 500KB, so banding and grey wash are unavoidable. Do not keep recompressing: check whether the portal accepts split uploads, or compress the images locally before assembling the PDF — that usually looks better than squeezing the PDF itself.
Questions
Can a 500KB scan still be printed?
On screen it reads fine. Printed at large size, text edges soften. For a printed submission, target 1–2MB instead — the difference is obvious.
Do stamps disappear after compression?
They do not disappear, but red stamps blur at heavy downsampling. Always open the preview afterwards; if it looks wrong, raise the target and recompress.
Why is the output size different each time I compress?
The target is an upper bound, not a fixed output. The algorithm picks a path based on content, so results land close to each other but do not shrink indefinitely.