benchmark · WebP quality benchmark

WebP Quality Benchmark

WebP quality settings often give a useful size drop before visible artifacts become obvious.

Benchmark notes

  • Quality 80 was 346 KB.
  • Quality 70 reduced the sample to 249 KB.
  • Quality 50 reached 163 KB and needs close review.

WebP quality results

QualityOutput sizeChange from q90Useful first testCaution
90550 KBBaselineNear-source web exportCan be larger than JPEG q90 here
80346 KB-37%Default web trialReview texture
70249 KB-55%Smaller web imagesCheck gradients
60201 KB-63%Upload limit trialCheck fine edges
50163 KB-70%Small targetArtifacts can show

Test methodology

ImgShrink generated four repeatable samples with sharp: a photo-style gradient, a UI screenshot, a transparent graphic and a flat color illustration.

Each output was encoded with the stated format and quality setting, then measured by byte size before being rounded for the table.

Test images and parameters

Photo sample: 1600x1067 pixels. Screenshot sample: 1365x768 pixels. Transparent sample: 512x512 pixels. Flat graphic sample: 1200x800 pixels.

WebP used quality 78 for the cross-format table, AVIF used quality 50, and JPEG baselines used quality 90 unless a quality row states otherwise.

What we learned

Quality 80 was 346 KB.

Quality 70 reduced the sample to 249 KB.

Quality 50 reached 163 KB and needs close review.

Limitations

These values are benchmark results for the sample set, not a promise for every uploaded file.

Real images vary by noise, detail, transparency, dimensions, browser encoder and the target platform's accepted formats.

Benchmark questions

Are these exact results for my image?

No. They are measured sample results that help choose a first setting to test.

Do these tests upload user images?

No. They use generated samples and browser-style encoding assumptions.