Viewing profile — jonsneyers

Exactly. Image compression should excel at avoiding excess. Though maybe some people think the JPEG committee is now creating spreadsheet formats...

JPEG XP would have been a nice name for a successor of JPEG 2000, I suppose :) There's also a JPEG XE now ( https://jpeg.org/jpegxe/index.html ), by the way.

PNG can and is often used in a lossy way. Reducing the number of colors so PNG8 can be used instead of PNG24/PNG32 is the most common way to do that. Tools like pngquant exist, and…

It's technically correct. Googlers (at Google Research Zurich) have been working on jxl-rs, a Rust implementation of JPEG XL. Google Research has been involved in JPEG XL from the …

For lossless, bitdepth of course does matter. Lossless image compression is storing a 2D array of integer numbers exactly, and with higher bitdepth, the range of those numbers grow…

Thanks! Yes, my hope is that jxl can become an interoperable format for layered images. It does not have all the functionality of image editor formats (PSD, XCF, etc), but it does …

This article is from 2020. I think so far it has aged reasonably well. But you might be interested in my more recent articles too. You can find those here: https://cloudinary.com/b…

Last time I tested, libjxl e1 had a better compression ratio than default libpng, while being two orders of magnitude faster. See https://cloudinary.com/blog/jpeg-xl-and-the-pareto…

Lossless compression is not about importance of data. Lossless is lossless, if the result of a roundtrip is not EXACTLY IDENTICAL then it is by definition not lossless but lossy. M…

The above claims are not very accurate. JPEG and JPEG 2000 were based on the principle that the core codec was royalty-free but there might be patent-encumbered optional things (su…

JPEG XL is a royalty-free codec and "generating revenue streams" was never a goal for the project. You can see this already in the very first draft call for proposals from 2017: ht…

Chair of the JPEG XL adhoc group of JPEG here. I wasn't around when the name for this project was chosen (I only got involved after the call for proposals, at which point the codec…

Thanks for the suggestion, oxipng is indeed a better choice. Next time I will add it to the plots!

It is unlikely that there will be any bitstream changes in JPEG XL. There is still a lot of potential for encoder improvements within the current bitstream, both for lossy and for …

No it doesn't. And yes, regular JPEG is still a fine format. That's part of the point of the article. But for many use cases, better compression is always welcome. Also having feat…

Assuming the websites are using images of appropriate dimensions (that is, not using huge images and relying on browser downscaling, which is a bad practice in any case), you can q…

Humans generally tend to prefer smoothing over visible blocking artifacts. This is especially true when a direct comparison to the original image is not possible. Of course differe…

It has lossless just to check a box in terms of supported features. A bit like how JPEG XL supports animation just to have feature parity. But in most cases, you'll be better off u…

You are right, but that would make an uglier plot :) Some of the intermediate options are available though, through various more fine-grained encoder settings than what is exposed …

This matters way more for video (where you are decoding 30 images per second continuously) than it does for still images. For still images, the main thing that drains your battery …

Safari/Webkit has added JPEG XL support already. Firefox is "neutral", which I understand as meaning they'll do whatever Chrome does. All the code has been written, patches to add …

Lossless WebP is very good indeed. The main problem is that it is not very future-proof since it only supports 8-bit. For SDR images that's fine, but for HDR this is a fundamental …

Both rav1e and libaom have a speed setting. At similar speeds, I have not observed huge differences in compression performance between the two.

No browser bothers with hardware decode of WebP or AVIF even if it is available. It is not worth the trouble for still images. Software decode is fast enough, and can have advantag…

There are no royalties to be paid on JPEG XL. Nobody but Cloudinary and Google is claiming to hold relevant patents, and Cloudinary and Google have provided a royalty free license.…