Baring in mind that turning on jpegxl means exposing yet another image format parser to the web and the security track record of image formats has not been stellar.
Baring in mind that turning on jpegxl means exposing yet another image format parser to the web and the security track record of image formats has not been stellar.
IMO the killer feature of JPEG XL is its ability to losslessly transcode already existing JPEG images.
See also these articles for a more detailed comparison:
https://cloudinary.com/blog/how_jpeg_xl_compares_to_other_im...
https://cloudinary.com/blog/time_for_next_gen_codecs_to_deth...
(disclaimer: they were written by one of the authors of JPEG XL)
It's a nice transitory feature, but I think improved progressive decoding is even more worthwhile.
Features that actually matter to normal users are what is important.
In that area progressive display seems like it would arguably be more useful, though I think it would still be dependent on what the image size is - websites now routinely require megs of JS to display anything at all, because net speeds are now fast enough that huge amounts of data are needed to get to a “noticeable” latency that would warrant display of incomplete data.
WEBP has blurry chroma, looking like it's subsampled then upscaled. The chroma on JPEG-XL is trying to be full resolution, and if you look at the chroma in isolation, it looks a bit blocky, but it's not blurry at all.
The lossless recompression of existing .jpg content and faster software encoding for its native VarDCT format seem to provide immediate benefits in contexts where AVIF doesn't fit well now, either because AVIF encoding is slow or because AVIF would require a lossy reencoding of a lossily compressed source.