Compress PDF to 500KB
Compress PDF to 500KB online. Reduce your PDF file to around 500KB for email, uploads and forms, free, fast, no watermark.
PDF files · up to 50 MB each · 100 MB with a free account
| File name | Size | Compress to |
|---|
Checking files and selected compression settings.
This page stops at 50 MB and one file per run. Pro compresses files up to 1 GB and a full batch in one go, with a priority queue.
What this tool does
Set 500 KB as the target and the engine works down to it in steps, stopping at the first result that fits rather than padding the file back out.
It is the pictures inside the PDF that shrink: they are downsampled a step at a time until the file fits. Text typed into the document stays text, so it remains selectable and sharp at any target.
Files are processed on our servers, not in your browser. The upload and the result are both permanently deleted within 1 hour, no backups and no copies kept.
No watermark, and no account needed to use it. 5 files a day at up to 50 MB each, sent singly or together; signing in is free and raises each file to 100 MB.
Getting a statement under 500 KB
-
1
Check what you already have
Open the file properties before anything else. A good number of bank e-statements are already under 500 KB, and compressing one that fits only costs you quality.
-
2
Upload and aim at 500 KB
Pick the 500 KB target rather than a smaller one. The cap is what you have to clear; going further than it buys nothing and spends image detail you may need.
-
3
Read the result before you submit it
Open the compressed file and look at the transaction table, not the header. Small print in the body is where a too-aggressive target shows first, and it is the part the person at the other end actually reads.
Who actually needs a PDF under 500 KB
500 KB is the cap on two kinds of upload in particular. Income Tax Return supporting documents, such as Form 16, salary slips and rent receipts, are usually capped at 500 KB per file, and so are the three-month bank statements that loan applications ask for. Both are documents you did not create yourself: they arrive from a payroll portal or a bank, at whatever size that system decided to produce.
Check the original before you compress it
Most bank e-statements already ship between 300 and 800 KB, which means a good number of them are under the cap before you touch them. Compressing a file that already fits only degrades it. Open the file properties first; if it reads 480 KB, upload it as it is.
The ones that overshoot usually do so for a specific reason: the bank embedded transaction images, or the statement was scanned rather than generated. A statement that is genuinely text will rarely exceed 500 KB however many pages it runs to.
What a 500 KB target actually changes
Roughly 70 to 95 percent of a typical PDF's size is embedded images. Text and vector content are never rasterised during compression, so they stay sharp and selectable no matter how aggressive the target is. Everything a 500 KB target gives up comes out of the images.
At this target there is real headroom. A 13.2 MB three-page 300 DPI scan compresses to 724 KB when aimed at 1 MB, so 500 KB asks for more reduction than that but far less than the 96 KB the same file reaches at a 100 KB target. In practice a scanned statement stays readable, including the small print in transaction tables, which is the part that matters when a loan officer reads it.
When 500 KB is the wrong target
If nothing is imposing a 500 KB limit, do not use this page. A 1 MB target takes the same 13.2 MB scan to 724 KB with noticeably more image detail preserved, and every common email attachment limit accepts it comfortably.
If the document is going to a portal that states 200 KB or 100 KB, compress to that number directly rather than to 500 KB and hoping. Aiming at the cap you actually face produces a better result than compressing twice.
If it will not get under 500 KB
A scan that refuses to come down is almost always a high-DPI colour scan of many pages. Three things help, in order of how much they recover: rescan at 150 DPI rather than 300, scan in greyscale rather than colour, and split the document so each upload carries fewer pages.
Greyscale alone often does it. Bank statements and salary slips carry no information in their colour, and dropping it removes two of the three channels before any quality reduction is needed.
Questions people actually ask about this
My statement is already 420 KB. Should I compress it anyway?
No. It already clears the cap, and compressing it again only discards image data for no benefit. Upload the original.
Will the transaction table still be readable at 500 KB?
Yes. Text and vector content are never rasterised during compression, so they stay sharp and selectable whatever the target. Only embedded images are reduced, and at 500 KB there is a lot of headroom before that becomes visible.
Why is my scanned statement so much bigger than a downloaded one?
A downloaded e-statement is text, which costs almost nothing to store. A scan is a photograph of text, so every page is a full image. That is why a scanned statement can run to several megabytes while a downloaded one of the same length sits in the hundreds of kilobytes.
What if 500 KB still is not small enough?
Rescan in greyscale first. Statements and salary slips carry no information in their colour, and dropping it removes two of the three channels before any quality reduction is needed. After that, scan at 150 DPI rather than 300, then split the document so each upload carries fewer pages.