JPEG XL Is Back in Chrome: Your 2026 Image Guide
JPEG XL Is Back in Chrome — Here's What It Means for Your Images
In February 2026, Google did something nobody expected: it brought JPEG XL back to Chrome. After controversially removing the format in 2022, Chrome 145 shipped with a Rust-based JXL decoder, reversing one of the most debated decisions in web image history. If you work with images — whether you're a photographer, designer, developer, or just someone who converts iPhone photos — this matters.
But here's the thing: JPEG XL isn't enabled by default yet. It's behind a flag. Firefox is still working on its implementation. And meanwhile, AVIF and WebP already work everywhere. So what should you actually do with your images in 2026? This guide breaks down exactly what JPEG XL is, how it stacks up against the formats you're already using, and how to convert between all of them right now — free and private, directly in your browser.
What Is JPEG XL and Why Does It Matter?
JPEG XL (file extension .jxl) is a next-generation image format developed by the Joint Photographic Experts Group — the same organization behind the original JPEG that's been powering the web since 1992. It was standardized in 2022 as ISO/IEC 18181, combining research from Google's PIK format and Cloudinary's FUIF format into a single, royalty-free standard.
What makes JPEG XL genuinely different from just "another image format" comes down to three capabilities no other format offers simultaneously:
The format delivers files that are 35-55% smaller than traditional JPEG at equivalent visual quality, and roughly 20% smaller than AVIF at high quality settings. For photographers and designers working with large image libraries, those savings add up fast.
Why Did Chrome Remove — Then Restore — JPEG XL?
The backstory matters because it explains where we are today. In 2022, Google's Chrome team removed experimental JPEG XL support, citing low ecosystem adoption and the success of WebP and AVIF. The developer community pushed back hard — the Chromium bug tracker for JXL restoration became one of the most-starred issues in the project's history.
What changed? In November 2025, Google's Chromium team formally reversed its "obsolete" declaration and accepted a Rust-based decoder (jxl-rs) contribution. By February 2026, Chrome 145 shipped with JPEG XL decoding support, gated behind the chrome://flags/#enable-jxl-image-format flag.
Google has set clear conditions for enabling JPEG XL by default: a commitment to long-term maintenance and meeting standard Chrome launch criteria. The realistic timeline for default-on support is the second half of 2026. Meanwhile, Safari has supported JPEG XL since version 17, and Firefox has a Rust-based decoder in Nightly builds targeting Firefox 149, though several blockers remain before stable release.
JPEG XL vs AVIF vs WebP: The 2026 Comparison
You've probably seen comparison articles before, but most miss the nuance. Each format wins in different scenarios. Here's where things actually stand in April 2026, with real data:
| Feature | JPEG XL | AVIF | WebP |
|---|---|---|---|
| Compression vs JPEG | 35-55% smaller | 40-50% smaller | 25-34% smaller |
| Browser support (2026) | ~18% (Safari + Chrome flag) | ~93-95% | 97%+ |
| Lossless compression | Yes (best in class) | Yes | Yes |
| Progressive decoding | Yes | No | No |
| Lossless JPEG recompression | Yes (20% savings) | No | No |
| HDR support | Yes | Yes | No |
| Animation | Yes | Yes | Yes |
| Encoding speed | Very fast (~100x AVIF) | Very slow | Fast |
| Max image dimensions | 1+ billion pixels per side | 8193 x 4097 (base) | 16383 x 16383 |
| Color depth | Up to 32-bit float | Up to 12-bit | 8-bit |
The takeaway isn't that one format "wins." It's that they serve different use cases. JPEG XL has the best compression at high quality and the unique ability to recompress existing JPEGs losslessly. AVIF dominates at low-to-medium bitrates and has the broadest modern browser support. WebP is the safe universal fallback that works everywhere.
Who Should Care About JPEG XL Right Now?
Not everyone needs to act on JPEG XL today. Here's a practical breakdown:
Act now if you're a photographer or designer with large JPEG archives. JPEG XL's lossless recompression can shrink your existing photo library by 20% with zero quality loss — and you can convert back to the original JPEG at any time. This is a storage savings play that requires no compromises.
Start testing if you're a web developer. Enable the Chrome flag, experiment with serving JXL images using the
Wait and watch if you're a casual user. For everyday image sharing and conversion, AVIF and WebP handle everything you need today with universal browser support. When JPEG XL goes default-on in Chrome and lands in Firefox stable, the switch will be seamless.
How to Convert Your Images Today
With PhotoFormatLab's HEIC to JPG converter, you can convert iPhone photos in seconds. Our JPG to WebP converter cuts file sizes by 25-34%. The JPG to AVIF converter delivers files up to 50% smaller. Every conversion happens entirely in your browser. Your files never leave your device. Check out our guide on the best CloudConvert alternative or our breakdown of WebP vs JPEG. For Apple devices, the HEIC to WebP converter is useful. Read our deep dive on understanding HEIC.
The Format Roadmap
Use WebP and AVIF today. Prepare for JPEG XL.
Frequently Asked Questions
Is JPEG XL supported in all browsers in 2026?
Not yet. Safari supports JXL natively, Chrome 145 has it behind a flag. Default-on expected H2 2026. ~18% global support.
Should I switch from WebP or AVIF to JPEG XL right now?
Not for web delivery. JXL is excellent for local storage and archiving with 20% lossless savings.
How do I open a .jxl file?
macOS Preview/Safari support JXL. Windows has a Microsoft Store plugin. Chrome needs the flag enabled.
What is JPEG XL lossless recompression?
Convert JPEG to JXL for ~20% smaller files with zero quality loss. Original JPEG is perfectly recoverable.
Which image format should I use for my website in 2026?
Serve AVIF first, WebP fallback, JPEG final fallback. Add JXL when Chrome enables it by default.