Title: webp support with EWWW IO Last modified: August 31, 2016 --- # webp support with EWWW IO * Resolved [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/) * Hi, I’m the author of the EWWW Image Optimizer plugin, and I was reading an article that mentioned your plugin. I thought I’d check it out and noticed you had webp support. With EWWW I.O., the only options have been to use .htaccess rules (if the site is NOT employing a CDN), or use page parsing+js because of caching plugins. * I really appreciate that you added this capability, and I wondered if you would be able to add support in your webp routine for the naming scheme used by EWWW Image Optimizer? * Instead of replacing the file extension, EWWW IO appends .webp to the existing filename. We started with the other method, but it had some issues with filename collisions (if you have a .png and a .jpg with the same basename), so we switched to the appending method a while back. * [https://wordpress.org/plugins/cache-enabler/](https://wordpress.org/plugins/cache-enabler/) Viewing 15 replies - 1 through 15 (of 15 total) * Plugin Author [KeyCDN](https://wordpress.org/support/users/keycdn/) * (@keycdn) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7334908) * Thanks for reaching out! We haven’t seen any collisions with the filename so far. Do you have an example for this? * I also think it is cleaner to have only the actual extension there instead of having still the previous file format. * What about a switch on your end to allow replacing of the image extension to webp? That would immediately enable the benefits of the Cache Enabler for the webp files. * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7334934) * I’ve never actually seen a collision in real life, but with several hundred thousand users, I do everything I can to avoid them. Here is the thread where we originally discussed changing the renaming scheme in EWWW IO: [https://wordpress.org/support/topic/webp-filename-not-unique?replies=8#post-5977643](https://wordpress.org/support/topic/webp-filename-not-unique?replies=8#post-5977643) * Plugin Author [KeyCDN](https://wordpress.org/support/users/keycdn/) * (@keycdn) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335168) * I recommend to change the extension to WebP. I don’t see any problem with that. * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335169) * Except there IS a potential for file-name conflicts, not a chance EWWW is changing back. * Plugin Author [KeyCDN](https://wordpress.org/support/users/keycdn/) * (@keycdn) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335171) * We added the support to for appended .webp. We haven’t done a version bump yet, so just test this with the current version 1.0.9. Can you add a link to the Cache Enabler in your plugin settings and on the plugin website? * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335172) * Very cool, I’ll test it out, and will definitely add a link to Cache Enabler for my next release. * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335173) * Hmm, I tried it on two different sites and it doesn’t seem to be working. I converted all my images on the home page of [https://ewww.io](https://ewww.io), and the cache enabler says ‘webp’ at the bottom, but it doesn’t appear to be loading webp. * Update: after double-checking, it’s only working for .png images. The other images on that site use .jpeg extensions, but my test site images are just plain .jpg. * Plugin Author [KeyCDN](https://wordpress.org/support/users/keycdn/) * (@keycdn) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335174) * Indeed, there was an issue with .jpeg, which is fixed now. Just delete the plugin and install it again. * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335175) * That did the trick, fully webp now! Would be nice to have a link to EWWW IO on the Cache Enabler settings too 🙂 * Plugin Author [KeyCDN](https://wordpress.org/support/users/keycdn/) * (@keycdn) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335176) * Awesome! We will certainly add you to the list of compatible plugins. * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335177) * I’m also going to try to auto-detect when Cache Enabler’s webp option is on, and then gray-out/disable the EWWW webp rewriter. * Plugin Author [KeyCDN](https://wordpress.org/support/users/keycdn/) * (@keycdn) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335186) * The gray-out works perfect! How about suggesting the Cache Enabler there as well? I guess not many people will know about the new option to integrate WebP images otherwise. * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335187) * Yeah, I was trying to think of a way to tie that in, to raise awareness of that method. * Thread Starter [nosilver4u](https://wordpress.org/support/users/nosilver4u/) * (@nosilver4u) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335188) * Ok, I’ve got a little blurb alongside the ‘Alternative WebP Rewriting’ option, and I opted to completely hide that option if we detect that Cache Enabler is active, and the WebP cache option is enabled. I thought that would probably be better, so people don’t go crazy trying to figure out why they can’t enable an option that is grayed-out. Although one would hope that folks would remember they already have Cache Enabler’s WebP option enabled, I’ve been in I.T. too long to assume any such thing 🙂 * Also, I know KeyCDN runs Optimus, but thought I’d ask anyway if you’d be willing to add a link to EWWW IO on your settings, something like “Convert your images to WebP with Optimus or EWWW IO.” * Plugin Author [KeyCDN](https://wordpress.org/support/users/keycdn/) * (@keycdn) * [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335189) * Sounds good! We will link to ewww on the plugin page once we completed all the compatibility checks with the different plugins we are running right now. Viewing 15 replies - 1 through 15 (of 15 total) The topic ‘webp support with EWWW IO’ is closed to new replies. * ![](https://ps.w.org/cache-enabler/assets/icon.svg?rev=2442383) * [Cache Enabler](https://wordpress.org/plugins/cache-enabler/) * [Support Threads](https://wordpress.org/support/plugin/cache-enabler/) * [Active Topics](https://wordpress.org/support/plugin/cache-enabler/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/cache-enabler/unresolved/) * [Reviews](https://wordpress.org/support/plugin/cache-enabler/reviews/) ## Tags * [webp](https://wordpress.org/support/topic-tag/webp/) * 15 replies * 2 participants * Last reply from: [KeyCDN](https://wordpress.org/support/users/keycdn/) * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/webp-support-with-ewww-io/#post-7335189) * Status: resolved