Huge fan of JXL, but this article feels pretty AI sloppy. Not much said here, coming from the google blog I was hoping for some news about how they are pushing the format forward by introducing decoders in to Android and enabling on Chrome.
Android is the only mainstream OS that does not support JPEG XL right now.
I'm generally pretty pro-AI, but I find this icky. Of course, I wouldn't have noticed except the whiteboard drawing seemed not quite right, so I'll probably be fooled in the future.
Based on what I've heard, Google is monitoring per-org usage and strongly / incessantly encouraging teams to experiment with the technology, so a lot of tokens get spent on pointless stuff like that. The preceding diagram, which is needlessly busy and blurry, appears to be AI-generated too.
> That's rich coming from the company that tried to kill it
This post is written by three of the authors of the JPEG XL spec, implementors of the reference and rust implementations of libjxl, and...longtime google employees.
Yeah, but they left out that Chrome removed their own support for JPEG XL saying no one in the industry was in favour of it despite everyone seeing it was the future screaming for it and building support for it into their own products.
Chrome's blink was the only major browser engine not supporting it and that prevented it from becoming a web standard and they refused to acknowledge they were wrong.
Chrome only backtracked once jpeg-xl was subsumed into the PDF standard because if Chrome did not support jpeg-xl, they would by extension also not be supporting pdf.
jpeg xl is also now used for the latest version of the DNG raw image format, and the iphone now encodes raw images as jpeg xl in DNG. It's so clearly the future for photography that Google is holding back. Apple surprisingly has been the first with full support everywhere in their OSs and in Safari.
Probably got some time to go. The new rust decoder likely needs more time to be proven reliable and safe, and Firefox doesn't even get the flag to turn it on until the next release 152.
Android is the only mainstream OS that does not support JPEG XL right now.
I'm generally pretty pro-AI, but I find this icky. Of course, I wouldn't have noticed except the whiteboard drawing seemed not quite right, so I'll probably be fooled in the future.
Here's a blog post by him: https://cloudinary.com/blog/2026-the-year-of-jpeg-xl
This post is written by three of the authors of the JPEG XL spec, implementors of the reference and rust implementations of libjxl, and...longtime google employees.
Chrome's blink was the only major browser engine not supporting it and that prevented it from becoming a web standard and they refused to acknowledge they were wrong.
Chrome only backtracked once jpeg-xl was subsumed into the PDF standard because if Chrome did not support jpeg-xl, they would by extension also not be supporting pdf.
Looks like by the end of the year we can expect Chrome and Firefox support.