JPEG XL faces fierce competition from AVIF. And Google. A bit of both0:00 - What is JPEG?1:20 - JPEG XL2:07 - AVIF3:08 - JPEG XL's Strengths4:58 - AVIF Suppo...
image compression standards are my jam so i watched the video.
jpeg is a decades-old lossy image compression format that’s historically been pretty good for its purpose of storing adequate quality images while conserving space and especially bandwidth. but there are modern alternatives that are better, including jpeg xl that the author highlights as especially useful because it’s backwards compatible with old jpeg files. and one of the video author’s main arguments is that jpeg xl is robust and future-proof, it will continue to be a file format that’s shareable and readable for many years or even decades to come.
but the modern internet ecosystem (meaning google chromium browser which dropped support for jpeg xl last year) seems to be gravitating towards avif, the av1 image format. it’s a file format for still images based on the av1 video compression algorithm that’s focused more towards maximizing compression, and isn’t backwards compatible with jpeg. another big issue with avif is that it caps out at 12 bits of color resolution compared to 32 bits of color resolution in jpeg xl, which can lead to some unsightly compression artifacts.
jpeg xl is also a much simpler format to encode and decode so it uses less hardware capacity and therefore energy use when creating and displaying many images. and jpeg xl supports progressive decoding, loading up and displaying an initial low quality version of the image and filling it in with finer details, rather than having to load and decode the entire image at once. he also complains about avif headers causing problems, things that will make it more difficult to even read the files in the future, potentially.
that’s about what i got out of the video. personally i agree, i wouldn’t go storing my old photos as avif anytime soon.
Can I ask for your thoughts on .webp vs .avif for static web development? I’m working on moving towards .webp just because AstroJS has a Image library that converts images to .webp at build time and sort of figured, sure why not? But I only recently really learned about .avif.
Someone tell me why.
image compression standards are my jam so i watched the video.
jpeg is a decades-old lossy image compression format that’s historically been pretty good for its purpose of storing adequate quality images while conserving space and especially bandwidth. but there are modern alternatives that are better, including jpeg xl that the author highlights as especially useful because it’s backwards compatible with old jpeg files. and one of the video author’s main arguments is that jpeg xl is robust and future-proof, it will continue to be a file format that’s shareable and readable for many years or even decades to come.
but the modern internet ecosystem (meaning google chromium browser which dropped support for jpeg xl last year) seems to be gravitating towards avif, the av1 image format. it’s a file format for still images based on the av1 video compression algorithm that’s focused more towards maximizing compression, and isn’t backwards compatible with jpeg. another big issue with avif is that it caps out at 12 bits of color resolution compared to 32 bits of color resolution in jpeg xl, which can lead to some unsightly compression artifacts.
jpeg xl is also a much simpler format to encode and decode so it uses less hardware capacity and therefore energy use when creating and displaying many images. and jpeg xl supports progressive decoding, loading up and displaying an initial low quality version of the image and filling it in with finer details, rather than having to load and decode the entire image at once. he also complains about avif headers causing problems, things that will make it more difficult to even read the files in the future, potentially.
that’s about what i got out of the video. personally i agree, i wouldn’t go storing my old photos as avif anytime soon.
Damn I love a good Hexbear infodump.
Can I ask for your thoughts on .webp vs .avif for static web development? I’m working on moving towards .webp just because AstroJS has a Image library that converts images to .webp at build time and sort of figured, sure why not? But I only recently really learned about .avif.
sure, i don’t do web development so
Fair enough.
The justification for webp for Android development is that it reduced apk size
It checks all of the boxes for royalty-free, feature-rich and efficient storage
Okay, I saw this really great video about it: https://youtu.be/FlWjf8asI4Y
Hope this helps!
I found a YouTube link in your comment. Here are links to the same video on alternative frontends that protect your privacy:
aint nothing but a heartache