Firefox 157 will include JPEG XL by default on all platforms
groups.google.com
Firefox 157 will include JPEG XL by default on all platforms
1–10 of 137 posts
Re: Firefox 157 will include JPEG XL by default on all platforms
#2Re: Firefox 157 will include JPEG XL by default on all platforms
#3Re: Firefox 157 will include JPEG XL by default on all platforms
#4I'm curious how many HN people in 2026 have not yet heard of JPEG XL / jxl
Re: Firefox 157 will include JPEG XL by default on all platforms
#5--
Also, I was under the impression that after backtracking, Chromium was relying on Mozilla to come up with a Rust port, but it seems it was the reverse. Good on Google Research.
https://hacks.mozilla.org/2026/08/intent-to-ship-jpeg-xl/
> So, we laid down a challenge to the JPEG XL team at Google Research: Build a safe, performant, compact, and compatible JPEG XL decoder in Rust, and we’ll ship it. That challenge was met; Google Research built jxl-rs, and it’s the core of our JPEG XL support in Firefox.
Re: Firefox 157 will include JPEG XL by default on all platforms
#6Re: Firefox 157 will include JPEG XL by default on all platforms
#7I'm curious how many HN people in 2026 have not yet heard of JPEG XL / jxl
Re: Firefox 157 will include JPEG XL by default on all platforms
#8Chrome appears to be doing the same: https://groups.google.com/a/chromium.org/g/blink-dev/c/-gDoj...
Re: Firefox 157 will include JPEG XL by default on all platforms
#9Re: Firefox 157 will include JPEG XL by default on all platforms
#10I'm curious how many HN people in 2026 have not yet heard of JPEG XL / jxl
I have only heard of it in passing. I wonder what it adds beyond Webp and Avif.
Also webp is IMO subjectively worse at the same file sizes than the other two. Dunno if there's any studies on it to back that up though. It also has a max image size that is plausibly a problem in some use cases (16k in one dimension) while AVIF is 65k per axis and JXL 1M per axis.