WebP vs AVIF vs JPEG XL: Which Format Wins in 2026?

By the ImageSEO Team. Updated July 2026. ~12 min read.

The image format wars in 2026 come down to three contenders: WebP, AVIF, and JPEG XL. Each is meaningfully better than the JPEG and PNG most sites still ship. The right choice for your WordPress site comes down to three things — browser support, file size, and the tooling you already run. This guide gives you the practical answer, the real numbers behind it, and the exact WordPress setup to serve the best format to every visitor automatically.

Format is not just a performance detail, either. Image weight is one of the biggest levers on Largest Contentful Paint, and Core Web Vitals feed both Google rankings and the retrieval pipelines behind AI search. Choosing the right format is image SEO work, not just engineering housekeeping.

The 30-second verdict

• Use WebP by default. 98%+ browser support, ~30% smaller than JPEG, native WordPress support since 5.8. It is the safe baseline for every site.
• Add AVIF if your CDN or plugin supports it. ~50% smaller than JPEG and smaller than WebP, with ~93% browser support in 2026. Serve it with WebP as a fallback.
• Skip JPEG XL for now. Google dropped Chrome support in 2022. Even in 2026 it lives only in Safari and a few niche browsers — not viable for the open web yet.

The rest of this article explains why, with the browser data, compression benchmarks, and the WordPress configuration that puts it into practice.

Why image format matters for SEO

Before comparing formats, it helps to be clear about why the choice matters beyond raw page weight:

• Largest Contentful Paint (LCP). On most pages the LCP element is an image. A hero photo that is 50% lighter loads measurably faster, and LCP is a ranking-relevant Core Web Vital.
• Crawl and retrieval budget. Lighter pages are crawled more efficiently, and the retrieval bots behind AI search abandon slow pages. A fast image is a readable image — see how ChatGPT, Claude, and Perplexity read your images.
• Bandwidth and mobile experience. Smaller files mean lower bounce on mobile connections, which feeds engagement signals.

In other words, format is a genuine SEO input. It will not rank a page on its own, but it removes friction that holds good pages back. For the broader picture, our complete image SEO guide sets format in context with the higher-leverage signals.

The three contenders at a glance

The headline: WebP wins on compatibility, AVIF wins on compression, and JPEG XL — despite being technically excellent — loses on the one thing that matters most for the open web, browser support.

WebP — the safe default

Released by Google in 2010, WebP is supported by Chrome, Firefox, Edge, Safari, and Opera. WordPress has shipped native WebP upload and serving since 5.8, and the entire plugin and CDN ecosystem converts to it automatically. Compression is available in both lossy and lossless modes, and typical files run 25–35% smaller than an equivalent-quality JPEG.

• Pros: near-universal browser support, native WordPress handling, solid compression, the most mature tooling of the three.
• Cons: AVIF compresses better when you can use it; no HDR support.
• Tooling: ShortPixel, Imagify, Smush, and most CDNs convert JPEG/PNG to WebP with no manual work.

If you do nothing else after reading this article, move your site to WebP. It is the lowest-risk, highest-coverage upgrade available, and it works for essentially every visitor.

AVIF — the quality leader

Released in 2019 by the Alliance for Open Media, AVIF is the compression champion. Files are typically 20–30% smaller than WebP and 45–55% smaller than JPEG at comparable quality, and it holds up especially well at low bitrates where other formats turn blocky. Chrome, Firefox, Edge, Safari (since 16.0), and Opera all support it in 2026; a few environments such as older Samsung Internet builds still lag.

• Pros: best-in-class compression, excellent quality at low bitrates, HDR and wide-gamut support.
• Cons: slower, more CPU-intensive encoding on upload; a minority of CDNs still lag on generation.
• Tooling: Bunny.net, Cloudflare Polish, and Kinsta CDN convert to AVIF on the fly; some plugins offer it as an add-on.

The catch is the ~93% support figure. You should not serve AVIF alone — you serve it with a WebP or JPEG fallback so the ~7% of browsers that can’t read it still get an image. The next section shows how that fallback works.

JPEG XL — the one that almost won

