JPG vs WEBP: is it worth converting your images?
WebP often produces smaller files than JPG at comparable visual quality, though actual savings depend on your photo and settings. Here is where that saving is real, where it isn't, and what you give up.
By Ranjith R, Creator & Developer of TryImagerPublished Last updated: 7 min read
WEBP is a modern image format that does two things JPG cannot: it compresses more efficiently at the same perceived quality, and it supports transparency. Browser support stopped being a real concern years ago — every current version of Chrome, Firefox, Safari and Edge decodes it. The open question is no longer 'can people see it' but 'is the saving worth the conversion step'.
How much do you actually save?
On unedited photographs with smooth gradients and soft detail — skies, skin, bokeh backgrounds — WebP's block prediction usually produces a noticeably smaller file than JPG at matched visual quality. For example, on a 1600 × 1200 hero photograph (7.68 MB of raw RGBA canvas pixels), WebP's predictive macroblock coding models smooth sky transitions across larger blocks than JPG's fixed 8×8 grid. Actual savings vary by image content and quality setting, and are smallest on images that are already heavily compressed: converting a 60 KB JPG that has visible artefacts mostly re-encodes the artefacts, and you may even end up with a larger file.
The PNG case is the strongest one
For transparent cut-outs, shadows and overlays, WebP can keep an alpha channel while compressing colour data lossily. That offers a useful alternative to lossless PNG for web delivery, but the saving depends on image content and quality. Compare the measured export and inspect edge detail before replacing your working original.
What you give up
- Desktop software: some older editors, print workflows and enterprise tools still don't accept WEBP. Keep a JPG master if a file is going to a client or a printer.
- Platform uploads: most social and marketplace uploaders accept WEBP now, but a few still reject it. Convert back to JPG if an upload fails.
- Metadata: conversion drops most EXIF data. If camera settings or copyright fields matter to you, preserve the original.
- Editing chain: WEBP is lossy like JPG, so the same generation-loss rule applies — convert once, at the end.
Choosing a quality setting
| Quality | Use it for | What you'll see |
|---|---|---|
| 90–95 | Hero images, portfolios, product detail | Visually indistinguishable from the source |
| 75–85 | Most web images, blog photos, thumbnails at scale | No visible loss at normal viewing size |
| 55–70 | Background imagery, long feeds, email | Slight softening in fine texture |
| Below 50 | Rarely worth it | Blockiness and colour smearing in flat areas |
Quality numbers are not comparable across formats. WEBP at 80 is not the same amount of data as JPG at 80 — it usually looks better and weighs less. Judge by the output, not by the number.
A workflow that holds up
- Keep the original file untouched somewhere. Every conversion below starts from it, not from a previous export.
- Resize to the largest size the image will ever be displayed at. This dominates everything else.
- Export WEBP at quality 80 for the web, and a JPG at quality 85 as the compatibility fallback if you need one.
- Spot-check the result full-screen, not in a thumbnail — artefacts hide at small sizes.
Why WebP handles smooth gradients better than JPEG
Standard JPEG processes every 8 × 8 pixel block independently during discrete cosine transform (DCT) quantization, which is why pushing a JPEG down to a strict byte budget creates visible stair-step seams across clear blue skies or studio backdrops. WebP uses intra-frame block prediction derived from VP8 video keyframes: before encoding a block, the encoder inspects adjacent top and left pixels to predict the gradient direction and only encodes the residual difference. In a browser test on a 1600 × 1066 studio portrait (286 KB source JPEG), exporting to WebP at quality 80 produced a 164 KB file while keeping background transitions smooth; re-encoding a heavily compressed 58 KB thumbnail JPEG to WebP at quality 85 grew to 64 KB because block boundaries in the source acted as artificial detail. Always compare the before-and-after byte readout on your actual file.
Technical Diagram · JPEG Independent 8×8 DCT Blocks vs WebP Predictive Macroblocks
If you serve images on your own website and still want a fallback for legacy systems, the standard HTML `<picture>` element lets you ship both formats cleanly without JavaScript detection: place a `<source srcset="hero.webp" type="image/webp">` tag above your standard `<img src="hero.jpg">` element so modern browsers download the smaller WebP asset while older viewers fall back to the JPEG automatically.
Tools for this
- JPG to WEBPUse it to see the actual saving on your own image, in bytes.
- WEBP to JPGUse it when an app or client refuses to open a WEBP file.
- PNG to WEBPUse it the biggest win of all — transparency at a fraction of the size.
- Image CompressorUse it to dial in quality or a target KB ceiling on JPG and WEBP files.