# Chrome 155 enables JPEG XL by default, moving the format toward mainstream web delivery Chrome's October 6 stable release ships JPEG XL decoding without a flag using the memory-safe Rust jxl-rs decoder. Safari already supports still images, and Firefox targets default support in version 158 on October 13. JPEG XL is leaving the experimental-browser niche. Chrome 155 now decodes it by default, but Edge, older installed browsers and Safari's partial feature set still require fallbacks. - Status: Active - Published: 2026-10-08T17:55:13+13:00 - Updated: 2026-10-08T17:55:13+13:00 - Categories: Web Development, Browsers & Web Standards - Tags: Chrome, Firefox, image formats, JPEG XL, web performance - Canonical HTML: https://beyondthe.news/dossiers/chrome-155-jpeg-xl-default-firefox-158-browser-support ## 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. ## Key details - Chrome 155 began stable rollout October 6, 2026 with JPEG XL decoding enabled by default. - Chrome uses the jxl-rs memory-safe Rust decoder. - JPEG XL supports HDR, progressive decoding, animation and lossless JPEG transcoding, subject to each browser's implementation. - Safari 17+ supports still JPEG XL images but lacks animation and progressive rendering. - Firefox 158 is scheduled for October 13, 2026; its stable rollout was still pending on October 8. - Edge and other Chromium derivatives are not assumed to have shipped equivalent support. - Google recommends testing AVIF and JPEG XL against representative images rather than replacing all formats blindly. ## Builder takeaways - Test JPEG XL against AVIF for high-fidelity photos, archives and progressive delivery rather than assuming one format always wins. - Serve fallbacks through picture or content negotiation until actual client support is sufficiently high. - Check CDN transformation, CMS upload, cache and MIME-type support before enabling JXL site-wide. - Treat Firefox 158 as scheduled until the stable release actually ships, and verify Edge independently. ## What to watch - Firefox 158 stable release and feature caveats on October 13. - Edge and Android/WebView rollout details and installed-browser adoption. - CMS/CDN encoder support, image processing pipelines and practical Core Web Vitals measurements. ## Uncertainties - Chrome 155 stable rollout does not mean every installed Chrome has updated. - Firefox 158 support is planned, not yet stable as of this dossier date. - Comparative compression and performance depend heavily on image content, encoder settings and network conditions. ## Sources - [Shipping JPEG XL in Chrome](https://developer.chrome.com/blog/jpeg-xl-in-chrome) — Chrome for Developers · primary · 2026-10-06T00:00:00+13:00. Official announcement for Chrome 155 JPEG XL and jxl-rs design. - [Chrome 155 Release Notes](https://chromestatus.com/release-notes/155) — Chrome Platform Status · primary documentation · 2026-10-06T00:00:00+13:00. Chrome 155 release status and decoding feature. - [Intent to Ship: JPEG XL](https://hacks.mozilla.org/2026/08/intent-to-ship-jpeg-xl/) — Mozilla Hacks · primary · 2026-08-24T00:00:00+12:00. Mozilla implementation rationale and progressive-rendering context. - [Firefox 158 release notes for developers](https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/158) — MDN · primary documentation · 2026-10-04T00:00:00+13:00. Scheduled Firefox 158 release timing; do not describe as already stable. - [JPEG XL in Chrome: What Changes Now Chrome 155 Ships It](https://mochify.app/guides/jpeg-xl-chrome-support) — Mochify · independent technical analysis · 2026-10-07T00:00:00+13:00. Independent deployment caveats and browser support limitations.