Image Compressor
Make pictures small enough to send
Cut JPG, PNG, WebP and AVIF file size with a live before/after view and a quality dial you actually control.
Image Compressor
Runs in your browser · nothing uploaded01 — How to use Image Compressor
02 — Getting good results
03 — Questions
No. Every image is decoded, resized and re-encoded entirely inside your browser tab, in a background worker. Nothing is sent anywhere at any point — there is no upload step for this tool to have, and no network request happens while a file is compressed.
JPG, PNG, WebP and AVIF can be dropped in, and any of those four can be chosen as the output format regardless of what you started with — so a batch of mixed PNGs and JPEGs can, for example, all be converted to WebP in one pass.
The saving you get depends on the source image, not a fixed rate. A photo straight off a camera or an uncompressed screenshot usually shrinks a great deal; an image that has already been compressed elsewhere, or a simple graphic saved as PNG, may barely shrink at all — resizing or switching format tends to help more in that case than lowering quality further.
No. Compressing an image here means redrawing it and re-encoding the result, and that process does not carry metadata through — EXIF (camera, date, GPS data), ICC colour profiles and any other embedded metadata in the original file are all dropped. If you need to preserve that information, keep the original file alongside the compressed one.
04 — More about Image Compressor
How lossy compression actually works
A lossy image codec does not store an image pixel-for-pixel. It transforms blocks of pixels into a frequency representation, keeps the parts of that representation the human eye is most sensitive to, and discards or coarsens the rest. The quality setting controls how aggressively that discarding happens: a high quality keeps most of the detail and produces a large file; a low quality throws more away and produces a small one, at the cost of visible artefacts once enough detail is gone. This is why the same slider produces very different results on different images — a busy, detailed photo has more high-frequency information to lose than a smooth gradient does.
Choosing a format
JPEG is the oldest and most universally supported lossy format, and remains a safe default when compatibility matters most. WebP generally reaches a smaller file than JPEG at equivalent visual quality, and adds transparency support that JPEG lacks. AVIF, based on a newer video codec, can compress further still at low-to-medium quality, though support for opening AVIF files is less universal than WebP's. PNG is lossless — it never discards detail — which is exactly why it is the right choice for flat-colour graphics and the wrong choice for photographs, where its files can run many times larger than a lossy equivalent.
Quality versus file size is not a straight line
Pushing the quality dial down does not save file size at a constant rate. Near the top of the range, small reductions in quality barely move the file size, because there is little redundant information left to remove. Further down, the same size reduction in the slider removes proportionally more, and visible artefacts appear more quickly. That is why a moderate setting around 75–85 tends to sit in the useful part of the curve for photographs: enough of the detail the codec would discard is genuinely redundant, so the size drops noticeably before quality loss becomes obvious.
When to resize instead of just compressing
Quality and resolution are two separate levers, and they are not interchangeable. Compressing harder keeps every pixel but represents each one less precisely; resizing removes pixels outright. When an image is going to be displayed smaller than its original size — a thumbnail, an inline web image, an email attachment — resizing down to roughly the size it will actually be shown at removes information that was never going to be visible anyway, before compression even gets involved. That combination, downscale first and then compress at a moderate quality, generally beats compressing the full-size original harder to hit the same target file size.
61 more tools
where this came from.
Same shell, same shortcuts, same promise: nothing leaves your browser.