Journey to JPEG XL: open-source experiments shaped the future of image coding
ledoge
60 points
31 comments
June 03, 2026
Related Discussions
Found 5 related stories in 104.4ms across 10,002 title embeddings via pgvector HNSW
- JPEG Compression 7777777phil · 20 pts · March 14, 2026 · 57% similar
- Perceptual Image Codec: What Matters in Practical Learned Image Compression ksec · 107 pts · May 24, 2026 · 52% similar
- Celebrating Interesting Flickr Technologies steerpike · 14 pts · March 12, 2026 · 46% similar
- Coding Agents Could Make Free Software Matter Again rogueleaderr · 141 pts · March 29, 2026 · 46% similar
- FFmpeg at Meta: Media Processing at Scale sudhakaran88 · 239 pts · March 09, 2026 · 45% similar
Discussion Highlights (10 comments)
rowbin
That's rich coming from the company that tried to kill it. The audacity...
lousken
Out of experimental when?
Mindless2112
> In this Gemini-reconstructed scene, ... 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.
neuroelectron
AI slop article
yboris
Weird they don't name Jon Sneyers - a person pivotal in creation of JPEG XL Here's a blog post by him: https://cloudinary.com/blog/2026-the-year-of-jpeg-xl
Gigachad
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.
bnolsen
I personally think something like the qok format is a better way to go. Make something that performs well and is dirt simple to implement.
LoganDark
I'm behind -- did Chrome un-remove JXL support? Google is suddenly behind it again? Why/how did they change their minds?
201984
Mostly off topic, but why is the spec for JPEG and JPEG XL paywalled? I wouldn't call them open standards if they're not available free-of-charge to the public.
_HMCB_
Google spearheaded this and yet their browser only has experimental support? While Safari shipped it in 2023? At least, that’s how I’m reading this.