Cloudinary moves your media library to their servers, so any WebP stuff would be done on their end, with no interaction from EWWW IO. The only reason to use EWWW IO with Cloudinary is for the initial compression, after which the image is uploaded back to Cloudinary.
Just out of curiosity, what are you trying to accomplish with Cloudinary? In other words, why are you using Cloudinary in the first place?
Sorry for the delay and thanks for the reply, I wanted to deliver images in webp and use some cdn
So yes, you should be able to use EWWW IO with Cloudinary for that purpose. But again, you don’t need to do anything with WebP on EWWW IO, that should be handled by Cloudinary. That said, I’m not 100% sure if that’s automatic on their end, or something you have to specifically enable.
Hopefully they’ve improved things, but last I checked, using the Cloudinary plugin is terrible for responsive images (it removes support for srcset entirely). So you get some benefits (WebP and some compression), but lose the built-in WordPress ability to serve scaled images for various device/screen sizes.
Our Easy IO CDN gives you all those things, and even improves responsive images: https://ewww.io/easy/
