The tier where compression stops being a trade-off
Below a few hundred kilobytes, compression is a negotiation — you're trading detail for file size, and it shows if you push too far. At 1MB, that negotiation mostly disappears. Most photos reach a quality setting in the 75–90% range to hit a 1MB target, well above where JPEG artefacts start to show up even under close inspection. You're not choosing between "small" and "good" here; you're mostly just removing bytes the original file was storing inefficiently.
Where a 1MB target actually helps
| Situation | Why 1MB fits |
|---|---|
| Print submission portals | High enough quality for print, well under most upload ceilings |
| Portfolio or design showcase | Near-original detail, faster page loads than the source file |
| Archiving a large photo library | Meaningful storage savings with essentially no visible loss |
| Sharing full-resolution photos by email | Clears most attachment limits without a visible quality hit |
1MB versus the smaller targets on this site
The other compression pages here (100KB, 200KB, 500KB) exist because some form or platform enforces that exact ceiling and you have no choice but to hit it. 1MB is different: nothing is usually forcing you down to this number specifically. Reach for it when you want a smaller, faster-loading file but quality is the priority — not a hard limit you're racing to clear.
Format choice matters least here
At smaller targets, WebP's efficiency advantage over JPEG is the difference between visible and invisible compression. At 1MB, both formats usually have enough room that the choice comes down to compatibility instead: use JPEG for anything going to a system you don't control, and WebP only when you're certain the destination supports it and want to squeeze out the last bit of sharpness.
What if quality search alone can't reach 1MB
For most photos this won't happen, since 1MB is a generous target. If it does — typically with very large, highly detailed originals — the tool falls back to scaling the image down, but never below the minimum width field. Raise that number if you want to guarantee a certain resolution regardless of file size, or lower it to give the compressor more room to work with.
Nothing is uploaded to do this
Decoding, the quality search, and re-encoding all happen inside your browser via the Canvas API. The photo is never sent to a server, so there's no queue, no daily limit, and no size cap beyond your own device's memory. Re-encoding through a canvas also strips EXIF metadata — camera model, GPS coordinates, timestamps — from the result automatically.