JPEG XL returns to Chrome and Firefox: What photography gains and what is still missing?
Most cameras today deliver 12 or 14 bits per channel, and JPEG keeps 8. The loss happens at the end of the work, when the photo is already edited and it is time to save it. The ceiling does not come from the sensor: it is set by the format, defined in 1992, when today's cameras did not exist.
JPEG XL has existed for years and targets exactly that point. It handles lossy and lossless compression, supports up to 32 bits per channel, and converts an old JPEG without recompressing it: the file is about 20% smaller and the original comes back bit for bit. The news is that Chrome 155 and Firefox 158 open it by default, and that Safari has done so since version 17.
JPEG XL is not new, and yet the question is why we keep saving in JPEG. The return to browsers puts the topic back on the table, but it does not change the core: the obstacle is not in the browser.
A format does not win on quality alone
Before JPEG XL there were JPEG 2000 and WebP. The first compressed better and ended up in digital cinema, medical imaging and archives that must preserve originals for decades. The second was reasonable for the web and loaded fast, but it was still limited to 8 bits per channel.
Neither replaced JPEG, and it was not for technical merit. Changing a standard involves cameras, monitors, labs, software and millions of files already saved. Compatibility comes first, and cost follows.
Chrome had it in testing since April 2021 and removed it in December 2022, with version 110. The reasons it gave were a lack of ecosystem interest, improvements that did not justify maintenance, and a wish to focus on the formats that already existed.
The loss becomes visible when editing. Gradients in a sky break into steps and there is less room to recover highlights, because that information is no longer in the file. A 14-bit RAW stores 16,384 levels per channel; a JPEG stores 256.
The format survived outside Chrome
The return did not come from a campaign. It came from pieces adding up. Safari added it in version 17, along with macOS Sonoma and iOS 17, though with a limitation: still images only and no progressive decoding. Adobe added support in Lightroom Classic and Photoshop, and in Capture One a third-party plugin appeared that exports at 16 bits.
Firefox needed more than goodwill: a safe decoder. Mozilla had discarded the C++ reference decoder because of the attack surface it added to a browser, and in January 2026 it adopted a version written in Rust. Since 158 it opens it by default.
AVIF, built on the AV1 video codec, is still the best option for lightweight, fast publishing. The advantage flips when quality is the measure: JPEG XL wins on high-quality images, while AVIF tends to smooth grain and fine detail when compression is aggressive.
The limit is in the camera
Having a browser does not change how images are captured. Almost no body offers JPEG XL as a save format, so the workflow stays the same: RAW or JPEG in the camera and the decision about the file afterwards. The known exception is Apple, where the iPhone 16 Pro compresses in JPEG XL when shooting ProRAW.
The most profitable use today is the master file. Saving an edited photo with 16-bit depth required a huge TIFF. JPEG XL keeps depth, dynamic range and profiles, at a size that can be far below the TIFF.
For a photographer, the useful change is not being able to see the format in a browser. It is that the master stops being a TIFF of hundreds of megabytes and that a light copy comes out of the same file, without duplicating work or choosing between quality and space.
The test is cheap. Export one photo, compare its size, open it with the program already in use and look at the detail on the monitor. If it convinces, the format enters the master archive; if not, there is nothing to migrate. What does not make sense is moving an entire catalogue because of a version announcement.
Useful links
Some links may be affiliate links (sponsored).