AVIF achieves universal browser support as Edge and Safari close gaps
This article examines the current state of consumer image formats in 2026, noting that AVIF has achieved universal browser support alongside WebP and JPEG. It provides a technical trade-off analysis for streaming engineers, highlighting AVIF's superior compression efficiency for photos versus the faster encoding speeds and broader legacy compatibility of WebP and JPEG.
Key Takeaways
- AVIF achieved baseline universal support following Edge's inclusion in early 2024 and Safari's 2023 updates.
- Photographic content in AVIF typically results in file sizes 20% to 50% smaller than comparable WebP versions.
- WebP remains the pragmatic default for UI graphics and screenshots, where its mature lossless mode often outperforms AVIF.
- AVIF encoding is 5 to 10 times slower than WebP, creating potential latency bottlenecks for on-the-fly image services.
- JPEG retains a strategic role for legacy compatibility, progressive rendering, and universal support in email clients and office suites.
Why It Matters
Universal support shifts AVIF from a niche experimental format to a viable primary delivery standard for streaming and web architectures. For high-traffic platforms, transitioning to AVIF provides an immediate 20% reduction in image-related egress costs and improves Core Web Vitals on bandwidth-constrained mobile devices. However, the high computational cost of AVIF encoding demands a shift in infrastructure strategy: developers must prioritize asynchronous build-time conversion or aggressive edge caching to mitigate real-time processing latency. Watch for the emergence of JPEG XL, which has recently reappeared in Chromium 145 and promises to challenge AVIF’s compression dominance by late 2026.
Additional Context
The path to universal AVIF support was marked by significant browser engine divergence. While Google integrated AVIF into Chrome 85 in 2020, Microsoft Edge only finalized support in Version 121 in January 2024. Per Can I Use and recent site reporting from July 2026, global browser support for AVIF now stands between 93% and 95%. This puts it nearly on par with WebP, which achieved similar coverage after Safari adopted the format in 2020. Despite this web parity, AVIF continues to struggle with OS-level integration; for instance, macOS Finder Quick Look still requires third-party plugins to preview AVIF files natively as of mid-2026, per PicShift updates. The competitive landscape is further complicated by the resurrection of JPEG XL. After being removed from Chrome in 2023, Google reintroduced a Rust-based JPEG XL decoder in Chrome 145 in February 2026. Per ReezoAI and CoreWebVitals.io, JPEG XL is expected to be enabled by default in late 2026, offering features AVIF lacks, such as byte-for-byte reversible lossless transcoding of existing JPEG archives. This capability could reduce storage and CDN costs by 20% without the quality risk associated with re-encoding to AVIF. Major cloud providers have standardized their responses to these shifting formats by integrating automated transformation at the edge. Per FinancialContent reports from May 2026, platforms like Cloudflare, Akamai, and Amazon CloudFront now offer server-side format negotiation. These services detect browser headers and automatically serve AVIF to compatible clients while falling back to WebP for older versions, effectively abstracting the complexity of format management away from the origin server. For engineering teams, the decision has shifted from a browser compatibility assessment to a compute-versus-bandwidth cost-benefit analysis.
Read full article at daily.dev
Get this in your inbox → Subscribe
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source