WebP support detection issue

@dereklc

Who care’s about nginx? I am on LiteSpeed! The only thing that counts, is if browser supports . webp or avif, but you don’t need extra server configuration or any script coding to make .webp or .avif available. HTML has all you need.

The browser decides what image type he supports.

<picture>
	<source srcset="image.avif" type="image/avif">
	<source srcset="image.webp type="image/webp">
	<source srcset="image.png" type="image/png">
	<img alt="">
</picture>

FYI:
https://caniuse.com/?search=webp
https://caniuse.com/?search=avif

• This reply was modified 2 years, 2 months ago by serpentdriver.

@serpentdriver

Thanks once again for the information.

Two elements in my ecosystem (that I know about at the moment) care about nginx: the short pixel plugin I use to optimize images, and my hosting service who responded that they didn’t want to modify it when Google analytics code had to be put into my headers and Google decided it needed NGINX modified.

And since my forte is developing content and not spending all my time trying to figure out technical issues, then I’m just determining what works and doesn’t work based on my own experience and choosing the simplest solution that works for the most people. I was only expressing my concern that others may not be able to see images of a non-ubiquitous format. That’s all.

Thank you @serpentdriver — I think I have what I need to press on.