JPG vs WebP: which format should you use?

JPG has been the dominant photograph format for three decades. WebP is Google's modern replacement with meaningful advantages: better compression, alpha channel support, and animation. Almost every modern browser supports WebP now, but JPG remains the safe choice when you can't control the destination environment.

Head-to-head comparison

Aspect	JPG	WebP
Compression	Lossy	Lossy or lossless
Typical file size	Baseline	25-35% smaller at same quality
Transparency (alpha)	No	Yes
Colour handling	24-bit YCbCr	24-bit with better chroma
Browser support	Universal since ~1995	~97% of modern browsers
Design tool support	Universal	Growing — Figma yes, older tools no
Encoding CPU cost	Very cheap	2-3× more expensive
Best for	Photograph delivery anywhere	Modern web photograph delivery

When to use each

Use JPG when

You need something that opens on every device without question
The image will pass through email, WhatsApp, or systems that re-encode
You're preparing for print or a colour-managed workflow
CPU cost of conversion matters (batch of thousands)

Use WebP when

The image is for a modern website you control
Page-weight and Core Web Vitals matter
You want transparency in a photograph-quality output
You want a single format that can replace both JPG and PNG for delivery

The verdict

For a website you control, WebP is the modern default — smaller files, better quality, transparency support. For anything that leaves your control (email attachments, third-party uploads, print prep), JPG remains the safe bet. Most sites end up serving WebP with a JPG fallback via the HTML picture element.

Frequently asked questions

Is WebP really 25-35% smaller than JPG?

Yes, at the same visual quality. Google's own benchmarks (2020) show 26% smaller than PNG for lossless and 25-34% smaller than JPG for lossy. In practice, savings depend on image content — photographs with lots of detail see closer to 25%, while images with flat regions can see 40%+ savings because WebP's prediction filters exploit spatial redundancy JPG can't.

Does WebP work in every browser?

As of 2026, WebP has ~97% global browser support — every major browser since Chrome 32 (2014), Firefox 65 (2019), Edge 18, and Safari 14 (2020). Only very old Safari (macOS Mojave and earlier), IE, and some enterprise browsers reject it. For most sites, use WebP as the primary format with a JPG fallback via the picture element.

Will converting JPG to WebP improve quality?

No. Any quality already lost to JPG compression stays lost. The WebP file will be smaller than the original JPG at the same visual quality, but you can't recover thrown-away pixel data. Convert from the highest-quality source you have — RAW or original PNG is best.

Can I use WebP for print?

Technically yes, but no reason to. Print workflows overwhelmingly expect TIFF (lossless) or high-quality JPG. Most professional print RIPs and prepress tools don't support WebP natively. Stick with JPG or TIFF for anything going to a printer.

Does WebP support transparency like PNG?

Yes. WebP supports full 8-bit alpha channel transparency, both in lossy and lossless modes. A transparent WebP is typically 25% smaller than the equivalent PNG. This is one of the biggest wins over JPG — you get photograph-quality compression AND transparency in the same file.

Why do some CMS platforms still reject WebP uploads?

Older WordPress installs (before 5.8), some Shopify apps, and legacy enterprise CMSes still validate uploads against a JPG/PNG allowlist. If your CMS rejects WebP, either update to a modern version or upload as JPG and convert to WebP at delivery time via a CDN like Cloudflare Polish or Cloudinary.

What's the difference between lossy and lossless WebP?

Lossy WebP uses VP8-based prediction and quantization, similar to JPG but more sophisticated — files are 25-35% smaller than JPG at the same quality. Lossless WebP is a completely different algorithm based on entropy coding — files are 26% smaller than PNG on average. Use lossy for photographs, lossless for graphics with sharp edges.