JPEG XL Is Back in Chrome: What You Need to Know (2026)
JPEG XL Browser Support Has Changed Everything in 2026
JPEG XL is officially back in Chrome. After Google controversially removed JPEG XL support from Chrome in October 2022, Chrome 145 shipped in February 2026 with a Rust-based JXL decoder built in. This reversal is one of the biggest image format developments in years, and it affects every web developer, photographer, and content creator working with images.
If you have been watching the JPEG XL story unfold, here is exactly what changed, how to start using JPEG XL today, and what you should do to prepare your workflow.
What Happened: Chrome 145 and the JPEG XL Comeback
Google originally added experimental JPEG XL support to Chrome in April 2021, then removed it entirely in December 2022 with Chrome 110. The stated reason was "insufficient ecosystem interest." Thousands of developers and photographers pushed back, but Google held firm for over three years.
Several factors forced the reversal in late 2025:
Chrome 145, released in February 2026, includes JPEG XL decoding behind a feature flag. This means the code is in the browser — you just need to turn it on.
Current JPEG XL Browser Support (March 2026)
Here is where every major browser stands right now:
|---------|---------------|------------|-------|
Effective global coverage: Approximately 20-25% of users can view JPEG XL natively (Safari). Once Chrome enables JXL by default (expected H2 2026), that figure will jump to approximately 85-90% overnight.
How to Enable JPEG XL in Chrome Today
If you want to start viewing and testing JPEG XL images in Chrome right now, here is how:
After relaunching, Chrome will decode and display .jxl images on any website that serves them. This is decoding only — Chrome will not yet encode images to JPEG XL, but it will render them correctly.
What This Means for Web Developers
You do not need to switch formats today
JPEG XL is not ready to be your primary web image format yet. With only Safari supporting it by default and Chrome requiring a flag, serving JPEG XL as your only format would leave 75-80% of visitors unable to see your images.
The recommended image format strategy for websites in March 2026 remains:
You can convert your images to AVIF right now using PhotoFormatLab's JPG to AVIF converter or PNG to AVIF converter — everything processes in your browser with no uploads.
You should start preparing for JPEG XL
Even though you should not serve JPEG XL exclusively today, you can prepare:
Generate JXL versions of key images. When Chrome enables JXL by default (likely H2 2026), you will want JXL files ready to serve. Start building your pipeline now.
Implement content negotiation. If you use a CDN like Cloudflare, Fastly, or AWS CloudFront, configure it to check the browser's Accept header and serve the best supported format:
Test your images in JXL format. Enable the Chrome flag and verify that your converted JXL images look correct. Pay attention to color accuracy, transparency handling, and any edge cases in your specific image content.
The lossless JPEG recompression opportunity
JPEG XL has a feature that no other format can match: lossless JPEG recompression. You can take any existing JPEG file and recompress it as JPEG XL, reducing its size by approximately 20% while producing output that decodes to the exact same pixels as the original. The process is fully reversible.
For sites with large JPEG libraries — media outlets, photography portfolios, e-commerce catalogs — this is an immediate win once browser support is widespread. You save 20% bandwidth with zero quality tradeoff.
What This Means for Photographers
Photographers have the most to gain from JPEG XL browser support expanding. Here is why:
If you are sharing photos online, you still need JPEG or WebP for compatibility today. Use PhotoFormatLab to convert your images between any format — all processing happens locally in your browser, so your original photos never leave your device.
JPEG XL vs AVIF: Quick Decision Guide
Since we already published a detailed JPEG XL vs AVIF comparison, here is the quick decision framework:
|----------|------------|-----|
For a deeper dive into how these formats compare on compression, quality, and features, read our complete JPEG XL vs AVIF breakdown.
Timeline: When Will JPEG XL Be Ready for Production?
Based on current signals from browser vendors and the development community:
Q1 2026 (now): Chrome 145 has JXL decoding behind a flag. Safari supports JXL by default. Firefox has JXL in Nightly builds.
H2 2026 (expected): Chrome enables JPEG XL decoding by default. Edge follows immediately (Chromium-based). This would bring global JXL support to approximately 85-90%.
2027: Firefox ships default JXL support. JPEG XL becomes practical for production web use without fallbacks for the vast majority of visitors.
Beyond 2027: JPEG XL becomes a viable primary format alongside AVIF, potentially replacing WebP as the "safe modern default" once legacy browser share drops further.
How to Convert Images for the JPEG XL Era
While waiting for full JPEG XL browser support, the smart move is to optimize your images in the best currently-supported formats. PhotoFormatLab processes all conversions directly in your browser — your files never leave your device.
Popular conversions for 2026:
The Bigger Picture: Why Image Formats Matter More Than Ever
The return of JPEG XL to Chrome reflects a broader trend: images continue to dominate web bandwidth. According to the HTTP Archive, images account for approximately 45% of the average web page's total weight. With Core Web Vitals directly affecting search rankings, choosing the right image format is not just a performance optimization — it is an SEO decision.
The format hierarchy for 2026 is clear:
For more on choosing the right format for your specific use case, see our complete image format comparison guide and best image format for websites in 2026.
Frequently Asked Questions
Q: Is JPEG XL supported in Chrome now?
Yes, Chrome 145 (released February 2026) includes JPEG XL decoding support, but it is behind a feature flag. You need to enable it manually at `chrome://flags` by searching for "JPEG XL" and setting it to "Enabled." Default enablement (no flag needed) is expected in the second half of 2026.
Q: Should I convert all my website images to JPEG XL?
Not yet. With only approximately 20-25% of browsers supporting JPEG XL by default (Safari), you would still need fallback formats for the majority of visitors. The best strategy for 2026 is to serve AVIF as your primary format with WebP and JPEG as fallbacks. Start generating JXL versions of your images so you are ready when Chrome enables default support.
Q: What is lossless JPEG recompression in JPEG XL?
JPEG XL can take any existing JPEG file and recompress it into a JPEG XL file that is approximately 20% smaller while being mathematically identical to the original when decoded. The process is fully reversible — you can reconstruct the exact original JPEG from the JXL file. No other image format offers this capability.
Q: How does JPEG XL compare to WebP?
JPEG XL offers significantly better compression than WebP (typically 30-50% smaller files at the same visual quality), plus features WebP lacks: progressive decoding, lossless JPEG recompression, 32-bit color depth, and support for extremely high resolutions. However, WebP has universal browser support while JPEG XL is still gaining adoption. For a full comparison of modern formats, see our WebP browser support guide.
Q: Will JPEG XL replace JPEG?
JPEG XL was explicitly designed as a successor to JPEG, and it is superior in every technical dimension: better compression, more features, and backward compatibility through lossless JPEG recompression. However, replacing a format with 30 years of universal support takes time. JPEG will remain necessary as a fallback for years to come, but JPEG XL is positioned to gradually take its place as browser support expands.
Q: Can I view JPEG XL images on my phone?
On iPhones and iPads running iOS 17 or later, Safari displays JPEG XL images natively. On Android, Chrome for Android will gain JPEG XL support on the same timeline as desktop Chrome (currently behind a flag, expected to enable by default in H2 2026). For sharing images with others, converting to JPG or PNG ensures universal compatibility across all devices.