Hi @sarahdev,
Thank you for your message.
Our plugin is not used to optimize the amount of disk space used. The plugin can be used to optimize the weight of images loaded on the website, which makes the website load faster.
Maybe I’ll tell you how our plugin works? When a browser tries to download an image file, the plugin checks if it supports the AVIF format (if enabled in the plugin settings). If so, the browser will receive an equivalent of the original image in the AVIF format. If it does not support AVIF, but supports the WebP format, the browser will receive the equivalent of the original image in WebP format. In case the browser does not support either WebP or AVIF, the original image is loaded. This means full support for all browsers.
Our plugin does not modify or delete original files. Files converted to WebP and AVIF formats are saved in a separate directory: /wp-content/uploads-webpc/.
Best,
Mateusz
Hi Mateusz,
I understand your plugin isn’t meant for optimization in that way. However, my concern is with the images in the uploads-webpc. They have double extensions ‘.jpg.webp’ I am concerned that having a double extension is causing some errors. Can you confirm if this is expected behavior or not? Thank you.
@sarahdev, what double expansion issues do you mean?
The plugin does not change URLs to images, so when looking at the source of the website, you will see the URLs for the default images all the time. The plugin creates redirections to output files in WebP and AVIF format, changing the MIME type of these images, but without changing the URL.
Below I have attached the tutorial describing how to test the plugin:
https://mattplugins.com/docs/how-to-test-converter-for-media-plugin
Not Expansion, extensions. And not the URLS’ of the images the actual saved image files in the upload folder. I’ve taken a screenshot and linked it here: https://imgur.com/a/2UTmtPP
This may be an intentional aspect of the plugin, I just want to confirm since I am having issues with file size and readability I am worried it might be causing that issue. Again, just want to confirm if that is a feature and not a bug.
@sarahdev, this is how the plugin works and it is intentional. It does not cause any problems and everything works fine.
