Yes. They're adding it back to Chrome.

This last January at FOSDEM there was a panel with representatives from different browser companies. During the panel Kadir Topal, a web platform product manager at Google, indicated that because of the interest they saw in JPEG XL through the Interop Project that they changed their course on supporting it.

https://github.com/web-platform-tests/interop

The video of the panel can be found at https://fosdem.org/2026/schedule/event/7E7387-browser_in_202... . He starts speaking on the issue at about 13:00

That is a very cherishable way to put it. In realty JXL has been on one of the highest request in Interop for at least 2 if not 3 years, and both Microsoft Edge and Safari have spoken about frustration of "certain features" not being implemented despite high number of votes.

Safari is currently lacking animation and progressive decoding - still ahead of everyone else currently.

Looks like by the end of the year we can expect Chrome and Firefox support.

He only mentioned decode complexity. Would be interesting to know the average encode complexity compared to AV1.

Encoding speed even on Mac Studio is atrocious, it’s in range of single frames per second as opposed to realtime+ for even h265

The specification for AV2 has only been finalised very recently, so performant encoders have not yet been developed. Meaningful comparison to older codecs like H265 and AV1 will only be possible once that has changed. (It'll be slower, but almost certainly not one-frame-per-second slow.)

Getting the full bitrate gains will be slower.

For any specific bitrate and quality target, there's a good chance it'll be faster.

Perhaps you meant lossy? Everything I'm seeing says that Opus does not support lossless.

I believe they meant saving space by converting a lossless collection to a good lossy format like Opus.

Google Research was central in developing and continuing to push JPEG XL.

The Google Chrome folks are the ones who decided to disallow it. You could argue that they are trying to kill it, but certainly not Google at large.

Lots of people are using AV1. They just don't know it.

I believe MacOS has full support. Windows now has support available as a free installable plugin.

Mozilla said that the current decoder state was unacceptable but if Google Research wrote them a Rust version that met their shippable criteria they'd ship it. That's planned to be done this summer. So I'm optimistic Firefox will ship support (courtesy of Google Research) within the year.

That would just leave Chrome support and Windows to ship by default. I'm hoping Firefox's support would cause pressure on the Chrome team.

Goodly amount of static here - unclear to me how much of it is added and how much is original.

https://www.my80stv.com/

Ok, so this is one step in such hyper-fast data transmission. What would be the other hurdles?

*she