3 ms·
Teams & developers will likely only chose a single format if they can, the one that most browsers support, because doing some content negotiation is more code,
by throw_m239339 1y ago
Teams & developers will likely only chose a single format if they can, the one that most browsers support, because doing some content negotiation is more code, more work. It doesn't take away anything from the parent point though, if JPEG-XL is more performant it could reduce bandwidth requirements.
- alwillis 1y ago> because doing some content negotiation is more code, more work It's actually not more work. The user's browser automatically handles the content negotiation and only downloads the image format it understands: <picture> <source srcset="photo.jxl" type="image/jxl"> <source srcset="photo.webp" type="image/webp"> <img src="photo.jpg" alt="Product photo" loading="lazy"> </picture> macOS, iPadOS and iOS get the JPEG-XL image, device that can handle WebP get that and everything else gets JPEG. There are several image delivery services that will provide the best image format depending on the device that's connecting.