Does Chrome support JPEG XL in 2025?

No. Chrome removed experimental JPEG XL support in 2022 and hasn't reactivated it. Safari and Edge (Windows 11) do support it natively since 2024-2025.

Is JPEG XL better than AVIF?

JPEG XL offers similar compression to AVIF with advantages in progressive encoding and JPEG legacy compatibility (lossless recompression). However, AVIF has better browser support today (Chrome, Firefox, Safari) and better integration in the web ecosystem.

Should I migrate to JPEG XL now?

Not for public web. Keep using AVIF/WebP with fallback to JPEG, given their complete support and positive impact on Core Web Vitals. JPEG XL is interesting for Apple/Windows environments where it opens natively, but it's still watchlist for web.

How do I implement fallbacks with the picture element?

Use with multiple ordered by preference: first AVIF, then WebP, and finally JPEG/PNG as fallback. Browsers automatically select the first compatible format.

JPEG XL in 2025: Safari and Windows Adopt It, Chrome Still Doesn't

What Changed in 2025: JPEG XL Timeline

JPEG XL (JXL) has experienced significant advances and setbacks in its adoption over recent years. Here's the current state in 2025:

Safari: Full Support Since 2024

Apple added native JPEG XL support in Safari 17 (macOS Sonoma and iOS 17) in September 2023, consolidating in 2024. This means all modern Apple devices can display JXL images without conversion or polyfills.

Windows 11/Photos: Native Compatibility

Microsoft integrated JPEG XL support in Windows 11 (22H2 and later) and the native Photos app. Users can open, view, and manage .jxl files directly from file explorer without additional software.

Chrome: No Default Support

Google removed experimental JPEG XL support in Chrome 110 (February 2023) citing "insufficient interest" and "unclear benefits over existing formats." As of 2025, Chrome still doesn't support JXL natively, representing over 65% of the global browser market.

Current support status:

✅ Safari (macOS, iOS): full support
✅ Edge (Windows 11): full support via system
❌ Chrome: no support (65%+ market share)
❌ Firefox: no default support
⚠️ Opera/Brave: depend on Chromium, no support

JXL vs AVIF/WebP Today: Technical Comparison

How does JPEG XL compare with modern formats that already have broad support?

Compression and Quality

JPEG XL: 10-40% smaller than JPEG at equivalent quality, with superior progressive encoding and JPEG legacy compatibility (lossless recompression)
AVIF: Similar or slightly better compression than JXL, especially in complex photographic images. Based on AV1, optimized for web
WebP: 25-35% smaller than JPEG, but inferior to AVIF and JXL in high-complexity images

Transparency and Alpha Channel

All three formats support full transparency with alpha channel. JPEG XL stands out for its efficiency in alpha channel compression, while AVIF offers better integration with current web tools.

Progressive Encoding

JPEG XL excels with advanced progressive encoding, allowing quality preview from the first bytes. AVIF supports progressive but with less flexibility. WebP lacks real progressive support.

Ecosystem and Tooling

AVIF/WebP clearly win:

Native support in Chrome, Firefox, Safari, Edge
CDN integration (Cloudflare, Cloudinary, Imgix)
Node.js processing (Sharp, Squoosh, ImageMagick)
Validated and optimized Core Web Vitals metrics

JPEG XL still limited:

Experimental tooling (libjxl, ImageMagick)
No CDN with automatic transformation
Absence in web analysis tools (PageSpeed Insights, Lighthouse)

When Does Migrating to JPEG XL Make Sense?

For Public Web: NOT YET

Since Chrome and Firefox don't support JXL, serving this format penalizes over 75% of users. Current recommendation is:

✅ Use AVIF as primary format (universal support in modern browsers)
✅ WebP as fallback for slightly older browsers
✅ JPEG/PNG as final fallback
✅ Implement lazy loading and responsive images with <picture>
📊 Measure Core Web Vitals impact (LCP, CLS, INP)

