Chrome Has Added JPEG XL Decoding Support

The browser now supports the high-efficiency image format to enable 30-50% better compression than legacy JPEG.

Updated on Oct. 7, 2026 in Computers

Isometric editorial illustration of stacked geometric prisms representing structured data, symbolizing modern image compression technology.
Chrome version 155 now includes native decoding support for the JPEG XL image format, enabling developers to achieve significantly higher compression efficiency through modern, Rust-based architectural improvements. AI Illustration. Upload story photo >

Live Poll

Do you prefer web browsers to prioritize new image formats to improve browsing speeds?

Chrome version 155 has introduced native decoding support for the JPEG XL image format. The implementation, designed for high-fidelity and lossless compression, follows the Chrome team's participation in the Interop 2026 investigation.

Why it matters

By integrating JPEG XL, Chrome addresses web developer demand for more efficient media storage and transmission. The move marks a shift toward modern formats that offer significant performance gains over aging standards.

The new JPEG XL decoder delivers a 30-50% improvement in compression efficiency compared to the standard JPEG format. This implementation was rewritten in the Rust programming language to mitigate memory safety vulnerabilities.

The players

Chrome

A widely used web browser developed by Google that renders web content and manages multimedia parsing through a complex internal engine.

Interop 2026

A collaborative industry effort aimed at improving cross-browser compatibility and standardizing new web technologies.

The details

To ensure performance, the decoder employs a SIMD (Single Instruction, Multiple Data) abstraction layer—a method that allows processors to perform the same operation on multiple data points simultaneously for faster computation. Developers utilized Rust to replace traditional C++ implementations, effectively eliminating common memory-safety risks. The final code was verified through extensive fuzzing—a technique involving the injection of random data to find crashes—and AI-assisted review processes.

Timeline

  1. 2026: JPEG XL was evaluated as a proposal in the Interop Process.

  2. Chrome 155: Decoding support officially became available.

The Tech Race

This integration follows the findings of the Interop 2026 JPEG XL investigation, which evaluated the format against modern standards. It marks a push to move the web ecosystem beyond legacy JPEG toward architectures optimized for high-fidelity assets.

Users will begin to benefit from the format as websites adopt JPEG XL for high-fidelity assets, potentially resulting in faster load times and lower data usage. Web developers can now leverage these compression efficiencies in their own projects to reduce bandwidth requirements.

The takeaway

The transition to JPEG XL reflects a broader trend of prioritizing memory-safe code and efficient compression in browser engines. Watch for upcoming web performance benchmarks to see how this implementation scales across varied hardware configurations.

Further reading

For more on evolving browser capabilities, browse the Computers section.

Live Poll

Do you prefer web browsers to prioritize new image formats to improve browsing speeds?