Designers argue about WebP vs JPEG the way mechanics argue about engine oil — loudly, and usually without numbers. Here are the numbers.
WebP vs JPEG: the spec table
| Format | Compression | Transparency | Animation | Support (2026) |
|---|---|---|---|---|
| WebP | Lossy and lossless | Yes | Yes | over 96% of browsers in use in 2026 (caniuse) |
| JPEG | Lossy | No | No | every browser and device made in the last 25 years |
Two rows, but they hide the biggest practical gap: file size on real images, covered next.
The kilobyte question
For WebP, the working reality: 25-34% smaller than an equivalent JPEG, per Google's published study. For JPEG: a 12-megapixel photo lands around 3-4 MB at quality 85.
Content decides everything. Flat-color graphics, screenshots and photographs sit on completely different compression curves, so the same pair of formats can swap winners between two images.
For pure web delivery, measure both against WebP before deciding: at over 96% of browsers in use in 2026 (caniuse), it often makes this whole debate academic.
Whichever way the kilobytes fall, remember they compound: a saving of 200 KB per image across a forty-image page is eight megabytes a visitor never downloads.
What each format can carry
WebP is lossy and lossless, strongest at modern websites, web optimization, progressive web apps; its known costs are not supported in older browsers, limited editing software support.
JPEG is lossy, aimed at photographs, social media, web images; the trade-off there: lossy compression, no transparency, quality degrades on re-saving.
Notice the two cost lists barely overlap: that is why this pairing survives — each format covers the other's blind spot.
Which one should you use?
Choose WebP when your job looks like modern websites, web optimization, progressive web apps and the priority is 25-35% smaller than JPEG, supports transparency and animation.
Choose JPEG when you are in photographs, social media, web images territory and need small file size, universal support, great for photos.
Switching sides costs nothing: the JPEG converter and the WebP converter each take seconds, so test both on a real file from your project.
Troubleshooting the usual suspects
Colors shifted. Usually a color-profile story: the source carried a wide-gamut profile and the viewer assumes sRGB. Convert from an sRGB master when the destination is the web, and the shift disappears.
The file will not open. Nine times out of ten the viewer is the limitation, not the file. Try a second viewer before blaming the conversion, or convert to JPEG — if that copy opens, the original was fine all along.
Transparent areas turned white. The target format has no alpha channel; flattening is the documented behaviour, not a bug. Re-convert to PNG or WebP if transparency must survive.
The file got bigger. Some content genuinely compresses worse in the new format — flat graphics in photo-oriented codecs, photos in graphics-oriented ones. The size readout before download is the early warning.
What this means for page speed
Images are usually the heaviest asset class on a page, so format choice flows straight into Largest Contentful Paint — the Core Web Vitals metric Google weighs for ranking. Lighter images, earlier paint, better scores: the chain is that direct.
The compounding is what surprises people: 200 KB saved per image across a forty-image page is eight megabytes a visitor never downloads.
Measure before and after with PageSpeed Insights — the image-weight line item makes the improvement concrete instead of theoretical.
Transparency, animation and the small print
Transparency: WebP carries an alpha channel; JPEG does not. If your work involves logos over photos or UI elements, this single row outweighs every compression argument.
Animation: WebP can animate; JPEG is strictly still.
Both formats are exactly as old as their trade-offs suggest: WebP from 2010, JPEG from 1992.
How the compression actually works
Dual-mode formats carry both toolboxes: a lossy mode for photographs and a lossless one for graphics. That flexibility is exactly why the modern web formats displaced single-mode ancestors.
Lossy compression throws away detail the eye is bad at noticing — fine texture, subtle color steps — and keeps what perception cares about. That is how a photo drops 80% of its weight while looking identical at arm's length; it is also why each re-save discards a little more.
Every recommendation here is downstream of those mechanics — formats do not have personalities, only algorithms.
Two formats, two eras
WebP comes from 2010, built by Google; JPEG from 1992, by the Joint Photographic Experts Group. Every difference in the table above traces back to what problems were worth solving in those two moments.
The general law of image formats: the older one opens in more places, the newer one wastes fewer bytes. WebP and JPEG follow it exactly.
Living with each format
WebP is handled by the full toolchain — Photoshop, GIMP, and everything between: support in 2026 means over 96% of browsers in use in 2026 (caniuse).
For JPEG, the picture is every browser and device made in the last 25 years. Where support diverges, the older format usually wins on reach and the newer one on efficiency — the classic trade.
Converting between WebP and JPEG
Moving a file either way is the easy part: the JPEG converter and the WebP converter both take drag-and-drop batches and return a ZIP. Dimensions never change; only the encoding does.
Convert once from the best source you have — chaining a file through three formats is how visible artifacts are born.
Four real scenarios
The photographer delivering a wedding gallery cares about quality first and upload time second — the format whose profile reads "25-35% smaller than JPEG, supports transparency and animation" or "small file size, universal support, great for photos" closer to that wins the job.
The web developer chasing Core Web Vitals weighs file size above everything: between 25-34% smaller than an equivalent JPEG, per Google's published study and a 12-megapixel photo lands around 3-4 MB at quality 85, the smaller real-world output gets shipped.
The office user attaching a file for an unknown recipient optimizes for one thing — that it opens. Whichever of the two enjoys broader support is the safe envelope.
The print shop reverses every web instinct: resolution and lossless data outrank file size completely, because a 60 MB master is cheaper than a reprint.
Frequently Asked Questions
Can I convert between WebP and JPEG without quality loss?
Lossless-to-lossless conversions are perfect copies. The moment a lossy format is involved, some data is discarded — normally invisible at default settings, but keep your originals as the master copies.
Which is better for a website in 2026?
Browser support is the deciding spec: WebP — over 96% of browsers in use in 2026 (caniuse); JPEG — every browser and device made in the last 25 years. For pure web delivery, also weigh WebP and AVIF, which usually undercut both on size.
Does transparency survive in both?
WebP: supports transparency. JPEG: no alpha channel. Converting from a format with alpha into one without will flatten transparent areas, usually onto white.
Do WebP and JPEG support animation?
WebP: yes. JPEG: no — stills only. For short animated clips on the web, animated WebP has largely replaced the older approaches on size alone.
Does it matter which one my camera or phone produces?
Devices choose for storage efficiency, not for your workflow. Whatever comes out of the device is just the starting point — keep it as the original and convert copies to fit each destination.
Can I batch convert a mixed folder of WebP and JPEG?
Yes — converters key on each file's actual type, not the folder. Drop the mixed set, pick one target format, and the output comes back uniform in a single ZIP.
Written by Giovanni Picaro, a web developer who has been building image tools and optimizing sites since 2019. Sources: MDN image format reference and Google web.dev. Last reviewed: 2026.