WebP vs JPG: Which Should You Actually Use?
Where WebP genuinely wins, where JPG is still the right answer, and why "supported everywhere" matters more than file size.
WebP is technically the better format. That does not automatically make it the right choice — it depends entirely on where the image is going.
The short version
- Serving images on a website → WebP, with a JPEG fallback if you care about very old browsers.
- Anything you send to another person → JPG.
- Anything you upload to a form you do not control → JPG.
- Images with transparency → PNG or WebP, never JPG.
- Photographs you will edit again → keep the original; export JPG or WebP at the end.
Where WebP wins
File size. At the same visual quality, WebP files are typically 25–35% smaller than JPEG. Across a site with a lot of images, that is real bandwidth and a real improvement in load time.
Transparency. WebP supports an alpha channel, so a single format covers both photographic and graphic content. JPEG cannot do this at all.
Lossless mode. WebP can compress losslessly, which makes it a reasonable PNG replacement for some graphics — smaller than PNG, no quality loss.
Where JPG still wins
Universal acceptance. This is the whole argument. A JPG opens in every editor, uploads to every form, prints from every service, and displays on every device made in the last thirty years. WebP does not.
Predictable tooling. Camera workflows, professional print pipelines, and archival systems are built around JPEG. Fighting that costs more time than the bytes are worth.
Editing headroom. JPEG's behaviour under repeated editing is well understood, and every tool handles it identically.
The size claim, in context
"25–35% smaller" is true and worth having, but it is not the whole picture:
- The saving applies at equal visual quality. If you compare a q90 WebP against a q90 JPEG using an encoder that interprets quality differently, the comparison is meaningless.
- On flat-colour graphics, WebP's advantage grows — this is where JPEG's block structure wastes the most bits.
- On already-compressed images, converting between formats cannot recover anything. Re-encoding always costs a little.
A practical workflow
Keep one high-quality master of anything you care about — the original export, or a lossless copy. From that master, produce whatever the destination needs:
- Web for a site you control → WebP
- Email, forms, messaging, print → JPG around q85–90
- Transparency → PNG or WebP
Do not treat either format as the master. Both are delivery formats.