Compress an image to under 500 KB
Five hundred kilobytes is the ceiling you hit once a portal outgrows the small caps: job application systems, marketplace uploads, CMS media libraries, email policies that allow a few photos per message. This page opens the compressor with the budget already set — and at 500 KB, almost nothing has to give.
- Nothing is uploaded
- Budget: 500 KB
- JPEG · WebP · AVIF · PNG
- Unlimited & free
Drop your images here
or paste from the clipboard · ⌘V / Ctrl+V works too
JPG · JPEG · PNG · WebP · AVIF · HEIC · GIF · BMP — no file count limit
Compression settings
Applied to every imageAuto measures each image: it encodes a test pass at several quality levels, scores the result against the original, and keeps the smallest file that still clears a ~40 dB fidelity floor.
Advanced options
Auto applies a halo-free unsharp mask only when an image is scaled below 82%.
Generated in your browser by a synth — no audio file is downloaded, and it stays silent when a batch finishes in a couple of seconds.
WASM codecs are fetched from a public CDN on first use and give slightly smaller files. Every fallback still works offline.
Results
Why 500 KB shows up everywhere
Five hundred kilobytes is what form designers choose when the photo matters but the storage bill still does. It sits one rung above the classic 100–200 KB caps, and the systems that use it are everywhere:
| Where | Typical limit | Usual format rule |
|---|---|---|
| Job applications and ATS portals | 200 KB – 500 KB | JPG or PNG |
| Marketplace and classified listings | 200 KB – 1 MB | JPG or WebP |
| CMS, LMS and intranet media libraries | 500 KB – 2 MB | Anything |
| Government and visa portals (photo step) | 240 KB – 500 KB | JPG |
| Email attachment policies | ~1 MB per image batch | Anything |
At 500 KB, quality is not the question
Unlike a 50 KB budget — where every byte is fought over — 500 KB is generous enough that almost any image fits at its full resolution. A 12-megapixel phone photo written as high-quality JPEG lands between roughly 2 and 4 MB, so a large original still needs work; but anything at or below web resolution, every screenshot, every diagram, and most downscaled photographs fit with quality to spare. The engine still does the same job it does at every budget: it searches for the highest quality that fits under the line and reports the real byte count, so the file you upload is just under 500 KB rather than 480 KB of needless blur or 510 KB of rejection.
The one situation that needs care is a fresh-from-camera photograph. Full-resolution phone photos are simply bigger than 500 KB, so something has to give. The engine gives up bytes in the least visible order: first encoder quality, in small steps; then, only if it must, dimensions in gentle steps. The result is the largest-looking image that fits, not the first preset that fit.
Getting the most from the budget
- Do not resize by hand first. At 500 KB, hand-resizing is the most common way to throw away quality you could have kept. Let the engine fit the budget; resize only when the form names pixel dimensions too.
- Screenshots and diagrams: keep them PNG. Text and flat UI survive PNG palette quantization beautifully, while JPG develops fuzz around every letter. A quantized PNG screenshot at this budget is usually indistinguishable from the original.
- Photographs: WebP or AVIF when allowed. Where JPEG needs 500 KB, WebP often needs about 350 KB for the same look — the surplus buys either smaller files or visibly more detail. If the portal demands JPG, the engine simply spends the whole budget on quality.
- Batches: drop them all at once. Every file gets the same 500 KB treatment in parallel and comes back as individual downloads or one ZIP.
Other budgets in one place
Other limits come with their own page: compress an image to 50 KB for passport and signature uploads, compress an image to 100 KB for the most common general cap, and compress an image to 200 KB for university forms. If your goal is not size but privacy — stripping the GPS location a phone photo carries before you post it — use remove GPS from a photo. Any other number works the same way: type it into the target field, or open the main compressor for the full auto mode.
Frequently asked questions
Can I compress an image to exactly 500 KB?
Yes — pick Target size and enter 500. The engine binary-searches encoder quality until the output fits under 500 KB, and reports the real byte count of the finished file rather than an estimate.
Will a 500 KB photo look bad?
No. 500 KB is a generous budget: almost any phone photo up to about 12 megapixels fits at full resolution with quality to spare. Only very large, very detailed images need downscaling, and the engine reduces dimensions in gentle steps rather than one jump.
What is the 500 KB limit usually for?
It is the common cap on job application and ATS portals, marketplace and classified listing photos, CMS and LMS media libraries, and email attachment policies that allow a few images per message. The number varies, but 500 KB is the most frequent ceiling once a form outgrows the classic 100–200 KB caps.
Should I resize the image before compressing to 500 KB?
Almost never. At a 500 KB budget most images fit on quality alone, so leave the resolution alone and let the engine preserve every pixel. Resize by hand only when the form also names pixel dimensions.
Can I compress a whole batch to 500 KB each?
Yes. Drop in as many files as you like — every one is compressed to the same 500 KB budget in parallel, and you can download them individually or as a single ZIP archive.
Are my images uploaded to a server?
No. This is a static site with no upload endpoint. Your images are decoded, resampled and re-encoded inside your own browser, so they cannot leave your device even by accident.