ZizzleUp Editorial Team • April 13, 2026
The JPEG XL image format is officially back — and this time, it arrived inside the world’s most popular browser. After controversially dropping support in 2022, Google restored JPEG XL to Chromium in January 2026 and shipped it to the stable Chrome 145 release in February. For web developers, photographers, and site owners, this is one of the most significant image format developments in years. Understanding what JPEG XL offers — and how to prepare for its wider rollout — can give your website a meaningful head start in speed, visual quality, and SEO performance.
What Is the JPEG XL Image Format?
The JPEG XL image format — commonly shortened to JXL — is a next-generation raster image codec designed as a universal replacement for JPEG, PNG, WebP, GIF, and even AVIF. Developed under the Joint Photographic Experts Group, it was standardized as ISO 18181 and engineered to excel in every dimension that earlier formats compromise on: compression efficiency, visual quality, decoding speed, and feature breadth.
Technically, JPEG XL is impressive across the board. It compresses images 50–60% smaller than traditional JPEG at equivalent visual quality. Furthermore, it encodes 10–15% more efficiently than AVIF at practical speeds. Additionally, JPEG XL is the only modern web format to support true progressive decoding, which means images appear quickly at low resolution and sharpen as more data arrives — a huge benefit for slow connections.
Beyond compression, JPEG XL supports wide color gamut (Display P3), HDR (High Dynamic Range) with PQ and HLG transfer functions, 32-bit color depth, alpha transparency, and animation — all in a single format. Crucially, it can also losslessly transcode existing JPEG files with zero quality loss and approximately 20% smaller file sizes, making migration from legacy libraries uniquely painless.
Why the JPEG XL Image Format Left Chrome — and Why It’s Back
To understand why this comeback matters, it helps to know the history. Google introduced experimental JPEG XL support in Chrome in April 2021. Then, in October 2022, Chrome’s team removed it — citing limited ecosystem adoption and a preference for AVIF. The decision triggered immediate backlash from developers, publishers, and the JPEG XL community.
Three years later, however, pressure from the broader ecosystem reversed that decision. Safari shipped JPEG XL support in version 17. Firefox updated its position and began integrating a Rust-based decoder. The PDF Association designated JPEG XL as its preferred format for HDR content in PDF specifications — a move that directly impacted Chrome’s own built-in PDF viewer. Developer surveys identified JPEG XL as a top pain point in Interop 2026, the cross-browser interoperability initiative.
Consequently, Google’s Chrome architecture team welcomed a new implementation using the Rust-based jxl-rs decoder in November 2025. By January 2026, the code was merged into Chromium. Chrome 145, released in February 2026, shipped JPEG XL decoding to the stable channel — gated behind the #enable-jxl-image-format flag in chrome://flags. This marks the first native JPEG XL support in Chrome since version 110 in late 2022.
JPEG XL vs WebP vs AVIF: How the JPEG XL Image Format Compares
The JPEG XL image format outperforms both WebP and AVIF in several key areas, though each format has its own strengths. Here is how they compare across the dimensions that matter most:
| Feature | JPEG XL | AVIF | WebP |
|---|---|---|---|
| Compression vs JPEG | 50–60% smaller | ~50% smaller | 25–35% smaller |
| Progressive decoding | ✅ Yes | ❌ No | ❌ No |
| Lossless JPEG transcoding | ✅ Yes (unique) | ❌ No | ❌ No |
| HDR & Wide Color Gamut | ✅ Full | ✅ Full | ❌ 8-bit sRGB only |
| Animation support | ✅ Yes | ⚠️ Limited | ✅ Yes |
| Encoding speed | Fast (2.5× faster than AVIF) | Slow | Fast |
| Global browser support (2026) | ~12% (growing) | ~93% | ~97% |
The most striking JPEG XL advantage is its lossless JPEG transcoding capability. No other modern format can re-compress an existing JPEG library without any quality loss — and do so while achieving a 20–30% file size reduction. For sites with large image archives, therefore, migration to JPEG XL provides instant savings without touching a single source file.
How the JPEG XL Image Format Improves SEO and Core Web Vitals
Smaller image files directly improve Google’s Core Web Vitals — particularly Largest Contentful Paint (LCP), the metric that measures how quickly the main visible content loads. According to early testing, websites using the JPEG XL image format can achieve page load times up to 30% faster than those relying on traditional JPEG, with comparable or better visual quality.
Real-world benchmark data from Cloudinary’s analysis of 40,000+ images found that JPEG XL at effort level 6 produced files 20% smaller than AVIF — while encoding 2.5 times faster. Similarly, a DebugBear benchmark of a 990 KB photograph showed JPEG XL delivering the file at just 472 KB — a 52% saving over the original, compared to 700 KB for WebP and 507 KB for AVIF.
Faster LCP scores reduce bounce rates, improve session duration, and send stronger user experience signals to Google. Since Google’s March 2026 Core Update completed just days ago on April 8, site owners are actively looking for performance improvements to recover or protect rankings. Adopting a more efficient image format is one of the highest-leverage optimizations available without changing a site’s content strategy.
JPEG XL Browser Support in 2026: What You Need to Know
Browser support for the JPEG XL image format is growing steadily but is not yet universal. As of April 2026, here is where each major browser stands:
- Chrome / Chromium: Available since Chrome 145 (February 2026) behind the
#enable-jxl-image-formatflag. Default-on status is pending completion of long-term maintenance commitments. - Safari: Native support since Safari 17 (2023). Safari users, therefore, already receive JPEG XL images seamlessly.
- Firefox: Support introduced in Nightly builds; actively integrating the same Rust-based
jxl-rsdecoder. General availability expected later in 2026. - Edge: Follows Chromium, so Chrome 145’s implementation applies. Currently requires the same experimental flag.
Combined browser support currently sits at approximately 12% globally — primarily from Safari users. However, the trajectory is clear: Chrome’s flag-gated support will become default-on once Google completes final validation, and Firefox is actively building the same decoder. Interop 2026 has included JPEG XL as an investigation area with participation from Apple, Google, Microsoft, and Mozilla — a strong signal of coordinated adoption ahead.
In the meantime, the recommended deployment strategy is to serve JPEG XL to supporting browsers while providing WebP or JPEG fallbacks for others, using the HTML <picture> element with type="image/jxl" source hints.
How to Convert Your Images to the JPEG XL Image Format Today
The good news is that converting images to the JPEG XL image format is easier than ever. Several tools already support JXL encoding and can be used to start building a future-ready image pipeline:
- Squoosh — Google’s browser-based image conversion tool supports JPEG XL encoding with adjustable quality settings. No installation required.
- ImageMagick — The command-line workhorse supports JXL encoding as of recent versions, making it suitable for batch processing scripts.
- Cloudinary — The CDN platform already supports automatic JPEG XL delivery to supported browsers, making server-level adoption straightforward.
- libvips / sharp — Node.js image processing libraries with JXL support are available for developers building custom pipelines.
- ACDSee Photo Studio Ultimate 2026 — Desktop photo software now includes native JPEG XL export.
For a quick, no-setup conversion of individual images — whether you’re testing JPEG XL output or need to convert photos to WebP or PNG while JXL browser support matures — ZizzleUp’s free online image converter lets you convert JPG, PNG, WebP, and more directly in your browser. No account needed, and your files never leave your device.
When encoding JPEG XL, effort level 6 strikes the best balance between file size and encoding speed for most web use cases. Higher effort levels (up to 9) produce slightly smaller files but take significantly longer to encode, making them better suited for pre-generated assets rather than on-the-fly delivery.
Conclusion
The return of the JPEG XL image format to Chrome marks a turning point for web image standards. After three years of controversy, JPEG XL has re-entered the browser ecosystem with stronger credentials: a memory-safe Rust decoder, cross-browser momentum from Safari and Firefox, PDF industry backing, and developer demand that Google could no longer ignore.
For website owners and developers, the opportunity is real and growing. JPEG XL delivers better compression than any competing format, uniquely supports lossless JPEG transcoding, and enables true progressive loading. As browser support expands through 2026, sites that adopt a JPEG XL delivery strategy — with appropriate fallbacks — will gain measurable advantages in page speed, Core Web Vitals scores, and user experience.
Start experimenting now. Convert key images to JPEG XL, measure the file size savings, and implement the <picture> element with progressive fallbacks. The format’s era of browser exile is over — and the web is better for it.
Sources
- 🔗 Google Chrome 145 Released With JPEG-XL Image Support — Phoronix (Feb 10, 2026)
- 🔗 Chrome 145 Update Introduces JPEG-XL — Analytics Insight (Feb 11, 2026)
- 🔗 JPEG XL and Core Web Vitals: What You Need to Know — CoreWebVitals.io (Mar 3, 2026)
- 🔗 Google Quietly Brings JPEG XL Back to Chrome — TechRadar (Jan 19, 2026)
- 🔗 JPEG XL (JXL) Is Coming Back to Chrome — Coywolf (Jan 19, 2026)
- 🔗 Chrome to Support Much Smaller, Faster Images as JPEG XL Makes a Comeback — Neowin (Jan 13, 2026)
- 🔗 JPEG XL — Wikipedia (updated 2026)