check if images were modified

EWWW IO doesn’t add a “fingerprint” to your images, that would kind of defeat the purpose of lossless compression, which is to get rid of all that excess baggage ??

But, if they also restored the database, you should not find an ewwwio_images table in your database. If you do, then they may not have restored the backup. But of course, they may have only done the files, so it depends on what exactly you asked them to do.
That’s the only way I can think of to check on things.

That said, if you don’t have some way to check if the images were modified, then why are you upset with them about optimizing your images? By default, it’s a completely lossless process, and does nothing but speed up your site.
In other words, why didn’t you want them to have EWWW IO active on your site? Did it cause some issue for you, or was it simply that they didn’t “ask permission”?

At any rate, if you have further questions about EWWW IO, just let us know! You can also email us via https://ewww.io/contact-us/ for a faster response in the future.

Hi,
your plugin changes the file-size of the original files correct?
So if your plugin has already compressed my images I should be able to download an image from my website and expect its size to be smaller than what it was before.

So for example. I uploaded an image on my blog which was 250kb. If your plugin had already done its job, and I now go to download the image from my website, it should be smaller than 250kb, is this correct?

Also its format should have been changed to webp?

Yes, file sizes should be smaller, though not always, because it IS possible for someone to have “properly compressed” their image prior to upload.

If WebP conversion is enabled, the plugin adds a new image with a .webp extension, and those should be very obvious in your file manager. But WebP conversion isn’t enabled by default. Only lossless (Pixel Perfect) compression is done by default, no scaling, no WebP. No potentially “dangerous” options are enabled by default.