Do Son 
Google recently announced that the official release of Chrome 155 natively supports decoding the JPEG XL image format by default. As a result, browsers can now directly display JXL images and animations without requiring users to install extensions or enable experimental features. Previously, Google reinstated support for the JXL image format and introduced a decoder. However, this functionality required users to enable experimental options. With the advent of Chrome 155, the JXL decoder is now activated by default as an official, robust feature.
Balancing Compression, Image Quality, and HDR
Built upon the ISO/IEC 18181 standard, JPEG XL is a sophisticated image format that supports both lossy and lossless image compression. It also supports high dynamic range (HDR), immense color depth, seamless animations, and progressive decoding. Notably, progressive loading allows the system to present a preliminary overview of the image. Then, it can meticulously refine the intricate details.
Google asserts that at comparable visual fidelity, JPEG XL can achieve remarkable compression benefits ranging from 30 to 50 percent when compared to traditional JPEG. Furthermore, this innovative format facilitates lossless transcoding of existing JPEG files. Doing so significantly reduces file sizes while flawlessly retaining the ability to restore the original image. However, the actual efficacy of this process inherently fluctuates depending on the image content and specific compression parameters.
Navigating Compatibility Concerns for Web Developers
The Google Chrome development team strongly advises developers to test both JPEG XL and AVIF image formats simultaneously based on their source materials. Among these, JPEG XL proves exceptionally suited for high-fidelity, losslessly compressed photographs and scenarios demanding progressive loading capabilities. As detailed in the official blog post regarding JPEG XL in Chrome, smaller image files hold the promise of drastically reducing the sheer volume of data transmitted by websites. Nevertheless, website administrators must still ensure their image processing systems, CDN distribution networks, and upload verification interfaces comprehensively support the JXL format.
Although mainstream browsers have gradually embraced the JXL format, various niche or legacy browsers inevitably lack support. Consequently, websites must meticulously address compatibility concerns by providing fallback resources, such as JPEG, WebP, or AVIF files, when JXL fails to load. Naturally, this redundancy will consume additional server storage space.
Apple’s Support: The Catalyst for JPEG XL’s Survival
The JPEG XL format actually debuted quite early, and Google Chrome offered preliminary support long before version 110. However, due to the sluggish development of the surrounding ecosystem, Google abruptly announced the removal of all JPEG XL support and experimental features upon the release of Chrome 110. Fortunately, Apple later integrated robust support for JPEG XL across its iOS and related operating systems. This pivotal move prompted countless developers to implore Google to reinstate its support. Ultimately, this compelled Google to orchestrate the triumphant return of JPEG XL.
Beginning its rollout on October 7, all iterations of Chrome 155, encompassing Windows, Linux, macOS, and Android platforms, now fully support the JXL image format. As time progresses, an ever-increasing multitude of websites will undoubtedly adopt the brilliant JXL image format.
Support Our Threat Intelligence
Find our tech and OS security coverage helpful? Support our work today and unlock a 100% ad-free reading experience!
Buy Me a Coffee
