Crawling

Chrome 155 now opens JPEG XL: 30 to 50% lighter than JPEG

Chrome decodes JPEG XL (.jxl) since version 155, stable since October 6. Google dropped it in 2023 for “lack of interest” but has changed its mind.

Chrome 155 now opens JPEG XL: 30 to 50% lighter than JPEG
Author
Carlos Sánchez
Topics
Crawling Technologies
Published
Reviewed

Chrome accepts JPEG XL again: it had dropped it in 2023 for "lack of interest", but has changed its mind. It promises 30 to 50% better compression than JPEG with no noticeable loss of quality. With Safari and, as of today, Firefox, the format can now be served in the three major browsers.

The announcement comes from the Chrome team on its developer blog: Chrome adds JPEG XL decoding support starting with Chrome 155. According to the Chromium schedule, that version reached the stable channel on October 6, the same day as the post. 

Google describes JPEG XL as a "next-generation" format that offers "30 to 50% better compression than JPEG, lossless compression, built-in HDR support, lossless JPEG transcoding and more".

The recommendation is not to replace AVIF but to combine both next-generation formats to get the best results.

Quality and weight: what each format offers

On paper, the differences lie in how each format compresses and in what it's able to store. The data comes from MDN's image format guide and, for JPEG XL, from its official website.

FormatCompressionTransparencyAnimationBits per channelProgressive loading
BMPSupports several, but is usually stored uncompressedYesNo8 and 16No
PNGLosslessYesYes, as APNGUp to 16Interlaced
JPEGLossyNoNo8Yes, as progressive JPEG
WebPLossy or losslessYesYes8No
AVIFLossy or losslessYesYes8, 10 and 12No
JPEG XLLossy or lossless, plus lossless recompression of a JPEG (20% smaller on average)YesYesUp to 32Yes

In practice, JPEG XL brings together what previously had to be split across formats: lossless like PNG, lossy like JPEG or WebP, HDR and wide colour gamut like AVIF, and progressive loading like progressive JPEG. Its official website claims it is "visually lossless at less than half the bits per pixel of JPEG".

The same image in five formats

An example with the same 400 × 475 pixel illustration. The first four versions are the ones from Carlos Sánchez's article on WebP; he exported the JPEG XL one from the same image.

BMPPNGJPGWebPJPEG XL
The sample image in BMPThe sample image in PNGThe sample image in JPGThe sample image in WebPThe sample image in JPEG XL
742 KB227 KB53.8 KB44.5 KB27.9 KB

If the JPEG XL image doesn't show, your browser can't open the format yet: you need Chrome or Edge 155, Firefox 158 or Safari 17.

BMP and PNG store the image losslessly, which is why they're so heavy; JPG and WebP compress it lossily. The JXL weighs 37% less than the WebP and 48% less than the JPG. Part of that difference is metadata: the PNG, the JPG and the WebP each carry about 13 KB of EXIF, XMP and colour profile, and the JXL carries none. Without them, the JXL is still the lightest: 12% less than the WebP and 31% less than the JPG, which also measures 400 × 449 and has slightly less image than the others.

This is how it looks in Chrome Canary with version 157:

jpgxl quality
It keeps practically the same quality while weighing much less

Let me know in the comments if you'd like AVIF added to the experiment

How to implement it

The recommendation would be to insert it inside a <picture> element with a <source type="image/jxl"> ahead of the AVIF, WebP or JPEG fallback, or with negotiation via the Accept header on the server or CDN. Google Search indexes the image in the src attribute of the fallback <img>, and Google's image documentation only supports BMP, GIF, JPEG, PNG, WebP, SVG and AVIF in that attribute, so the fallback still has to be one of those formats.

Where it shows most is in the weight: fewer bytes per image improve LCP when the large image is the main element, and lossless transcoding lets you convert an existing JPEG catalogue to JXL without recompressing and go back if needed. The sensible test is to take the ten heaviest images on the site, encode them in AVIF and in JXL at the same visual quality and compare sizes, as Google suggests.

A Rust decoder so history doesn't repeat itself

Chrome already had JPEG XL behind an experimental flag and removed it in 2023, citing a lack of interest from the ecosystem. The comeback rests on two things. The first is technical: image decoders "are one of the most critical and attacked surfaces of any modern browser", because they process binaries from the network inside the rendering process, and those written in C++ have led to memory bugs. That's why Chrome integrates jxl-rs, a decoder implementation "written entirely in Rust", with SIMD instructions isolated in "a small number of heavily reviewed places". Google says it has verified it with fuzzing and AI code review without finding "a single memory safety bug in the entire history of the implementation".

The second is demand: the decision "was based on the constant feedback and requests from web developers, seen above all in the Interop process, where it was a popular proposal in 2026 and several years before". Chrome has taken part in the Interop 2026 JPEG XL investigation so that there's test coverage of all the format's features across browsers.

Where it works today

BrowserJPEG XL support
ChromeSince 155 (stable on October 6, 2026)
SafariSince 17 (2023), still images; no animation or progressive decoding, according to caniuse
FirefoxSince 158, scheduled for release on October 13, 2026, according to caniuse and Mozilla's calendar
EdgeSince 155, according to MDN

References

  1. caniuse.com (2026, October 13). JPEG XL image format. https://caniuse.com/jpegxl (browser support, accessed October 13)
  2. Chrome for Developers (2026, October 6). Shipping JPEG XL in Chrome. https://developer.chrome.com/blog/jpeg-xl-in-chrome?hl=en Main source
  3. chromiumdash.appspot.com (2026, October 13). Chromium Dash: release schedule. https://chromiumdash.appspot.com/schedule (Chrome 155 stable on October 6, 2026)
  4. GitHub (2026, October 13). Interop 2026 proposal: JPEG XL. https://github.com/web-platform-tests/interop/issues/994 (the Interop proposal Google cites)
  5. Sánchez, C. (2022, March 4). SEO-focused Picture tag. sanchezdonate.net. https://sanchezdonate.net/articulo/etiqueta-picture/
  6. whattrainisitnow.com (2026, October 13). Firefox 158 release schedule. https://whattrainisitnow.com/release/?version=158 (Mozilla's schedule for version 158)

Original content under a CC BY 4.0 licence, translated and expanded.

If you like this article, you would help me a lot by sharing my content:
Training
Interested in Advanced SEO Training?

I currently offer advanced SEO training in Spanish. Would you like me to create an English version? Let me know!

Tell me you're interested
You might be interested in other articles:
SEO Articles