道場Dojo To the corridor
A samurai stands in front of a wall full of images, holding another picture.
All posts

道Dojo · · 3 min read

JPEG XL has landed. The XL is not a size guide

Chrome 155 and Firefox 158 now display JPEG XL by default. Why the new format is nice, but most websites have a very different image problem.

The samurai spent three days benchmarking AVIF, WebP and JPEG XL. Then he exported wearing gauntlets, and the only button big enough to hit said "Original size".

JPEG XL is now an ordinary image format for the web. According to web.dev's October round-up (29 October 2026), Chrome 155 and Firefox 158 have enabled image/jxl by default. Firefox even advertises the format in its Accept header. The same table lists Safari from version 17. Edge is still listed as unsupported.

On the Chrome blog (6 October 2026), Google cites 30 to 50 per cent better compression than JPEG. Add lossless compression, transparency, HDR and the option to repack existing JPEGs without any loss. Chrome's decoder is written in Rust, which lowers the risk of memory bugs. Sounds like a mandatory upgrade for every image. It isn't.

The format is rarely the problem

Our opinion after a lot of website projects: most images don't have the wrong format, they have the wrong size. A phone photo at 4032 × 3024 pixels goes straight through the CMS onto the homepage and is shown in a box 640 pixels wide. The browser loads just over twelve million pixels and displays around three hundred thousand. No format fixes that. An oversized JPEG XL is still oversized, just in nicer packaging.

Progressive rendering isn't a miracle cure either. JPEG XL can show a rough preview early, which feels faster. But corewebvitals.io (updated 4 November 2026) points out that Largest Contentful Paint only counts once the image is fully rendered. According to the same source, Safari doesn't decode progressively anyway. Feeling faster is nice, but it won't game your metrics.

How to use it sensibly

  1. Size first. Serve images at the dimensions they are displayed at, with srcset for several widths. Twice the width is plenty for high-resolution screens.
  2. Then the format. In a <picture> element, JPEG XL first, then AVIF or WebP, and a JPEG as the fallback. As long as Edge is missing, no format goes without a fallback.
  3. Test, don't trust. Google itself says JPEG XL is most helpful for high-fidelity and lossless compression and recommends comparing AVIF and JPEG XL. Worth testing for photos, less so for a small logo.
  4. Secure server-side delivery. If your server negotiates the format, you need Vary: Accept. Otherwise a cache may hand JPEG XL to browsers that can't read it.

Ideally, your CMS generates every size and format automatically from one large original. Then JPEG XL is just another tick box in the settings, and nobody on the team has to do pixel maths by hand. That's how we like to build websites.

This week's drill

Open your homepage in Chrome, right-click the largest image and choose "Inspect". In the developer tools, hover over the image URL after src. Chrome shows you two values: the rendered size and the file's intrinsic size. If the file is more than twice as wide as it is displayed, you've found your first job. Do it before you think about formats.

And in the export dialogue, from now on: the biggest button is rarely the right one.

Sources

  1. web.dev: New to the web platform in October (29.10.2026)
  2. Chrome for Developers: Shipping JPEG XL in Chrome (06.10.2026)
  3. CoreWebVitals.io: JPEG XL and Core Web Vitals (updated 04.11.2026)

Topics: bilderladezeitperformancewebentwicklung

読Read on