Do you have a general stance about it?

Once every couple of months I look into the state of both projects and it’s slow but steadily progressing.

I am mainly looking into it because of the file compression. My tests showed that I can save up to 70% in disk space for a jpg image without losing too much information for both formats, avif and jxl. It depends on the images but in general it’s astonishing and I wonder why I still save jpgs in 100% quality.

But, I could also just save or convert my whole library to 70% jpg compression. Any advice?

  • Yote.zip@pawb.socialEnglish
    1·
    1 year ago

    JXL is the best image codec we have so far and it’s not even close. I did a breakdown on some of its benefits here. JXL can losslessly convert PNG, JPG, and GIF into itself, and can losslessly send them back the other way too. The main downside is that Google has been blocking its adoption by keeping support out of Chromium in favor of pushing AVIF, which started a chicken and egg problem of no one wanting to use it until everyone else started using it too. If you want to be an early adopter you can feel free to use JXL, but just know that 3rd party software support is still maturing.

    Something you might find interesting is that the original JPEG is such a badass format that they’ve taken a lot of their findings from JXL and made a badass JPEG encoder with it named jpegli. Oddly, jpegli-based JPEGs are not yet able to be losslessly-compressed into JXL files, per this issue - hopefully that will be fixed at some point.