Compress an image to an exact file size.
Set the limit the form asks for — 100 KB, 200 KB, 1 MB — and get a file that actually fits. Everything runs in your browser, so your photos are never uploaded anywhere.
Drop images here
or browse your files — JPG, PNG, WebP. Paste works too.
Output will be at or below this size.
WebP is usually 25–35% smaller.
Caps the longest side. Leave empty to keep the original size.
Compression happens on your device. Files are never sent to a server.
How it works
-
01
Your image is decoded locally
The browser reads the file straight from disk into memory. Nothing is transmitted — open DevTools and check the network tab if you want proof.
-
02
Quality is searched, not guessed
The encoder runs a binary search across quality levels, keeping the highest setting that still lands under your target size.
-
03
Dimensions drop only if they must
If even the lowest usable quality overshoots, the image is resized down step by step. Sharp at a smaller size beats mush at full resolution.
-
04
You get an exact number
The result shows original size, final size and the reduction, so you can confirm it fits before uploading it to whatever demanded the limit.
Questions
Are my images uploaded to a server?
No. Compression runs locally in your browser using the Canvas API. Your files never leave your device and nothing is stored or logged. You can load the page, disconnect from the internet, and it will still work.
Will the output really be under the limit?
Yes. The tool searches encoder quality for the highest setting that still fits your target. If quality alone is not enough, it reduces the image dimensions step by step until the file fits. If a target is physically impossible, it tells you the smallest size it could reach rather than silently handing back a file that is too large.
JPEG or WebP — which should I pick?
WebP is usually 25–35% smaller at the same visual quality and is supported by every current browser. Pick JPEG when the receiving system is old or explicitly asks for a .jpg file, which many government forms and job portals still do.
Why does a very small target make my photo look soft?
A tiny budget forces the encoder to throw away detail. For documents or faces, it looks better to reduce the dimensions and keep quality high than to keep full resolution and crush quality. The tool switches to that strategy automatically once quality alone stops being enough.
Does it work with iPhone HEIC photos?
Safari decodes HEIC natively, so it works there. Chrome and Firefox cannot decode HEIC; the tool detects this and tells you what to do instead of failing silently. The quickest fix is to export the photo as JPEG first, or on iPhone set Settings → Camera → Formats → Most Compatible so new photos are saved as JPEG.
Is there a limit on how many files I can process?
The tool imposes none. Everything happens in your browser's memory, so a very large batch on a phone may be slow. A few dozen at a time on mobile, more on a desktop, is comfortable.