Hi @eddyg93 ,
The plugin allows you to convert your images to WebP, even new ones as they are added, however it also retains the original JPG/PNG version of the image for fallback purposes. There are two steps to WebP, generating them and delivering them. In order to generate WebP images, you check the box labeled “WebP Conversion” on the Essentials tab, save, and then run a bulk optimize. You can find a video here where you can even just run a “WebP Only” to just generate the WebP version: https://www.youtube.com/watch?v=cyntnjs7qkE
For the second step, delivering those images, I would recommend the documentation as it can be a bit to figure out. You either use the .htaccess rules or you can use JS WebP. https://docs.ewww.io/article/119-webp-delivery
Ah so there’s no actual way to convert all my images to webp and just have those, because if I converted the images to webp but still having the jpgs would make my site too huge in space factor.
Anyway I had decided to switch to webp also because now every browser supports it, the only one that won’t go is internet explorer but nobody uses it.
https://caniuse.com/webp
Right, there isn’t a built-in way to just have the WebP. You could use our CDN and it would take care of the site for you without touching your local images. Then you could compress your local images and keep that size down quite a bit, but that’s with a premium subscription.
We just checked our CDN logs and we still see about 45% still requesting non-webp versions of the images. That’s why we still use the original fallbacks and provide them. For example, I don’t think places like facebook natively support webp still, so though the browsers can support it, there are other factors that come into play.
I haven’t heard anything back about this in a while so I’m going to resolve this thread. If you have further questions, please feel free to open a new one!
