Updated: August 1, 2026
Short answer: Quality 80 is often a practical web starting point; quality 90 keeps more information and usually costs more bytes. Export both from the same source and choose the smaller candidate that still preserves the details your audience needs.
The difference between JPEG quality 80 and 90 is real, but it is not a fixed percentage of file size or a universal visual rule. The output depends on the source, dimensions, encoder, chroma subsampling, metadata, and how large the image is displayed.
The Fair Comparison
Hold these variables constant:
| Variable | Keep constant because |
|---|---|
| Original source | An already-compressed source can make one export look worse before the test begins |
| Pixel dimensions | A smaller image is not evidence that a quality setting is better |
| Encoder and version | Different encoders map quality values differently |
| Chroma subsampling | More or less color detail changes text and edge quality |
| Metadata policy | Extra EXIF can make a file larger without changing visible pixels |
| Viewing context | A difference at 100% may not matter at a 400px display size |
Export both candidates from the clean master. Do not export quality 90 from the original and quality 80 from an earlier JPEG.
What Usually Changes From 80 to 90
Quality 90 generally retains more high-frequency detail and creates a larger file. The visual benefit tends to be more noticeable in:
- fine product texture;
- hair, foliage, fabric, and noisy scenes;
- large images viewed close to 100%;
- smooth gradients where banding is visible;
- saturated edges when chroma is preserved.
The benefit may be difficult to see in a small card image, a soft background, or a correctly sized blog photo. That is why the rendered context matters.
web.dev’s JPEG guide describes quality as a content-dependent judgment rather than a setting with one guaranteed result.
A Practical Test Workflow
- Start with the clean master.
- Resize both candidates to the same largest useful display dimensions.
- Export one at quality 80 and one at 90 in the same encoder.
- Keep metadata policy and chroma options the same.
- Record exact bytes and output dimensions.
- Compare at 100% and at the actual CSS size.
- Check the uploaded or CDN-delivered copy.
Pick quality 80 when the important details look the same and the smaller file improves the delivery budget. Pick 90 when 80 damages detail users need, and the extra bytes are justified. If both fail, revisit dimensions, format, or the source rather than simply choosing a higher number.
Use Case Examples
| Use case | Likely starting test | Why |
|---|---|---|
| Blog photo at moderate width | 80, then 85 if needed | readers usually view it below 100% |
| Product image with zoom | 85–90 plus a separate master | labels and material texture matter |
| Portfolio case study | compare 85 and 90 at full display | gradients and fine craft may justify bytes |
| Email image | 75–85 at email dimensions | clients may resize or recompress |
| Screenshot | PNG/WebP before JPEG 80/90 | text edges expose JPEG artifacts |
| Print master | do not use either as the master | retain an original/high-quality source |
These ranges are starting experiments, not promises. Your representative files should decide.
Quality 80 vs 90 and Responsive Delivery
The better JPEG setting cannot compensate for sending too many pixels. Generate responsive widths and let the browser choose with srcset and sizes. Google’s image SEO guidance recommends responsive image practices, and web.dev’s guide explains the mobile bandwidth benefit.
<img
src="case-study-1200.jpg"
srcset="case-study-480.jpg 480w, case-study-800.jpg 800w, case-study-1200.jpg 1200w"
sizes="(max-width: 700px) 100vw, 800px"
width="1200"
height="800"
alt="A finished wooden chair in a studio"
/>
Set width and height or an aspect ratio to reserve layout space; web.dev’s CLS guidance explains the layout-stability reason.
Metadata and Chroma Can Confuse the Result
If the quality 90 file is much larger, check whether it also kept a thumbnail, GPS data, or an embedded editing profile. If quality 80 looks blurry around colored text, check chroma subsampling before concluding that the quality number is the problem.
For a screenshot, try PNG or WebP. For a transparent image, JPEG is not an option because it cannot preserve alpha. For a photo, JPEG remains a useful compatibility baseline even when WebP or AVIF produces a smaller candidate.
Avoid Re-encoding the Last Export
If quality 80 is too small and you want a better version, export quality 90 from the master. Do not open the quality 80 file and save it at 90; the missing information cannot come back, and a second lossy pass may add artifacts.
How to Make the Decision
Choose 80 when:
- the image is a normal web photo;
- the display is modest;
- the important details look clean;
- the byte saving supports faster delivery.
Choose 90 when:
- fine detail is visibly damaged at 80;
- the image is large or zoomable;
- product, portfolio, or brand detail earns the extra bytes;
- the destination accepts the larger file.
Choose neither when:
- dimensions are wrong;
- a screenshot needs PNG/WebP;
- the image must remain lossless;
- a platform will immediately transform the file.