Back to Blog
Image ToolsTrendingWeb Performance

JPEG XL Is Coming to Chrome 155What to Do With Your Images Now

November 14, 20268 min read

On October 6, 2026, the Chrome team announced that Chrome is shipping support for JPEG XL, an image format it dropped four years ago. If you run a website, a blog or a store, the practical question is simple: do you need to change anything? Short answer: not today. This guide covers what happened, what it could mean for your images, and a safe way to prepare.

What Actually Happened

JPEG XL has had an unusual few years in Chrome. It arrived behind a flag, was removed, and is now coming back with a new decoder. The timeline below is based on Chrome's own blog and press coverage.

  1. 2021

    Chromium adds experimental JPEG XL support behind a flag.

  2. 2022

    Chrome engineers remove it, saying there is not enough interest across the ecosystem to keep experimenting.

  3. November 2025

    Google signals on the Blink mailing list that it intends to bring back JPEG XL using a memory-safe decoder written in Rust (jxl-rs).

  4. January 2026

    The Register reports that the decoder has been integrated into Chromium.

  5. February 2026

    Third-party coverage reports a JPEG XL decoder in Chrome 145, hidden behind a flag and off by default.

  6. October 6, 2026

    Chrome's developer blog says Chrome is shipping JPEG XL decoding starting from Chrome 155, and encourages developers to try both AVIF and JPEG XL.

One detail to keep in mind: the Chrome post we read does not say whether decoding will be switched on by default in Chrome 155, and the earlier Chrome 145 reports describe a flag only. Check Chrome's release notes before you plan around a specific date. Safari has supported JPEG XL since Safari 17, according to The Register, while other browsers are at different stages.

Why People Care About JPEG XL

Chrome's announcement describes JPEG XL as offering 30-50% better compression than JPEG, lossless compression, built-in HDR support and lossless JPEG transcoding. That last feature is the one that gets attention from anyone with a large library of existing JPEG photos, because it lets those files be recompressed without further quality loss.

The same post recommends trying both AVIF and JPEG XL to get the best results, and says JPEG XL is most helpful for high-fidelity or lossless compression, especially of photographic images, or when progressive decoding is preferred. In other words, Google is not telling you to throw out WebP or AVIF. It is adding another option to test.

Does Anything Change for You Today?

Your current images

JPEG, PNG, WebP and AVIF files keep working exactly as before. A new decoder does not remove an old one.

Your visitors

Browser updates roll out gradually, and not every browser is at the same stage. Expect a long period where many visitors cannot load .jxl files.

Your Core Web Vitals

Format affects speed through file size and decode time. Core Web Vitals consultant Arjen Karel notes that LCP is measured when the image is fully rendered, so progressive decoding does not directly improve the LCP number.

Your workflow

Nothing breaks. The sensible move is to prepare, measure and test, not to convert your whole library this week.

How to Adopt It Safely Later: Progressive Enhancement

When you are ready to test JPEG XL, do not replace your existing images. Add it as the first choice inside a picture element. The browser reads the sources from top to bottom and uses the first format it understands, so everyone else falls back to what you already serve.

<picture>
  <source srcset="photo.jxl" type="image/jxl">
  <source srcset="photo.avif" type="image/avif">
  <source srcset="photo.webp" type="image/webp">
  <img src="photo.jpg" alt="Describe the photo" width="1200" height="800">
</picture>
  • ✓Keep width and height on the img tag so the page does not shift while images load.
  • ✓Order matters: put the format you most want to serve first, and the most widely supported one last.
  • ✓Compare real files, not marketing claims. Encode a handful of your own photos in each format at a similar visual quality and look at the sizes.

Which Images Could Benefit?

Not every image gains from a new format. Here is a practical way to think about it, based on Chrome's guidance and the third-party benchmarks we could verify.

Photographs & product shots

The best candidate for JPEG XL. Chrome's own post points to high-fidelity or lossless compression of photographic images. Test it against AVIF and WebP at the same visual quality before you commit.

Logos, icons & flat graphics

Keep SVG or PNG where you can. Benchmarks vary, and one comparison cited by Core Web Vitals consultant Arjen Karel found AVIF smaller than JPEG XL for a small logo. Do not assume the newest format wins everywhere.

Screenshots & UI captures

Lossless WebP or PNG is already a solid choice. There is no urgent reason to change a working pipeline.

Your original photo archive

JPEG XL can recompress existing JPEG files losslessly, and the same article cites savings of roughly 20% for that case. Still, always keep your untouched originals.

Images inside PDFs

The PDF Association reportedly added JPEG XL to its specification in November 2025. Viewer support will lag, so for PDFs you share widely, stay with JPEG or PNG for now.

Animated graphics

Chrome's post encourages developers to use .jxl images and animations, but support details differ between browsers. Test on the browsers your visitors actually use.

A Five-Step Checklist You Can Do This Week

  1. 1

    Resize every image to the size it is actually displayed at. Oversized images waste bytes in any format. Our Image Resizer handles this in your browser.

  2. 2

    Compress at a sensible quality. The Image Compressor has a quality slider and a target-size mode, so you can aim for a specific file size.

  3. 3

    Serve WebP as your default. Use Image to WebP to convert JPEG and PNG files, and read our JPG vs PNG vs WebP guide if you are unsure which format suits which image.

  4. 4

    Keep your originals. Whatever you encode today, store the untouched source files so you can re-encode in newer formats later.

  5. 5

    Wait for data before adding .jxl. Read the Chrome 155 release notes, check your analytics for the share of visitors on recent Chrome versions, then run a small test on a few pages.

A transparency note: our image tools currently output JPEG, PNG and WebP, so you cannot create .jxl files here yet. Steps one to four still apply, because resizing and compressing before you encode is the biggest saving in every format.

The Bottom Line

JPEG XL returning to Chrome is good news for image quality and file size, but it is a slow-moving change, not an emergency. Keep serving the formats that work, tidy up your image sizes now, and test JPEG XL as an optional first choice once the browser numbers justify it. This post reflects Chrome's October 6, 2026 announcement and press coverage available as of November 14, 2026, so check the sources below for updates.

About This Article

Author, dates, reading time, references, and related resources for stronger context and trust signals.

Visit homepage

Frequently Asked Questions

When does JPEG XL arrive in Chrome?

Chrome's developer blog, published October 6, 2026, says Chrome is shipping JPEG XL decoding starting from Chrome 155. The post does not say whether it is on by default, so check the Chrome 155 release notes before you plan around it.

Is JPEG XL replacing WebP or AVIF?

Not on its own. Chrome's own guidance is to try both AVIF and JPEG XL and see which gives the better result for your images. WebP, AVIF and JPEG all keep working, and most sites will keep serving them as the baseline.

Will my existing images stop working?

No. A browser adding a new decoder does not remove support for formats it already handles. Your JPEG, PNG and WebP files render exactly as before.

Can I convert images to JPEG XL on thepdftools?

Not today. Our image tools output JPEG, PNG and WebP. Resizing and compressing images before you encode them in any newer format is still the biggest win, and those steps work with our free browser-based tools.

How should I add JPEG XL to my site later?

Use a picture element with a JPEG XL source listed first, then AVIF or WebP, and a JPEG or PNG img tag as the fallback. Browsers pick the first format they support, so visitors on older browsers are unaffected.