Hacker News Reader

Since all modern browsers support AVIF, I'd skip WEBP and just use AVIF (possibly with a fallback for JPG/PNG).

Everytime I compared AVIF to WEBP there was basically zero size or visual difference and as far as I know AVIF is slower to encode and decode. And I'm not sure yet whether .avif files can be opened natively on Windows, Linux and MacOS on the default image viewers. I think I installed some kind of plugin via the Windows Store at some point to make that work, hard to tell now.

Odd, what are you using to create your avif's? I've done a bunch of work with them and the AVIF's were almost always significantly smaller than webp at equal or better quality.

Encoding is a pain, to be sure; I ended up creating a workflow where my source would save things as PNG files (giant, but lossless) then running a avifenc (https://github.com/AOMediaCodec/libavif) to produce the avif, and trashing the PNG.

Decoding though, all browsers have support, it's great.

> and trashing the PNG.

I don't delete my original source images, in case if I want to change the encoder parameters later, or if a newer encoder version improves quality.

Reply on news.ycombinator.com