A report this week from Hacker News, linking to Google's official Chrome developer blog, confirmed that JPEG XL (JXL) is now shipping in Chrome after a prolonged and controversy-laden development cycle. Google had previously added experimental JPEG XL support behind a flag in Chrome 91 in 2021, then abruptly removed it in late 2022, citing insufficient ecosystem interest — a decision that drew significant backlash from photographers, archivists, and open-source developers. The reversal and formal ship represents a meaningful policy shift inside Google.
JPEG XL was developed jointly by the JPEG committee and standardized in 2022. The format supports lossless compression, HDR color, wide color gamut, alpha transparency, and progressive decoding, the last of which allows an image to render a low-resolution version almost immediately before filling in detail as data loads — a behavior absent from standard JPEG. According to figures cited in the Chrome developer blog post, JXL achieves roughly 60% smaller file sizes than legacy JPEG at comparable perceptual quality, and outperforms both WebP and AVIF on certain photographic content. The format also includes a lossless JPEG transcoding pathway, meaning an existing JPEG can be re-encoded to JXL and then decoded back to a bit-for-bit identical JPEG with no generation loss, which is technically distinct from any other widely deployed web image format.
Firefox shipped JXL support in version 128 in mid-2024. Safari had added it earlier, in Safari 17 in late 2023. Chrome's addition now brings all three major browser engines into alignment, a threshold the format needed to cross before content delivery networks and CMS platforms would begin defaulting to it.
For readers who maintain offline media libraries, local backups of family photographs, or archival copies of documentation — a routine practice in preparedness-minded households — the lossless JPEG transcoding feature carries specific relevance that general tech coverage tends to skip over. A substantial portion of long-term personal archives are stored as JPEG files, a format that loses data each time it is re-saved. JPEG XL's lossless re-wrap means existing JPEG collections can be consolidated into JXL containers that are smaller on disk and fully reversible to the original JPEG bytes on demand, without any of the quality degradation that occurs when re-encoding to WebP or AVIF. For anyone managing multi-terabyte photo archives on NAS drives or offline hard drives — where storage density and format longevity both matter — this is the operationally meaningful detail in an otherwise browser-centric announcement. Our NAS and offline storage guide touches on format choices in the context of long-duration archive planning.
Browser adoption does not automatically migrate existing web infrastructure. Image CDNs, WordPress, and major e-commerce platforms will need to add JXL encoding pipelines before the format becomes common on the open web. Several CDN providers, including Cloudflare, have indicated they are evaluating JXL support, but no broad rollout dates have been announced as of this writing.
