• Sources: primary, discussion
  • Summary: Chrome is shipping JPEG XL decoding support for .jxl images and animations starting with Chrome 155, announced on 2026-10-06, and this is decoding only rather than encoding. The Chrome team states JPEG XL offers 30 to 50 percent better compression than JPEG plus lossless compression, built-in HDR and lossless JPEG transcoding, and recommends trying both AVIF and JPEG XL rather than replacing one with the other, with JPEG XL most useful for high-fidelity or lossless photographic images and for fine-grained progressive decoding. Chrome integrated jxl-rs, a pure Rust implementation, rather than the C++ reference libjxl, on the reasoning that image decoders process untrusted binary input inside the renderer process and have historically produced out-of-bounds reads, heap overflows and use-after-free bugs.
  • Why it matters: Reaching competitive speed safely required stabilizing the Rust target_feature_11 feature so SIMD could be used without unsafe code, then building a jxl_simd abstraction layer modeled on the C++ Highway library that confines unsafe operations to a small reviewed set, and the team states fuzzing and AI code review found no memory safety bugs across the implementation's history.
  • Follow-up: This archive already carries Mozilla shipping JPEG XL in Firefox 157 behind a Rust decoder it required before shipping, so watch whether a third engine commits and whether the Interop 2026 JPEG XL Investigation produces cross-browser test coverage.