Here is the headline: for web photos, WebP usually beats JPEG — often by 25–35% at the same quality, and it also supports transparency and a lossless mode. For years, browsers have all supported it. So why does JPEG still exist?

Because "usually" is not "always," and a few image types refuse to cooperate. The right answer comes from a small decision tree, not a rule.

The decision tree

Image typePickWhy
Web photo (quality ≤ 90)WebPSmaller at equal quality, supported everywhere modern
Transparent logo / graphicWebP (or SVG)WebP lossless keeps crisp edges and transparency
Downstream tool needs JPEGJPEGSome editors, print and EXIF pipelines still expect it
Screenshot with clean textPNG (or WebP)Sharp edges; JPEG adds fringing around text

When WebP quietly loses

Flat graphics and screenshots already compress well in PNG. Converting them to WebP often saves little or nothing, and can add encoder cost. Meanwhile, JPEG has a specific niche: very high compressibility with a slightly grainy look that some photos tolerate well. If your audience also runs print or legacy pipelines, keeping JPEG avoids surprises.

How to actually decide

Stop guessing. The compressor re-encodes your image as both JPEG and WebP and shows the exact resulting size. There is no format battle worth having purely in theory — run the number, compare visually, keep the smaller that still looks identical. That measurement also feeds the wider website optimization checklist.