NextFin News - On February 10, 2026, Google officially announced the release of Chrome 145 to the stable channel, introducing a suite of updates for Windows, macOS, and Linux. The most significant technical milestone in this version is the reintroduction of JPEG-XL (JXL) image decoding support. According to Phoronix, this marks a major reversal of Google's 2022 decision to deprecate the format, which at the time was cited as having insufficient ecosystem interest. The new implementation is notably built on a Rust-based decoder, jxl-rs, prioritizing memory safety over the traditional C++ libraries.
The release of Chrome 145 is not merely a routine update but a calculated response to the evolving needs of the global web infrastructure. Beyond JPEG-XL, the update includes support for the text-justify CSS property, column wrapping in multi-column layouts, and a transition to an SQLite backend for IndexedDB. However, the return of JPEG-XL is the centerpiece, currently gated behind the "enable-jxl-image-format" flag. This phased rollout allows Google to monitor performance and stability before a full-scale activation, reflecting a cautious yet committed approach to modernizing web media standards.
The decision to bring back JPEG-XL highlights a significant shift in the competitive landscape of image codecs. For years, the industry has been caught in a tug-of-war between AVIF, backed by the Alliance for Open Media, and JPEG-XL. While AVIF excels at high compression for low-bitrate scenarios, JPEG-XL offers superior fidelity for high-quality photography and professional-grade imagery. By re-integrating JXL, Google is acknowledging that a single codec cannot satisfy the diverse requirements of the modern web, where high-resolution displays and professional creative workflows demand more than what AVIF or the aging WebP can provide.
From a technical standpoint, the choice of a Rust-based decoder is a strategic move aligned with broader industry trends toward memory-safe programming. Memory vulnerabilities in C++ decoders have historically been a primary attack vector for browser exploits. By utilizing jxl-rs, Google is leveraging the safety guarantees of the Rust language to harden the browser's perimeter. This move is particularly relevant under the current administration, as U.S. President Trump has emphasized the importance of cybersecurity and domestic technological resilience. Ensuring that the world's most popular browser is resilient against memory-based attacks is a critical component of national digital infrastructure security.
The economic implications for web developers and content delivery networks (CDNs) are substantial. JPEG-XL allows for the lossless recompression of existing JPEG files, potentially reducing storage requirements by up to 20% without any loss in quality. For large-scale platforms like Facebook or Shopify, which manage petabytes of image data, this translates into millions of dollars in saved bandwidth and storage costs. Furthermore, the format's support for progressive decoding means that images can appear sharper faster even on slower connections, improving user retention and conversion rates for e-commerce entities.
Looking forward, the re-adoption of JPEG-XL by Google is likely to trigger a domino effect across the browser ecosystem. While Apple's Safari has already shown experimental support for the format, the weight of the Chromium engine—which powers Microsoft Edge, Brave, and Vivaldi—will effectively force the hand of web developers to begin serving JXL files. We can expect a surge in CDN support and image processing libraries over the next 12 months. As the web moves toward more immersive and visually demanding experiences, the flexibility and efficiency of JPEG-XL will likely position it as the dominant successor to the original JPEG standard, finally ending the decade-long search for a true universal replacement.
Explore more exclusive insights at nextfin.ai.