Developed by the JPEG committee as a true successor to the original JPEG, JPEG XL is arguably the best format on paper: excellent compression, backward compatibility with existing JPEGs, progressive decoding, and HDR. It had a genuine shot at becoming the standard — until Google removed Chrome support in 2022, citing insufficient ecosystem interest. Firefox and Safari kept or added it, but with Chrome holding the majority of the market, JPEG XL is effectively sidelined for the open web.

Verdict: don’t deploy it on a public WordPress site in 2026. Keep an eye on it — if Google reverses course, the calculus changes quickly — but today it can’t serve the majority of your visitors.

Browser support in 2026

This table is the whole argument in miniature. WebP is green across the board. AVIF is green almost everywhere. JPEG XL is red in the browser that matters most. Format decisions follow market reality, not technical merit alone.

File size and quality: real numbers

Compression percentages are easier to grasp as concrete file sizes. For a typical 1600px-wide hero photograph at visually equivalent quality, you can expect roughly:

Exact numbers vary with image content — photographs with smooth gradients compress differently from screenshots with hard edges — but the ordering is stable. AVIF is consistently the lightest, WebP is a comfortable middle, and both crush legacy JPEG. The practical takeaway: moving from JPEG to WebP alone can cut your image payload by a third, and adding AVIF on top can roughly halve it.

Lossy vs lossless: picking the right mode

All three formats support both lossy and lossless compression, and choosing the wrong mode wastes most of the savings. The rule of thumb maps to image content rather than format:

• Photographs and complex imagery — use lossy. The eye can’t see the discarded detail, and the file-size savings are dramatic (this is where AVIF’s lead is largest).
• Logos, icons, screenshots, and flat graphics — use lossless, or lossy at a very high quality setting. Hard edges and text reveal compression artifacts quickly, and these files are small to begin with.
• Images with transparency — both WebP and AVIF support an alpha channel, so you no longer need to fall back to heavy PNGs for transparent graphics. This is one of the biggest wins over the legacy stack covered in our WebP vs PNG comparison.

Most plugins and CDNs pick a sensible default automatically, but if you tune quality settings manually, set them per content type rather than site-wide.

How to serve the right format automatically

You do not pick one format and convert your whole library to it. You serve the best format each browser can read, and let the browser choose. There are two ways to do that.

1. The <picture> element

The HTML <picture> element lets the browser fall through a list of sources and load the first format it supports:

<picture>
  <source srcset="hero.avif" type="image/avif">
  <source srcset="hero.webp" type="image/webp">
  <img src="hero.jpg" alt="red leather tote bag, autumn 2026 collection">
</picture>

A Chrome user gets AVIF, an older browser falls back to WebP, and anything ancient still gets the JPEG. Note the alt attribute lives on the <img> — format optimization never replaces a good description.

2. Content negotiation at the CDN

Most modern CDNs do the same thing server-side: they read the browser’s Accept header and return AVIF, WebP, or JPEG from a single URL. This keeps your markup simple and is usually the easier path on WordPress, because the plugin or CDN handles generation and delivery for you.

The 2026 WordPress setup

The pragmatic, low-risk configuration for a WordPress site this year:

1. Upload as JPEG/PNG as usual. You don’t need to change your editorial workflow.
2. Convert to WebP automatically with an optimization plugin or your CDN. This alone covers ~98% of visitors with a lighter file.
3. Add AVIF as the preferred format if your CDN or plugin supports it, with WebP as the fallback via <picture> or content negotiation.
4. Serve over HTTP/2 or HTTP/3 so multiple images download in parallel.
5. Keep filenames semantic and alt text descriptive — the part that actually earns rankings. ImageSEO handles this layer.

That stack gives every visitor the lightest image their browser can read, with zero manual conversion and a clean fallback chain.

The encoding-cost trade-off

AVIF’s compression isn’t free: it is significantly slower and more CPU-intensive to encode than WebP. On a busy site that generates derivatives on the fly, that cost is real, and it’s the main reason some teams stay on WebP despite AVIF’s smaller files.

There are three ways to manage it. First, offload encoding to a CDN (Bunny, Cloudflare, Kinsta) so it never touches your origin server’s CPU. Second, generate derivatives asynchronously — convert on upload or in a background queue rather than on the first request, so visitors never wait on encoding. Third, on constrained or shared hosting, simply stick with WebP: the ~30% saving over JPEG with none of the encoding overhead is still an excellent outcome. The worst choice is synchronous AVIF generation on a weak origin, which can make pages slower than the heavier format would have.

