Google Chrome 155 Embraces the Future with JPEG XL Support
A New Era of Image Compression
The official Google Developer Blog recently published an exciting announcement on October 6. The article revealed that the upcoming Google Chrome 155 browser will officially introduce decoding support for the JPEG XL image format. The developers describe JPEG XL as a next-generation image format. It aims specifically to satisfy the demanding needs of modern web developers and professional photographers alike. For more technical insights, you can read about JPEG XL in Chrome directly on the developer blog.
Compared to traditional JPEG files, this new format delivers an impressive 30 to 50 percent improvement in compression ratios. Furthermore, it proudly boasts support for pristine lossless compression, native HDR capabilities, and seamless, lossless JPEG transcoding. The Google development team strongly encourages users to experiment with both AVIF and JPEG XL formats simultaneously.
They note that AVIF shines in scenarios requiring extreme bandwidth sensitivity and crucial loading speeds. Its rich feature set and widespread browser compatibility make it perfect for websites hosting massive image libraries. Conversely, JPEG XL proves uniquely suited for high-fidelity or strictly lossless compression tasks. It excels particularly with photographic imagery or when a project requires fine-grained progressive decoding.
Demonstrating Progressive Decoding
The Google team also shared a compelling video demonstrating the progressive decoding power of JPEG XL. In their specific example, the complete image file measured 146.7 KB. Astonishingly, users could clearly identify the main subject of the image after downloading only a few kilobytes of data.
Prioritizing Uncompromised Security
Regarding security, Google emphasized a critical reality of modern web architecture. Image decoders represent one of the most vital, yet vulnerable, attack surfaces in any contemporary web browser. These components process complex, completely untrusted binary structures directly from the internet. Moreover, they execute this code within the highly sensitive renderer process.
Historically, developers wrote these decoders using non-memory-safe languages such as C++. Consequently, these older implementations remained notoriously susceptible to severe vulnerabilities. These flaws frequently included out-of-bounds reads, dangerous heap overflows, and severe use-after-free bugs.
Therefore, Google proactively integrated jxl-rs to eradicate these security risks directly at their source. This tool is a pure Rust implementation of the JPEG XL decoder. To guarantee exceptional operational speed, Google deliberately incorporated secure SIMD instructions directly within the decoder. They also constructed a robust SIMD abstraction layer to manage this efficiently.
Furthermore, Chrome successfully incorporates the numerous performance optimizations inherent to jxl-rs. Google proudly stated that its dedicated team thoroughly vetted the jxl-rs implementation. They utilized rigorous AI-assisted reviews and extensive fuzz testing methodologies. Remarkably, these exhaustive tests uncovered absolutely zero memory safety issues throughout the entire development process.
