AVIF now outperforms WebP on compression by a meaningful margin — typically 30–50% smaller file sizes at comparable visual quality, with an 850KB JPEG hero image commonly compressing down to around 195KB as AVIF. Browser support has also caught up: AVIF now reaches roughly 93% of global browser traffic, spanning Chrome, Firefox, Safari, and Edge. For most WordPress sites in 2026, the real question isn’t AVIF or WebP — it’s how to serve both correctly.
The Compression Numbers
| Format | Typical size vs. JPEG | Global browser support |
|---|---|---|
| JPEG (baseline) | — | 100% |
| WebP | ~25-35% smaller | ~97%+ |
| AVIF | 30-50% smaller than WebP (not just JPEG) | ~93%+ |
The One Real Trade-off: Encoding Speed
AVIF’s main cost isn’t file size or quality — it’s encoding time. Converting a high-resolution image to AVIF can take several seconds, compared to milliseconds for WebP. In practice this doesn’t slow down your visitors at all, since modern optimization plugins encode images in the background (often at upload time or via a queue), not on-demand when a page loads. The trade-off only matters if you’re running your own conversion pipeline without background processing.
The 2026 Best Practice: Serve Both
The current consensus isn’t “pick AVIF or WebP” — it’s serve AVIF as the primary format with WebP as the fallback, using the <picture> element or your optimization plugin’s automatic format negotiation. That gets the ~93% of browsers that support AVIF the smallest possible file, while everyone else still gets a modern, well-compressed WebP image instead of falling all the way back to JPEG.
How to Actually Implement It
- Confirm your WordPress version. WordPress 6.5 and later supports native AVIF uploads, so implementation is largely a matter of configuration rather than custom code.
- Use an optimization plugin that generates both formats automatically and serves the best one per-browser via content negotiation, rather than picking one format for the whole site.
- Re-run existing media library images through conversion — new uploads getting AVIF/WebP doesn’t help images already on the site unless you bulk-convert the existing library too.
- Spot-check visual quality on a few hero/product images after conversion — AVIF’s aggressive compression is usually invisible, but it’s worth a manual check on your most important images.
This pairs directly with the loading-side Core Web Vitals work we’ve covered before — see WordPress Image Optimization Guide for 2026 Sites for the broader picture, and fetchpriority: The One-Line Fix That Cuts LCP for the hero-image-specific fix. Want your site’s image pipeline reviewed? Get in touch.
Frequently Asked Questions
Should I drop WebP entirely and only use AVIF?
Not yet — AVIF support, while strong, still trails WebP’s roughly 97%+ coverage. Serving AVIF with a WebP fallback covers effectively all modern browsers without leaving anyone on a worse format than necessary.
Will converting my media library slow down my server?
Background/queued conversion (which most modern optimization plugins use) spreads the encoding load over time rather than doing it all at once, so the impact on a live server is minimal if configured correctly.
Does WordPress need a plugin for AVIF, or is it built in?
WordPress 6.5+ supports uploading AVIF files natively, but automatic conversion of existing JPEG/PNG images into AVIF (and serving the right format per browser) still typically requires an image optimization plugin.
Featured image: original illustration.