Image compression has a sweet spot, and most people miss it from both sides: photos uploaded untouched at 8 MB, or crushed to visible mush by a quality slider dragged to 40. The honest middle ground keeps files small and eyes happy, and finding it takes one principle and one habit. This guide covers both, plus the resize step that often saves more than compression itself, using our free image compressor, which runs in your browser with no upload.
In this guide
What lossy compression actually throws away
Lossy formats like JPEG and lossy WebP exploit how human vision works: we notice brightness more than color detail and broad shapes more than fine texture. The encoder keeps what eyes prioritize and discards what they gloss over, which is why a photo can lose most of its bytes before it loses any visible quality. The discarding is permanent, every save re-decides what to keep, and the decisions are controlled by one number: the quality setting. The full lossy-versus-lossless picture lives in our image formats pillar; this guide is about using the slider well.
The quality sweet spot
For photographs, the practical JPEG and WebP quality range is 75 to 85. Above 85, file size climbs steeply while visible quality barely moves; the step from 85 to 100 can double the bytes for a difference no one can point to. Below about 75, artifacts start appearing in the places that show them first, smooth skies, skin, and sharp edges. The professional default is to start at 80, look at the result at full size, and only move if something looks wrong. Our quality adjuster makes the experiment cheap: same image, several settings, judge with your own eyes, and you will land in the same 75-to-85 zone the industry uses.
Resize first: the bigger win
The most effective compression is often not compression at all. A modern phone photo is around 4,000 pixels wide; a blog column, chat window, or marketplace listing displays perhaps 800 to 1,600. Sending the full resolution means shipping pixels nobody will ever see, and no quality slider fixes that, because the waste is in dimensions, not encoding. Downscaling a 4,000-pixel photo to 1,600 cuts the pixel count by a factor of six before any quality decision is made, and a downscale plus quality 80 routinely turns 8 MB into a few hundred kilobytes with no visible cost at the displayed size. The order matters: resize first, then compress, with the resizing trade-offs covered in the downscale tool.
How to spot over-compression
Three artifact families, and where to look for them:
- Blocking: faint 8-pixel squares in smooth areas, skies and shadows first. The classic sign the quality went too low.
- Ringing: ghostly halos along sharp edges, text, logos, branches against sky. This is also why screenshots and graphics belong in PNG or lossless WebP, not JPEG.
- Banding: smooth gradients turning into visible stripes, sunsets being the universal victim.
Judge at 100% zoom on the parts that matter; thumbnails hide everything. And never re-compress a compressed image repeatedly: each lossy save discards again, the photocopy-of-a-photocopy effect, so keep the original and derive every export from it.
When the format is the fix
At the same visible quality, WebP files run meaningfully smaller than JPEG, which is free savings when the destination supports it, and every current browser does. Photos heading to the web are the prime case: convert and compress in one move with the WebP compressor, and see our WebP guide for the format’s full story. The counter-cases are real too: JPEG remains the safe bet for maximum compatibility (old software, print shops, government portals), the reason iPhone photos so often make the HEIC to JPG trip, and graphics with text, sharp lines, or transparency want PNG or lossless WebP, where “compression” means a different, lossless mechanism and the quality slider does not apply.
Frequently asked questions
Is quality 100 the same as lossless?
No. JPEG at 100 still runs the lossy pipeline, just gently; detail is still discarded. If pixel-exact preservation matters, use a lossless format rather than a generous slider.
Why did my image get bigger after compression?
Usually one of two reasons: the source was already compressed harder than your new setting, or it was a graphics-style image where JPEG fights the content. Compressing a quality-60 file at quality 90 re-encodes mush at a generous bitrate, the worst of both worlds.
What is the right size for email attachments?
Resize to about 1,600 pixels on the long edge and quality 80, which lands typical photos in the 200 to 500 KB range, comfortable for any inbox and indistinguishable on screen from the original.
Does compressing remove the photo’s metadata?
Re-encoding often strips or reduces EXIF metadata, but do not rely on a side effect for privacy: check with an EXIF viewer and strip deliberately when it matters, especially GPS coordinates.