What changed
Google shipped JPEG XL decoding enabled by default in Chrome 155, whose stable rollout began October 6, 2026. The browser uses jxl-rs, a memory-safe Rust decoder, replacing the old experimental C++ implementation removed years earlier. JPEG XL offers lossless JPEG transcoding, HDR, progressive rendering and animation. Safari has supported still JPEG XL images since Safari 17, while Mozilla plans to enable JPEG XL by default in Firefox 158, scheduled for October 13. This is a real browser implementation milestone, not a declaration that all visitors already run a compatible version.
Why it matters
For image-heavy sites and media pipelines, JPEG XL can now be evaluated for high-fidelity photography, lossless archives and progressive loading without Chrome-specific flags. Chrome's reach changes the practical deployment equation, and Mozilla's forthcoming default support should broaden it further. Yet web developers must still negotiate different browser versions, Safari's partial feature support, other Chromium browsers, and image/CDN tooling; AVIF or WebP plus JPEG fallback remains sensible while adoption grows.
Chrome stable ships a new memory-safe decoder
Chrome 155 decodes image/jxl by default using jxl-rs written in Rust. The Chrome team says the implementation was fuzzed and reviewed with no memory-safety bugs found in its testing history; that is a vendor claim, not a guarantee against all bugs.
The cross-browser milestone is staggered
Safari 17+ supports JPEG XL still images but not animation or progressive rendering. Firefox 158 is scheduled for October 13 with default support, but it is not yet a completed stable release as of October 8. Edge and other Chromium derivatives have their own release schedules.
Choose JPEG XL for the workload, not just the headline
Google recommends comparing JPEG XL with AVIF on representative assets. JPEG XL is particularly attractive for high-fidelity or lossless photographic images and fine-grained progressive rendering; AVIF can remain more efficient at ordinary web-quality settings.
Production delivery still needs format negotiation
Use picture/source or a CDN image-negotiation path with existing AVIF/WebP/JPEG alternatives. Installed Chrome versions lag the new stable release, and downstream CMS, image transforms and marketplaces may not yet accept or generate .jxl.