Translations

Locally serve WebP versions of your images to supported browsers, and gracefully fall back on JPEGs and PNGs for browsers that don't support WebP.

Locally serve WebP versions of your images to supported browsers, and gracefully fall back on JPEGs and PNGs for browsers that don't support WebP.

Join WPMU DEV to use this feature

Join WPMU DEV to use this feature

Re-check status

Re-check status

Made changes?

Made changes?

Fix the "Serve images in next-gen format" Google PageSpeed recommendation by setting up this feature. Serve WebP versions of your images to supported browsers, and gracefully fall back on JPEGs and PNGs for browsers that don't support WebP.

Fix the "Serve images in next-gen format" Google PageSpeed recommendation by setting up this feature. Serve WebP versions of your images to supported browsers, and gracefully fall back on JPEGs and PNGs for browsers that don't support WebP.

Smush WebP

Smush WebP

Deactivation won’t delete existing WebP images.

Deactivation won’t delete existing WebP images.

This feature won’t delete the WebP files converted via CDN, only the files generated via the local WebP feature.

This feature won’t delete the WebP files converted via CDN, only the files generated via the local WebP feature.

Delete WebP Files

Delete WebP Files

If your server storage space is full, use this feature to revert the WebP conversions by deleting all generated files. The files will fall back to normal PNGs or JPEGs once you delete them.

If your server storage space is full, use this feature to revert the WebP conversions by deleting all generated files. The files will fall back to normal PNGs or JPEGs once you delete them.

Revert WebP Conversion

Revert WebP Conversion

Reload NGINX.

Reload NGINX.

Copy the generated code found below and paste it inside your http or server blocks.

Copy the generated code found below and paste it inside your http or server blocks.

Insert the following in the server context of your configuration file (usually found in /etc/nginx/sites-available). “The server context” refers to the part of the configuration that starts with “server {” and ends with the matching “}”.

Insert the following in the server context of your configuration file (usually found in /etc/nginx/sites-available). “The server context” refers to the part of the configuration that starts with “server {” and ends with the matching “}”.

If you don't know where those files are, or you aren't able to reload Apache, you would need to consult with your hosting provider or a system administrator who has access to change the configuration of your server.

If you don't know where those files are, or you aren't able to reload Apache, you would need to consult with your hosting provider or a system administrator who has access to change the configuration of your server.