With the speed around #JpegXL picking up (now in #Firefox and #Chrome nightlies), I'm wondering what good use of an #HTML srcset would be there.

As JXL's progressive compression is good, we don't need different files in the srcset (so there's no need to load the first few KiB again when zooming in), but how can or should the HTML somehow tell the browser that for (say) up to 800px width it can request the Range: bytes=0-12345, and the next usable zoom level of 1600px needs the first 42KiB?

FFmpeg 8.1 brings JPEG-XS initial support for the low-latency, visually lossless JPEG-XS codec via the libsvtjpegxs library, useful for high-speed editing pipelines.

#FFmpeg #jpeg #jpegxl #lossless

The truth is, #WebP is only a stopgap. The real deal is #AVIF and ultimately #JPEGXL (.jxl).

JPEG-XL is superior in almost everything. In the very few cases that it is not, that's where AVIF comes in.

We can get rid of WebP, old JPEG, GIF, later on. Maybe even PNG and APNG.

😜🖖🏽

I hope the F-Stop Gallery app for Android gets updated with WebP and JPEG XL support.

For now, I switched to Fossify Gallery.

https://www.fossify.org/apps/

#Android #WebP #JPEGXL

Unfortunately, as of today, mainstream browsers still offer very limited support for JPEG XL. If you're as curious about it as I am — wanting to understand its origins and how to enable it in your browser to save bandwidth, or convert your existing JPEG images to JPEG XL format without loss of quality while freeing up at least 20% of your hard drive space — then I invite you to read my new blog post:
https://zaku.eu.org/blog/2026-03-05-the-rise-fall-and-resurrection-of-jpeg-xl/
Please feel free to leave a comment😄

#JPEGXL