There's no single universal answer to how much compression an image can take before it starts looking bad — it depends heavily on the specific photo, the format, and how closely someone's actually looking. There are, however, some genuinely useful general patterns worth knowing. There's ultimately no shortcut that fully replaces actually looking carefully at the finished result before publishing it, since every image and every use case carries its own specific tolerance for compression.

General quality ranges worth knowing

  • 90–100% quality: visually indistinguishable from the original for almost any image, with only modest file-size savings.
  • 70–85% quality: the commonly recommended sweet spot for web photos — meaningful file-size reduction with little to no visible quality loss for most images.
  • 50–70% quality: noticeable file-size savings, with quality loss becoming visible on close inspection for many images, though often still acceptable for less prominent use.
  • Below 50%: visible artifacts (blockiness, color banding, blurred fine detail) become common across most images, generally not recommended except for thumbnails or genuinely space-constrained situations.

Why the same setting affects different images differently

An image with smooth gradients and few sharp edges (a sunset, a softly blurred background) tolerates aggressive compression far better than an image full of fine detail and sharp contrast (text, intricate patterns, busy textures). The same 60% quality setting that looks perfectly fine on one photo can produce clearly visible blocky artifacts on another, which is why a universal "safe" percentage doesn't really exist — it has to be judged per image.

How to find the right balance for a specific image

The most reliable method is a visual side-by-side comparison at a couple of different quality settings, viewed at the actual size the image will be displayed — quality problems that are obvious at 100% zoom are sometimes completely invisible once an image is shown at its normal, smaller display size on a page. Starting around 80% quality and adjusting down while checking for visible artifacts is a practical, reliable process that works regardless of the specific image content.

Signs that compression has gone too far

Blockiness (visible square patches, especially in smooth areas like skies or skin tones), color banding (visible stepped transitions instead of smooth gradients), and a general "smeared" loss of fine detail are the classic signs of over-compression. Any one of these appearing at the image's actual display size, not just when zoomed in, is a reliable signal to back off the compression level rather than push it further for marginal additional file-size savings.

Why thumbnails can tolerate much more aggressive compression

An image displayed very small — a thumbnail, a small preview icon — can generally tolerate significantly more aggressive compression than the same image would at full display size, simply because there are fewer displayed pixels for artifacts to become visible in. This is why many sites apply a much lower quality setting specifically to thumbnail versions of an image while keeping a higher-quality setting for the full-size version people click through to, rather than using one uniform compression level for every size an image appears at.

Try the image tool yourself — free, instant, no upload to any server.

Open the tool

Frequently asked questions

Is there a single safe compression percentage that works for every image?

No. The right level depends on the specific image's content — smooth, low-detail images tolerate much more aggressive compression than busy, detailed ones before quality loss becomes visible.

Should I judge compression quality while zoomed in or at normal display size?

At normal display size, ideally the actual size the image will be shown at on its final destination — artifacts that are obvious when zoomed in are often completely invisible at typical viewing size and distance.

What's the most common visible sign that an image has been over-compressed?

Blockiness in smooth areas (like skies or skin tones) and visible color banding in gradients are usually the first and most noticeable signs, appearing before more severe detail loss becomes obvious. Building this quick visual check into a regular publishing habit, rather than treating it as an occasional special step reserved for important images only, tends to catch over-compression consistently across an entire body of published work, not just when something happens to stand out.