Why Tiny JPEGs Look Different in Chrome

Re:Why Tiny JPEGs Look Different in Chrome by iknowstuff on Wednesday August 12, 2026 @02:23PM (#49276615)

Thoroughly enjoyed reading this!

In other news, AVIF is at 95%: https://caniuse.com/avif so it's probably time to give it the first preference over jpg.

[ Parent | on HN ]

Re:Why Tiny JPEGs Look Different in Chrome by adzm on Wednesday August 12, 2026 @02:50PM (#49276915)

Interesting, I don't seem to see options for this in avifenc for example, I suppose this needs fancier interaction with the library directly

[ Parent | on HN ]

Re:Why Tiny JPEGs Look Different in Chrome by gutechh on Wednesday August 12, 2026 @02:51PM (#49276932)

Thank you! I wonder if we'll ever see avif/webp takeover or if it's gonna be like ipv4/ipv6.

[ Parent | on HN ]

Re:Why Tiny JPEGs Look Different in Chrome by theandrewbailey on Wednesday August 12, 2026 @05:49PM (#49279053)

I've primarily been using AVIF with JPG as fallback on my blog for a few years. The efficiency gain is wild. I wonder if AV2 will be integrated into AVIF at some point (AVIF is based on AV1).

[ Parent | on HN ]

Re:Why Tiny JPEGs Look Different in Chrome by tosti on Thursday August 13, 2026 @05:21AM (#49283482)

The matrix of sources for a large picture can be mind boggling huge.

We have jpeg, webp, avif and jpegxl. Portrait orientation and landscape. 3 or 4 different pixel ratios and of course, different screen resolutions. Dark mode support doubles all of that work. Hardly anyone is going to do all of this correctly, automated or not.

[ Parent | on HN ]