The Future of Image Formats: WebP, AVIF, JPEG XL and Beyond (2026)
JPEG has been the world's dominant image format since 1992. Thirty-four years later, it is facing the most serious challenge to its dominance in its history — not from a single competitor, but from three: WebP, AVIF, and JPEG XL. Each takes a fundamentally different approach to replacing JPEG's aging compression algorithm. Each has different strengths, limitations, and browser support stories.
The question is not whether JPEG will be replaced — it will be, gradually, over the next decade. The question is which format replaces it, on what timeline, and what you should actually be using today. This guide answers all three questions with concrete data.
A Brief History of Image Format Evolution
The Four Contenders: A Deep Dive
WebP — The Current Web Standard
WebP is the clear winner of the current generation — not because it is the technically best format, but because it achieved the critical mass of browser support needed to become the default. All major browsers have supported it since 2020. Google, YouTube, Facebook, Netflix, Shopify, Amazon, and hundreds of thousands of websites now serve WebP as their primary image format.
WebP uses predictive coding derived from Google's VP8 video codec. Instead of JPEG's 8×8 DCT blocks (which produce the characteristic blocky artefacts at low quality), WebP predicts each block from its neighbours and only stores the error — a more efficient approach for most photographic content. The result is files that are typically 25–35% smaller than JPEG at equivalent visual quality.
WebP's four modes (lossy, lossless, alpha, animated) make it a genuine single-format replacement for JPEG, PNG, and GIF in web contexts. Its primary weaknesses are in print (no CMYK) and email (no Outlook support). For everything web-related, it is the right choice today.
AVIF — The High-Efficiency Challenger
AVIF (AV1 Image File Format) is derived from the AV1 video codec — a next-generation video compression standard developed by the Alliance for Open Media (a coalition including Google, Apple, Microsoft, Amazon, Netflix, and others). By 2026, AVIF has achieved solid browser support and is growing rapidly:
- Chrome 85+ (August 2020): Full AVIF support including animation and alpha
- Firefox 93+ (October 2021): Full support
- Safari 16+ (September 2022): Full support
- Edge 121+ (January 2024): Full support
AVIF's compression advantage over WebP is significant. At equivalent visual quality, AVIF files are typically 40–50% smaller than JPEG and 20–30% smaller than WebP. For high-traffic websites serving millions of images, this difference translates to meaningful bandwidth savings and faster load times.
AVIF also supports features JPEG cannot: HDR (high dynamic range), wide colour gamuts (P3, Rec. 2020), and 12-bit colour depth. These matter for photography on HDR displays and for content that needs to look correct on wide-gamut screens — which now includes most flagship smartphones and an increasing share of laptop displays.
The trade-off: AVIF encoding is significantly slower than both JPEG and WebP. This matters for server-side on-the-fly conversion. Pre-encoding (processing images ahead of time rather than on request) sidesteps this limitation for most deployment scenarios.
JPEG XL — The Format That Should Have Won
JPEG XL (JXL) is, by most technical measures, the best image format ever designed. It was created by a joint effort of Cloudinary, Google, and the JPEG Committee (the same body that designed the original JPEG). Its technical advantages are substantial:
- Better compression than AVIF at equivalent quality, especially for photographic content
- Lossless JPEG re-encoding — you can convert an existing JPEG to JPEG XL and back to the exact original bytes, with no quality loss. No other lossy format can do this.
- Progressive decoding — a JPEG XL image can be decoded progressively at any level of detail from a single stream, unlike AVIF's tile-based approach
- 12-bit colour, HDR, wide gamut — all the modern features
- Extremely fast decoding — JPEG XL decodes faster than AVIF and comparable to WebP
- Responsive images — JPEG XL can store multiple representations of an image (full resolution, thumbnail, low-res preview) in a single file
Despite all these advantages, JPEG XL faces a critical adoption problem: Google removed experimental JPEG XL support from Chromium in January 2023, citing "insufficient ecosystem interest." Since Chrome controls ~65% of global browser market share (and all Chromium-based browsers including Edge, Opera, and Brave), this decision effectively blocked JPEG XL from mainstream web deployment.
As of 2026, JPEG XL has full support in Safari 17+ and Firefox 113+ — but not in Chrome. This means roughly 60% of web users can view JPEG XL natively, but the 40% on Chrome cannot. Until Chrome ships JPEG XL, web developers cannot serve it without a JPEG fallback that negates much of the benefit.
The irony is significant: Google funded much of JPEG XL's development, then blocked it from their browser — possibly because JPEG XL would compete with AVIF (which is based on Google's AV1 codec, in which Google has a substantial investment).
HEIC / HEIF — Apple's Ecosystem Format
HEIC (High Efficiency Image Container) using HEIF (High Efficiency Image Format) has been Apple's default iPhone camera format since iOS 11 in 2017. Based on the HEVC (H.265) video codec, it achieves similar compression to AVIF — around 40–50% smaller than JPEG at equivalent quality.
HEIC will not become a web standard. Its adoption as a web format is blocked by MPEG-LA patent licensing — implementing HEIC support requires paying royalties, which no browser vendor outside Apple's own ecosystem is willing to do. Chrome and Firefox have no native HEIC support and are unlikely to add it.
HEIC is relevant primarily as an output format from Apple devices. If you photograph with an iPhone and need images for the web, convert from HEIC to JPG or WebP. Our HEIC to JPG converter handles this directly in your browser.
Compression Comparison: The Numbers
| Format | File size vs JPEG (same visual quality) | Browser support (2026) | Transparency | Animation | HDR / 12-bit |
|---|---|---|---|---|---|
| JPEG | Baseline | 100% | No | No | No |
| PNG | 2–3× larger | 100% | Yes | Limited (APNG) | No |
| WebP | 25–35% smaller | 97%+ | Yes | Yes | No |
| AVIF | 40–50% smaller | ~90% | Yes | Yes | Yes |
| JPEG XL | 45–55% smaller | ~60% (no Chrome) | Yes | Yes | Yes |
| HEIC | 40–50% smaller | <30% (no Chrome/Firefox) | Yes | Yes (HEIF sequences) | Yes |
What Should You Actually Use Today?
The practical answer in 2026 depends on your deployment scenario:
For Websites and Web Apps
The optimal delivery stack is now AVIF → WebP → JPEG, served using the HTML <picture> element:
<picture>
<source type="image/avif" srcset="photo.avif">
<source type="image/webp" srcset="photo.webp">
<img src="photo.jpg" alt="Description" width="800" height="600" loading="lazy">
</picture>Browsers pick the first source type they support. AVIF-capable browsers (Chrome, Firefox, Safari 16+) get the smallest files. WebP-capable browsers (all modern browsers) get the second-best option. Everything else gets JPEG. This approach adds no risk and improves performance for the majority of users.
For Images You Serve Today Without a CMS
If you are manually optimising images without a build pipeline or CDN:
- Convert to WebP using our JPG to WebP converter — it runs entirely in your browser, no upload needed
- Serve with a
<picture>element including a JPEG fallback - This alone will typically reduce your image payload by 25–35%
For Large-Scale Platforms with Image Pipelines
Encode AVIF for all images as part of your CI/CD pipeline using Sharp (Node.js) or libavif (C). Serve AVIF to supported browsers, WebP as fallback. The encoding time cost is paid once at deployment, not per request.
For Email
Use JPEG only. Outlook does not support WebP, AVIF, or JPEG XL. PNG works but is larger than necessary. JPEG at Q85+ is the universal safe choice for email in 2026.
For Photography and Archival
Shoot in RAW or JPEG at maximum quality. Archive in JPEG (Q95+) or TIFF. Convert to WebP or AVIF only for web delivery, keeping the original intact. Never discard your masters in favour of a format with uncertain longevity.
Convert Your Images to WebP — Free, Right Now
No upload, no registration. Our JPG to WebP converter runs entirely in your browser and processes files instantly with no size limit.
Predictions: What Will the Web Use in 2030?
Based on current adoption curves and industry dynamics, here is a reasonable projection:
WebP: Still Dominant
WebP will remain the default web image format for most content through 2030. It has the critical mass of tooling, CDN support, and developer familiarity to sustain its lead even as AVIF grows.
AVIF: Major Growth
AVIF will grow significantly, particularly for high-quality photography sites and e-commerce. CDN automatic conversion will drive adoption without requiring manual developer action.
JPEG XL: Uncertain
JPEG XL's future depends entirely on whether Chrome ships it. If Google reverses its decision — perhaps pressured by Apple and Mozilla shipping it — JPEG XL could become the next major format. Without Chrome, it cannot.
JPEG: Gradual Decline
JPEG will not disappear — it will remain the format for email, cameras, and compatibility-critical scenarios. But its share of web image delivery will continue falling as WebP and AVIF tooling becomes more automatic.
HEIC: Apple-Only Niche
HEIC will remain the default output of Apple cameras. It will not achieve web browser support outside Apple's ecosystem due to patent costs. Conversion tools will remain necessary.
AI-Assisted Compression
Neural image compression (models like ELIC, VCT, and others) is advancing rapidly. By 2030, AI-based compression may offer 2× better efficiency than any current format at equivalent quality — but infrastructure adoption will lag the technology significantly.
The Bottom Line for 2026
The image format landscape is mid-transition. JPEG is losing ground on the web but will remain important for email, cameras, and legacy compatibility for years. WebP has won the current round and is the sensible default for web delivery today. AVIF offers better compression where supported and is worth including in a multi-format delivery stack. JPEG XL is technically excellent but practically unusable for web at scale until Chrome ships support.
The most future-proof approach: store originals as JPEG or PNG, deliver WebP for web, and adopt AVIF as your second-choice source in a <picture> element. If JPEG XL gains Chrome support in the next few years, adding it as a first-choice source takes one line of HTML.
The conversion step from JPEG to WebP is the single highest-ROI optimisation most websites can make today. It requires no design changes, no code changes beyond a <picture> element, and delivers immediate improvements to page speed and Core Web Vitals.