Until now, next-gen WebP images could only be served by activating Smush Pro’s CDN. But by popular demand, Smush Pro now also supports local WebP image conversion.
Our CDN is awesome, it really is. However, we’re all for giving people options.
This is exactly why we’ve now made it possible to convert your images to WebP format without needing to use our CDN.
It was also one of Smush Pro’s (and WPMU DEV in general!) most anticipated and requested features of the year.
You told us that…
- If you were happy with your current CDN provider, you’d prefer not to have to switch to get WebP support.
- You were also conscious that using Smush Pro’s CDN to serve images uses precious bandwidth – which might not be ideal for larger sites.
So, like any good company who actually listens to their audience, we’ve obliged, and made our award-winning image optimization plugin – even better!
Read on to find out the in’s and out’s of Smush Pro’s game-changing new feature.
Here’s a quick overview if you want to skip to a particular section:
1. Why Convert to WebP?
2. Activating Local WebP on WPMU DEV Hosted Sites
3. Enabling Local WebP Conversion on Third-Party Sites
4. Apache Server Configuration
5. NGINX Server Configuration
6. How to Check Your Image Format.
Why Convert to WebP?
The benefits of WebP images speak for themselves.
WebP image files are much smaller and load faster than JPEGs and PNGs – all while offering no perceptible difference in quality.
The proof is in the pudding – when YouTube switched their thumbnails to WebP, they saw a 10% reduction in load time!
Once you activate the Local WebP feature, Smush Pro will convert your images into the next-gen file type during regular Smushing.
And while not all browsers support WebP (we’re looking at you, Internet Explorer!), you can rest safe in the knowledge that Smush will serve up the JPEG and PNG equivalent to non-supported browsers.
Activating Local WebP on WPMU DEV Hosted Sites
First things first – the latest version of Smush Pro needs to be installed on your site.
You can then head into the WebP settings.
If you host with us, you’ll be lucky enough to be greeted by this message on the next page: