What Image Compression Quality Should You Use?

See what common quality settings change, where artifacts appear, and how to choose a practical quality level for web images.

On this page13 sections
  1. What a quality slider means
  2. Codec differences
  3. 60/70/80/90
  4. Photos vs screenshots
  5. When to stop
  6. Testing workflow
  7. Worked example: optimize from the destination backward
  8. Practical takeaway
  9. Try it on a real image
  10. Continue reading
  11. Frequently asked questions
  12. Editorial note
  13. Sources and further reading

A useful answer to image compression quality settings starts by separating pixel dimensions, encoded bytes, format, and visual quality. Those variables interact, but they are not interchangeable; changing the wrong one can make the file smaller while making the image or the page worse.

Quality values are not standardized across codecs or encoders. “80” in one JPEG encoder is not mathematically equivalent to “80” in WebP, AVIF, or even another JPEG implementation.

Judge quality at the final display size. Zooming to 800% can reveal differences that a real visitor will never see, while hiding an image in a tiny preview can conceal ringing or block artifacts that become obvious on the live page.

Short version: Start with the image’s actual job, remove waste the layout cannot use, encode once from a good source, and verify the result in the real page. Smaller is useful only while the image remains visually and technically fit for purpose.

Starting point What to expect Good use What to inspect
90 Conservative, usually subtle loss Hero/product images where detail matters Whether the saving is large enough to justify re-encoding
80–85 Strong general web starting range Most editorial/product photos Fine texture, hair, foliage, edge ringing
65–75 More aggressive Thumbnails and low-prominence imagery Gradients, skin texture, text inside images
60 and below Deliberately aggressive Cases where bytes matter more than fidelity Blocking, smearing, banding, halos

These are testing ranges, not standards. Codec and encoder implementations differ.

What a quality slider means

A quality control is an encoder instruction, not a universal percentage of “original quality.” Different codecs and libraries map the number differently. Treat it as a tuning control and evaluate the output instead of attaching absolute meaning to the number.

Look for the artifacts that matter for the content: blocking in flat regions, ringing around edges, smearing of fine texture, color shifts, banding in gradients, or text that becomes harder to read. Stop lowering quality when the saving no longer justifies the visual cost.

Applied to image compression quality settings: start with a visually conservative encode, then step down until you can identify a repeatable defect at normal viewing size. If the next step saves only a small amount but makes hair, foliage, lettering, or gradients visibly worse, the previous setting is the better delivery choice.

Codec differences

This part of image compression quality settings is best understood as a trade-off rather than a fixed rule. The right choice depends on the visual role of the image, the publishing environment, and what happens to the file after it leaves the editor.

Use representative files and verify the result in the real destination. A workflow that looks good on one sample can fail on transparency, fine text, gradients, noisy photographs, or very large source dimensions.

60/70/80/90

A quality control is an encoder instruction, not a universal percentage of “original quality.” Different codecs and libraries map the number differently. Treat it as a tuning control and evaluate the output instead of attaching absolute meaning to the number.

Look for the artifacts that matter for the content: blocking in flat regions, ringing around edges, smearing of fine texture, color shifts, banding in gradients, or text that becomes harder to read. Stop lowering quality when the saving no longer justifies the visual cost.

Photos vs screenshots

This part of image compression quality settings is best understood as a trade-off rather than a fixed rule. The right choice depends on the visual role of the image, the publishing environment, and what happens to the file after it leaves the editor.

Use representative files and verify the result in the real destination. A workflow that looks good on one sample can fail on transparency, fine text, gradients, noisy photographs, or very large source dimensions.

When to stop

This part of image compression quality settings is best understood as a trade-off rather than a fixed rule. The right choice depends on the visual role of the image, the publishing environment, and what happens to the file after it leaves the editor.

Use representative files and verify the result in the real destination. A workflow that looks good on one sample can fail on transparency, fine text, gradients, noisy photographs, or very large source dimensions.

Testing workflow

Use a repeatable order instead of random tweaking: start from the best source, remove dimensions the layout cannot use, select a format that fits the content, choose a conservative quality level, inspect the result, and only then push harder if the remaining bytes matter.

After publishing, measure the real page. Optimization is complete when the resource fits the visual requirement and the page performs well—not when a standalone tool reports the smallest number you can produce.

Worked example: optimize from the destination backward

For image compression quality settings, imagine a 24-megapixel camera photo being used inside an article whose largest image slot is roughly 1,000 CSS pixels wide. The original may be several thousand pixels across. Before arguing about whether quality should be 78 or 82, decide which source widths the layout can actually use—for example a small mobile candidate, a mid-size candidate, and a larger high-density candidate.

Now encode those candidates from the master rather than repeatedly compressing an already compressed derivative. Compare JPEG, WebP, or AVIF only where the workflow supports them. Inspect the largest candidate at normal size, then check a crop containing fine detail and a smooth gradient. This process answers image compression quality settings with evidence from the real asset instead of a generic quality recipe.

Practical takeaway

For image compression quality settings, make one decision at a time and verify it in the final destination. Use the page’s actual dimensions, content type, compatibility needs, and user-visible result as the constraints. The goal is not to win a synthetic file-size contest; it is to publish an image that is efficient, understandable, and reliable for its job.

Try it on a real image

Use the compressor to apply this article to a real source image. Start at 82, then compare The image operation runs in your browser, which makes it practical to compare dimensions, format, output bytes, and visual quality without first sending the selected image to a remote compression endpoint.

Continue reading

Frequently asked questions

Is 80% quality good?

Use visual inspection at the intended display size. Quality controls differ across encoders, so there is no single numeric value that is optimal for every image and format.

What JPEG quality is best for web?

Use visual inspection at the intended display size. Quality controls differ across encoders, so there is no single numeric value that is optimal for every image and format.

What WebP quality should I use?

Use visual inspection at the intended display size. Quality controls differ across encoders, so there is no single numeric value that is optimal for every image and format.

Why does quality 100 still compress?

Use visual inspection at the intended display size. Quality controls differ across encoders, so there is no single numeric value that is optimal for every image and format.

Editorial note

Image formats, browser behavior, WordPress media support, and search guidance can change. This article is written to distinguish durable principles from version-specific behavior; version-sensitive claims should be rechecked during scheduled content refreshes.

Sources and further reading

Continue the series8 parts

Image Compression Fundamentals

  1. Image Compression: The Complete Guide
  2. How to Compress Images Without Losing Visible Quality
  3. Lossy vs Lossless Image Compression
  4. What Image Compression Quality Should You Use?
  5. Resize vs Compress Images: What Changes?
  6. How to Batch Compress Images Without Uploading Them
  7. Why Can a Compressed Image Be Larger Than the Original?
  8. Does Image Compression Reduce Resolution?