By insidethebox · · 4 min read

Chrome, Edge and Firefox now display JPEG XL by default, joining Safari. What the format is, how much smaller it makes images, and how to serve it with a fallback.

For three years JPEG XL was the image format the web almost had. In October 2026 that changed: every major browser now displays it by default. Here is what happened, what the format does, and what it means for your site.

You can try it on your own images with our free JPEG XL converter. It runs in your browser, so nothing is uploaded.

What happened

  • Chrome 155 and Edge 155 (6 October 2026) display JPEG XL by default, using jxl-rs, a new decoder written in Rust.
  • Firefox 158 (13 October 2026) turned JPEG XL on by default on desktop and Android, after the change slipped from Firefox 157. Its image requests now tell servers it accepts image/jxl.
  • Safari has displayed JPEG XL since version 17 in September 2023.

Browsers display JPEG XL but can't save or export it. To publish JPEG XL images you still need an encoder: libjxl's command-line tools, an image CDN, or a converter like ours.

What is JPEG XL?

JPEG XL (.jxl) is an image format standardised as ISO/IEC 18181, with the core codec published in 2022 by the JPEG committee. It is designed to replace JPEG, PNG and GIF with one format:

  • lossy and lossless compression
  • transparency and animation
  • HDR and wide colour gamut, at up to 32 bits per channel
  • progressive loading: a rough version of the whole picture first, then sharper passes
  • very large images, up to about a billion pixels per side
  • lossless JPEG recompression: a smaller copy of an existing JPEG that turns back into the exact original

How much smaller are the files?

We tested one 1600×900 photo, setting every format to the same visual quality: a SSIMULACRA 2 score of 80, which is high quality.

FormatSame quality (lossy)Every pixel kept (lossless)
JPEG140 kB—
WebP144 kB913 kB
AVIF104 kB—
PNG—1,585 kB
JPEG XL95 kB760 kB

At this quality, JPEG XL was 32% smaller than JPEG, 34% smaller than WebP and 9% smaller than AVIF. Lossless, it was 52% smaller than PNG and 17% smaller than lossless WebP. One photo is not a benchmark: AVIF tends to do better at lower quality, and results depend on the picture.

Lossless JPEG recompression

Most images already on the web are JPEGs. JPEG XL can repack a JPEG's compressed data more efficiently without decoding it to pixels. Our 2400×1350 test JPEG went from 320 kB to 271 kB, 15% smaller. Decoding it back produced a file identical to the original, byte for byte.

This means an archive or a CDN can store JPEG XL and still hand out the original JPEG to any client that asks for one. For now you need libjxl's tools: cjxl photo.jpg photo.jxl to recompress and djxl photo.jxl photo.jpg to restore.

Why Chrome removed it, and brought it back

Chrome added an experimental JPEG XL decoder behind a flag in 2021. In October 2022 the Chromium team announced they would remove it, citing too little interest from the wider ecosystem. Developers, photographers and companies objected loudly, and Apple shipped JPEG XL in Safari 17 a year later.

The turn came in November 2025, when the Chrome team said it would accept "a performant and memory-safe JPEG XL decoder". Image decoders are a common target for security exploits, so a decoder written in Rust removed the main objection. That decoder, jxl-rs, is what shipped in Chrome 155.

How to use JPEG XL on a website today

Serve it with a fallback, so every browser gets an image:

<picture>
  <source srcset="hero.jxl" type="image/jxl">
  <source srcset="hero.avif" type="image/avif">
  <img src="hero.jpg" alt="Describe the image" width="1600" height="900">
</picture>

Each browser takes the first source it can show. Keep width and height on the img so the layout doesn't shift while the image loads. If you use an image CDN, it can choose the format from the browser's Accept header instead.

Should you switch?

  • Photos on a content site or shop: add JPEG XL as the first <picture> source. Visitors on current browsers get smaller files; everyone else is unaffected.
  • Image archives and photo libraries: lossless JPEG recompression saves storage without risk, because the original can always be restored.
  • Keep your AVIF and JPEG fallbacks for now. Older browser versions stay in use for a while after a change like this.

For a side-by-side comparison of file sizes, features and browser support, read JPEG XL vs AVIF vs WebP. If you'd like help making a site faster, images included, see how we build websites or get in touch.

Sources

Topics: Engineering · Product

All insights