What happened

Google announced on its Chrome for Developers blog on 6 October 2026 that Chrome is shipping decoding support for the JPEG XL (.jxl) image format starting from Chrome 155. The Chrome 155 beta notes, published on 16 September 2026, describe the change as JPEG XL decoding in Blink, Chrome's rendering engine, using jxl-rs, a decoder written entirely in the Rust programming language. The beta notes list Android, ChromeOS, Linux, macOS and Windows as the platforms for the release.

In practice this means a website can serve .jxl images and Chrome users will see them without enabling any experimental setting.

Why the decoder matters

Image decoders process complex files straight from the internet, which makes them a common target for attacks. Google says it chose a pure Rust implementation to remove whole classes of memory-safety bugs at the source, rather than relying only on Chrome's sandbox. The team also reports extensive work to make the Rust decoder fast enough to compete with the existing C++ library.

What JPEG XL offers

JPEG XL is standardised as ISO/IEC 18181. According to the Chrome team, its features include:

  • Progressive decoding, so a recognisable image appears early while the rest loads.
  • Wide colour gamut, HDR and high bit depth, useful for modern cameras and displays.
  • Animation.
  • Lossless compression, and the ability to repackage existing JPEG files losslessly into a smaller JPEG XL file.

Google's announcement claims 30–50% better compression than JPEG. That is the Chrome team's figure; actual savings depend on the image and the settings used. Google does not present JPEG XL as a replacement for AVIF. It recommends trying both, and expects JPEG XL to be most useful for high-fidelity or lossless compression, especially of photographs, and where fine-grained progressive loading is wanted.

Should you switch to .jxl?

Not on its own yet, for most people:

  • Website owners can start offering JPEG XL alongside a fallback, using the HTML <picture> element so browsers that cannot display .jxl receive JPEG, WebP or AVIF instead.
  • Everyday users should keep sharing photos as JPG or PNG. Messaging apps, email clients, office software and older devices may not open .jxl files.
  • Photographers interested in lossless archiving can experiment, but should keep originals in established formats until their editing and backup tools fully support JPEG XL.

For an overview of the trade-offs, see our comparison of AVIF, WebP and JPEG XL and the practical JPG, PNG and WebP guide.

Does Convertios support JPEG XL?

Not at present. The Image Converter outputs JPG, PNG, WEBP, BMP and GIF, and the Image Compressor works with JPG, PNG and WEBP. Neither creates .jxl files, and we have not tested or listed JPEG XL as a supported input. We will review this as support across browsers and operating systems matures.