Compress images
Drag the divider to see exactly what you're giving up before you commit. Set a quality level, or name a file size and let the tool find the best quality that fits under it.
Compression
75–85 suits most photographs. Below 65, skies and hard edges start to block up.
The tool tries several quality levels and keeps the best one that fits underneath.
WebP is typically 25–35% smaller than JPEG at the same visual quality.
Usually the biggest saving available. A 4000 px photo shown at 1000 px is carrying 16× the pixels it needs.
Result
- Original
- —
- Compressed
- —
- Saved
- —
- Quality used
- —
- Pixels
- —
Related tools
Drop images here
or · add a batch and compare them one at a time
Before and after
Drop an image above and it appears here split down the middle — original on the left, compressed on the right. Drag the divider to compare.
Queue
Files you add appear here. Select any row to preview and fine-tune it on its own.
Where the kilobytes actually go
People reach for the quality slider first, but it's rarely the biggest lever. File size scales with the number of pixels, so a photo that's 4000 px wide carries four times the data of the same photo at 2000 px — before compression does anything at all. If an image is going to be displayed at 800 px on a page, shipping it at 4000 px wastes roughly 96% of what you're sending, and no quality setting will claw that back.
The practical order is: resize to the size it will actually be displayed at, then choose a modern format, then tune quality last. That sequence routinely takes a 6 MB phone photo to under 150 KB with no visible difference on screen.
Reading the comparison honestly
The divider view is showing you both images at whatever size fits your screen, which is usually smaller than full resolution. Compression damage hides at reduced size and reappears when someone zooms in or prints. If the image matters, check it at 100% before you commit, and pay particular attention to three places: smooth gradients like skies, where banding shows first; hard edges against flat colour, where you'll see a halo; and areas of fine repeated detail like foliage or fabric, which turn mushy.
Lossy, lossless, and why re-saving hurts
JPEG, WebP and AVIF are lossy: they discard information the eye is unlikely to miss, and they can't get it back. Each time you open and re-save a lossy file, the encoder makes fresh guesses about data that was already an approximation, and errors accumulate — the same way a photocopy of a photocopy degrades.
Keep your originals somewhere untouched and compress a copy. If you need to make another edit later, go back to the original rather than re-compressing the compressed version.
A note on PNG
PNG is lossless, so there's no quality dial to turn — the only ways to make one smaller are to reduce its dimensions, reduce its colour count, or stop using PNG. For photographs, converting to WebP is usually a saving of 80% or more. For screenshots, logos and diagrams, PNG is genuinely the right format and is already close to as small as it gets. That's why this tool defaults to WebP output when you feed it a PNG.
What quality number should I use?
Start at 80 and look at the comparison. For photos destined for a website, most people can't pick 80 from the original at normal viewing size. Drop to 70 if size matters more than fidelity, and stay above 85 only when the image will be printed or examined closely.
Target size mode says it couldn't reach my limit. Why?
Because even at the lowest quality the encoder can't fit that many pixels into that many bytes. Turn on the longest-edge limit and try again — reducing dimensions frees up far more room than quality alone.
Will compressing repeatedly make a file smaller each time?
Slightly smaller and noticeably worse. Every pass throws away more detail while the format's overhead stays put, so you lose quality much faster than bytes. Compress once, from the original.
Does this keep my photo's EXIF and GPS data?
No. The image is redrawn from raw pixels, so all metadata is dropped from the output. If you want to inspect what was in there first, use the metadata tool before compressing.
Why is AVIF sometimes missing from the list?
Because your browser can't write AVIF, even if it can display it. Encoding support is still uneven, so the option is hidden rather than silently handing you a mislabelled file.