Every time a JPEG image is saved, it loses a little quality. Compress it again and it loses more. Pass an image through WhatsApp, download it from a post, re-upload it to another platform — each step compounds the damage. At some point the image is so far from the original that no amount of further processing can fix it. Knowing when that point has been reached saves you from wasting time on something that can't be recovered.
Visual signs of over-compression
JPEG compression artifacts have a distinctive look once you know what you're looking for:
- Blocking. The image appears to be made of visible 8×8 pixel squares, especially in smooth areas like skies, skin tones, or plain backgrounds. This is the most obvious sign of heavy JPEG compression.
- Ringing. A halo-like fringe appears around sharp edges — dark halos around light objects, light halos around dark ones. Text baked into an image often shows this clearly.
- Color banding. What should be a smooth gradient (like a sunset sky) shows visible steps or bands of color rather than a continuous transition.
- Loss of fine texture. Fabric, hair, foliage, and similar high-frequency detail look smeared or mushy rather than sharp.
These artifacts are most visible when you zoom in to 100% (one screen pixel = one image pixel). At reduced zoom, they can be hidden by your screen's own downsampling.
The file size test
A heavily compressed image is often smaller than it "should" be for its pixel count. A rough benchmark: a typical phone photo at 3000×4000 pixels that looks good should be at least 1.5–3 MB as a JPG at normal quality. If the same-sized image is only 150–300 KB, it's been through significant compression. This isn't definitive — some images genuinely compress well — but combined with visible artifacts, small file size relative to pixel count is a tell.
What you can (and cannot) fix
Compression artifacts cannot be reversed. Once the data that was discarded is gone, it's gone. Compressing a damaged image less aggressively doesn't recover the lost quality — it just stops adding new damage.
What you can do with a heavily compressed image:
- Use it as-is if the quality is acceptable for the purpose. A 72 KB profile photo that looks fine at thumbnail size doesn't need to be "fixed."
- Apply a mild sharpening pass in an image editor — this won't recover lost detail but can make the image look slightly crisper by enhancing the edges that remain. Don't over-sharpen, as this makes the ringing artifacts more prominent.
- Upscale with AI — tools like Topaz Gigapixel, Real-ESRGAN, or several browser-based tools use neural networks trained specifically to reconstruct likely image detail. The results are surprisingly good at hiding compression artifacts, though they invent rather than recover the lost information.
- Go back to the original source. This is the only real fix. Find the original file before it was compressed — the camera roll, the original email, the RAW file — and start from there.
How to avoid this problem in the first place
- Save your originals in a lossless format (PNG or RAW) or at high JPEG quality (90%+) as the archival copy. Work from that, not from a shared or downloaded version.
- Don't save a JPEG, edit it, and save it again repeatedly. Each save-edit-save cycle adds a generation of compression loss. Do all edits in one session and export once.
- Download images from the highest-quality source available. "Right-click, save image" from a compressed web thumbnail isn't the original.