Which format should you use?

Common mistakes

• Serving AVIF with no fallback — the ~7% of browsers that can’t read it get a broken image. Always pair it with WebP/JPEG.
• Converting to a next-gen format but keeping huge dimensions — a 4000px AVIF is still oversized. Resize to the displayed size first.
• Stripping alt text during a bulk re-encode — some tools drop metadata. Re-encoding the format must never wipe the description.
• Chasing JPEG XL because it benchmarks well, ignoring that Chrome can’t display it.
• Treating format as the whole job — it’s one of five image SEO levers, and not the biggest.

Format is only half the story

The fastest, best-compressed image in the world ranks for nothing if it has no description. File format sits in the middle of the image SEO priority stack, not the top:

1. Alt text — the biggest SEO lever, and what AI engines quote
2. Semantic filename — a signal read before the page loads
3. File format and compression (WebP or AVIF — this article)
4. Lazy loading and LCP prioritization
5. Image sitemap and structured data

Get items 1 and 2 right with ImageSEO, which writes natural-language alt text and renames files semantically across your whole library. Get 3–5 right with your optimization plugin and CDN. If you’re still on legacy formats, our WebP vs PNG comparison covers the first upgrade most sites should make, and image for SEO ties the whole workflow together.

Frequently asked questions

Is AVIF always better than WebP?

On compression, yes — AVIF files are typically 20–30% smaller at the same quality. The trade-offs are slightly lower browser support (~93% vs ~98%) and heavier encoding. For most sites the answer is to serve AVIF with a WebP fallback so you get the best of both.

Does WordPress support AVIF natively?

Yes, WordPress added native AVIF support in 6.5, provided your server’s image library (Imagick or GD) supports it. In practice most sites still rely on a plugin or CDN to generate and serve AVIF reliably across hosts.

Will switching to WebP or AVIF hurt my image SEO?

No — as long as you keep the same semantic filenames and alt text, and your image sitemap reflects the served URLs. Google indexes WebP and AVIF normally. The faster load can only help. Just don’t let a bulk re-encode strip your metadata.

Should I keep JPEG fallbacks at all?

A JPEG (or WebP) fallback is cheap insurance for the small share of browsers and bots that don’t read AVIF. The <picture> element makes the fallback automatic, so there’s no reason to drop it.

Does image format affect Core Web Vitals?

Directly. A lighter hero image improves Largest Contentful Paint, one of the three Core Web Vitals Google uses. Moving from JPEG to AVIF on an LCP image is one of the simplest CWV wins available.

What about animated images — is AVIF better than GIF?

Hugely. Both WebP and AVIF support animation at a fraction of GIF’s file size. If you still ship animated GIFs, converting them to animated WebP or AVIF is one of the largest single payload reductions you can make.

Will JPEG XL ever come back?

Possibly. It remains technically strong and has support in Safari and Firefox. But until Chrome re-adds it, it can’t serve the majority of the web, so it stays off the recommendation list for production sites in 2026.

Do I need to re-upload my whole media library to switch formats?

No. The standard approach keeps your original JPEG/PNG uploads untouched and generates WebP or AVIF derivatives from them — via a plugin or CDN — leaving your media library and URLs intact. You can convert your back catalogue in a background bulk run without re-uploading anything.

Which format is best for an online store with thousands of product images?

AVIF with a WebP fallback, served through a CDN. At store scale the per-image savings compound into a meaningfully faster catalogue and lower bandwidth bills, and the CDN absorbs the heavier encoding cost. Pair it with descriptive, price-bearing alt text so those product images are also citable in Google Images and AI search.

Conclusion

For 2026 the answer is settled in practice, even if the theory is messier. WebP is the safe default every site should adopt. AVIF is the upgrade for performance-focused sites that can serve it with a fallback. JPEG XL is on the bench until Chrome changes its mind. Serve the best format each browser can read, keep your fallback chain intact, and resize before you convert.

Then remember that format is the middle of the stack, not the top. The images that win in search are fast and described — semantic filenames and natural-language alt text are what actually earn the rankings. ImageSEO handles that layer automatically across your whole WordPress library, so your perfectly compressed images also have something worth indexing.