Compress to a target size, not a guessed quality
Most compressors give you a quality slider and leave you to guess. That is backwards: what you actually know is the limit you have to fit — a 500 KB upload cap, a 100 KB form field, a 20 KB profile picture. This tool starts from that number and works out the quality and resolution that get you there.
It searches from the largest, sharpest settings downwards: full resolution at the highest quality first, then progressively lower quality at the same size, and only then a smaller image. The first combination that fits your target wins, so you always get the best-looking file that still meets the limit.
How to compress an image to a target size
- 1
Drop your images in
Add up to 20 files at once — JPG, PNG, WebP or AVIF, each up to 50 MB. Everything is processed on your own device, so nothing is uploaded.
- 2
Pick your target
Choose a preset from the dropdown — 1 MB, 500 KB, 200 KB, 100 KB, 50 KB or 20 KB — the same limits upload forms actually ask for.
- 3
Download the result
The tool finds the highest quality that still fits and shows you the exact file size before you save. One click downloads the finished image.
Common targets
How the quality and dimension search works
Compression is a search, not a setting, and the search runs from the best possible result downwards. Full resolution at the highest quality is tried first. If the file is still over the target, the quality comes down in steps and the size is measured after every attempt. Only when quality alone can no longer close the gap are the pixel dimensions reduced as well — and the first combination that fits wins, so nothing ever comes out softer than it had to be.
The order is not arbitrary. Most of the saving in a JPEG comes from the first drop in quality; past roughly quality 40 the extra bytes saved are paid for with visibly blocky edges, and from there removing pixels gives a cleaner picture for the same size. That is why a 20 KB result is usually a smaller image rather than a badly encoded large one, and why the same photo at 1 MB keeps its original dimensions.
What this tool will not do
It will not invent detail. A photo that a chat app or a social network already compressed has less information left to squeeze, so the result can be worse than compressing the untouched original would have been — start from the largest version you have.
It will not remove a watermark, add resolution, or change what is in the picture. The output is the same image at a lower quality, a smaller pixel count, or both.
And it will not pretend. When a source genuinely cannot be squeezed under the target without falling apart, the file is marked with a note instead of being silently served at the wrong size, and the smallest result the tool could produce is offered instead.
Frequently asked questions
Is my image uploaded to a server?
No. The compression runs inside your browser using the Canvas API and a Web Worker, so the file you pick never leaves your device. There is no copy of it on our side to store, leak or sell.
How do I compress an image to an exact size, like 100 KB?
Choose a target from the dropdown above — or open a size-specific page such as /image/compress-to-size/100kb/. The tool then lowers the encoding quality, and if that is not enough it also scales the image down, until the result fits under your target. The exact size of every file is shown before you download it.
Will the image look worse?
The tool always keeps the highest quality that still fits your target: it first tries the maximum quality at full resolution, and only reduces dimensions when quality alone cannot reach the target. That is why the same photo compresses better here than with a fixed-quality slider that makes you guess.
Which image formats can I use?
JPG, PNG, WebP and AVIF. Your JPG stays a JPG. PNG and AVIF inputs are written out as WebP, because PNG has no quality setting — WebP is the only way to hit a target size while keeping transparency intact.
Is there a limit or a watermark?
No watermark, no account, no daily quota. You can add up to 20 images at a time and each one can be up to 50 MB. Because the work happens on your own device, there is no per-file cost that would force a limit.
Does it work on a phone?
Yes — the tool is a normal web page and works in the browser on iOS and Android. Photos picked from the camera roll are processed on the device itself, which also avoids burning mobile data on an upload.
Does it work with HEIC photos from an iPhone?
Not directly — this tool reads JPG, PNG, WebP and AVIF. A HEIC file straight from an iPhone camera has to be turned into a JPG first, and the HEIC to JPG converter does exactly that, in the same browser-based, no-upload way. On the phone itself, setting the camera to "Most Compatible" also makes it produce JPG files from then on.
What if the size I need is not one of the presets?
Choose the next preset below your limit. The sizes offered — 1 MB, 500 KB, 200 KB, 100 KB, 50 KB, 20 KB — are the ceilings that forms, marketplaces and CMS fields actually enforce, and landing at 180 KB when a form asked for 200 KB is always safe. Working a quality slider until the number happens to fit is slower and less reliable, because the same slider value gives a different file size for every photo.
Can different images in one run have different targets?
No — one target applies to the whole batch, because the point of the tool is to satisfy a single limit. If two destinations demand different ceilings, run it twice; each run happens on your own device, so a second pass costs nothing but a moment.