For Apple/Windows Environments: CONSIDER

If your audience is predominantly Safari/macOS or Windows 11 users (designers, photographers, specific corporate environments), JPEG XL can offer advantages:

Smaller size with superior quality
Compatibility with existing JPEG workflows
More efficient progressive preview

But still requires fallback for web.

Practical Workflow with OrquiTool: Ready for Today

While JPEG XL matures in the ecosystem, OrquiTool lets you optimize your images with formats that work right now:

Step 1: Convert to AVIF/WebP

Upload your JPG/PNG to OrquiTool Converter
Select 75-85% quality for optimal balance between size and visual quality
Download AVIF and WebP versions of your images

Step 2: Implement Feature Detection with <picture>

Use the <picture> element to serve the best format per browser:

<picture>
  <source srcset="image.avif" type="image/avif">
  <source srcset="image.webp" type="image/webp">
  <img src="image.jpg" alt="Description" 
       loading="lazy" 
       width="800" 
       height="600">
</picture>

Browsers automatically select the first format they support, guaranteeing full compatibility.

Step 3: When JXL Matures in Chrome, We'll Add Preset

OrquiTool will monitor JPEG XL evolution. When Chrome reactivates support and development tools (Lighthouse, Core Web Vitals) integrate JXL, we'll add:

Native JPG/PNG → JXL converter
Web-optimized quality presets
<picture> templates with JXL as first option

Until then, AVIF/WebP are the best choice for production web.

Checklist for Image Optimization Today

Immediate Action

✅ Convert your JPG/PNG to AVIF with 80-85% quality
✅ Also generate WebP version as fallback
✅ Implement <picture> with AVIF → WebP → JPG
✅ Add loading="lazy" on below-the-fold images
✅ Define width and height to avoid CLS
✅ Use responsive images with srcset for different sizes

Recommended Quality Presets

Hero photos: AVIF quality 85%, WebP 90%
Product images: AVIF quality 80%, WebP 85%
Thumbnails: AVIF quality 70%, WebP 75%
Icons/simple graphics: WebP 80% or SVG when possible

Copy-Paste <picture> Template

<!-- Responsive + multiple formats -->
<picture>
  <source 
    srcset="img-800.avif 800w, img-1200.avif 1200w, img-1600.avif 1600w" 
    type="image/avif" 
    sizes="(max-width: 768px) 100vw, 800px">
  <source 
    srcset="img-800.webp 800w, img-1200.webp 1200w, img-1600.webp 1600w" 
    type="image/webp" 
    sizes="(max-width: 768px) 100vw, 800px">
  <img 
    src="img-800.jpg" 
    alt="Accessible image description" 
    loading="lazy"
    decoding="async"
    width="800" 
    height="600">
</picture>

Free Mini-Audit: Test Your Images

Want to know how much weight you can save by converting to AVIF/WebP?

Upload 3 representative images from your site to OrquiTool
Convert to AVIF and WebP with 80% quality
Compare original vs. optimized weight
Multiply savings by total number of images on your site

A 40-60% weight savings in images directly improves your LCP (Largest Contentful Paint) and reduces load time.

Conclusion: JPEG XL on Watchlist, AVIF/WebP in Production

JPEG XL is a promising format with real technical advantages, but its fragmented adoption in 2025 makes it unsuitable for production web. Safari and Windows 11 support it, but Chrome (65%+ market) still doesn't activate it.

Recommendation for 2025:

🚀 Use AVIF as primary format with WebP/JPEG fallback
📊 Measure Core Web Vitals impact with Google PageSpeed Insights
🔍 Keep JPEG XL on watchlist for 2026+ when Chrome reconsiders
⚙️ Use OrquiTool for local conversion without uploading your files

Next Steps

Optimize your images right now with OrquiTool: local processing, no file uploads, 100% free.

Convert Images Free →

JPEG XL in 2025: Safari and Windows Adopt It, Chrome Still Doesn't — What to Do Today (with OrquiTool)