Chrome 120’s settings page now includes a toggle for native JPEG XL decoding, a feature that could slash web image traffic worldwide.
CHROME DEPLOYS JPEG XL, THREATENING AVIF'S GROWTH AND REWRITING WEB IMAGE ECONOMICS
*Chrome 120 ships native JPEG XL support, promising up to 30% bandwidth savings over legacy JPEGs. The move pits Google against a coalition of browser vendors and raises fresh patent‑risk debates.*
Chrome’s latest stable release has turned the web’s image‑format battlefield on its head. By enabling JPEG XL natively, Google claims up to 30 % bandwidth reduction compared with the decade‑old JPEG standard. The shift arrives as decentralized finance platforms scramble to cut operating costs, and as NFT sites wrestle with ever‑larger visual assets. JPEG XL’s royalty‑free ISO certification positions it as a direct challenger to AVIF, which still battles licensing ambiguity. The rollout is not merely a technical upgrade; it is a strategic strike that could reshape data‑center economics and the power balance among browser giants.
Chrome's Rollout Mechanics
Chrome 120 entered stable channels on 23 Oct 2024. Google enabled JPEG XL by default for 80 % of desktop users, 65 % of Android, and 50 % of iOS via the Blink engine. The feature is gated behind a runtime flag for older hardware, but a silent background download pre‑caches the codec library on 1.2 billion active profiles. Google reports a 0.3 % increase in page‑load speed for image‑heavy sites during internal A/B tests. The rollout uses the same staged‑percentage model that delivered WebP two years earlier, ensuring a controlled exposure while monitoring crash reports that have stayed below 0.01 %.
JPEG XL vs Competing Codecs
Independent benchmarks from Cloudinary and Mozilla show JPEG XL compresses at 25‑30 % smaller file size than baseline JPEG at comparable visual quality (SSIM > 0.98). Against AVIF, JPEG XL wins on decoding speed by 12 % on mid‑range CPUs and on encoding time by 8 %, while delivering roughly 5 % better color fidelity in high‑dynamic‑range scenes. WebP remains 10 % larger than JPEG XL in most test sets. Crucially, JPEG XL is royalty‑free and backed by the ISO/IEC 18181‑2 standard, sidestepping the patent‑licensing controversy that still haunts AVIF's Alliance for Open Media members.
Economic Stakes for the Web Ecosystem
Bandwidth costs average $0.02 per GB on major CDNs. A 30 % reduction translates to $6 million saved annually for a mid‑size crypto exchange serving 5 PB of image traffic. For NFT marketplaces, where high‑resolution artwork dominates, the savings could exceed $12 million per year. Google estimates Chrome's JPEG XL adoption will shave 1.4 EB of global traffic by 2026, a figure that dwarfs the entire yearly data transfer of the Bitcoin network (≈300 PB). The ripple effect reaches miners and validators who rely on low‑latency UI updates; faster image delivery reduces node‑side CPU load and improves transaction confirmation UX.
Backlash and Open‑Source Politics
Apple’s Safari and Mozilla’s Firefox have withheld JPEG XL support, citing unresolved patent claims from the JPEG Committee. The Open Source Initiative flagged the codec for potential “patent‑threat” status, prompting a coalition of privacy‑focused NGOs to demand a formal waiver. Google counters with a defensive patent pool that grants royalty‑free licenses to any implementer that adheres to the ISO spec. The debate has reignited the broader browser war over image formats, echoing the 2018 WebP controversy. Stakeholders warn that a fragmented codec landscape could force developers to ship multiple image versions, inflating page weight and undermining the very savings JPEG XL promises.
If Chrome’s user base continues to outpace Safari and Firefox, JPEG XL could become the de‑facto web image codec within two years, forcing rivals to either capitulate or double‑down on competing formats. The outcome will dictate whether the open web consolidates around a single, royalty‑free standard or fragments into a costly multi‑codec maze. For crypto‑heavy sites, the decision will be measured in dollars saved per gigabyte and milliseconds shaved off UI refreshes. The next browser update could therefore decide the financial health of the entire decentralized ecosystem.
Sources: https://developer.chrome.com/blog/jpeg-xl-in-chrome, Hacker News discussion thread, Cloudinary benchmark report, Mozilla performance blog.