Working with WebP images

Flying Pigs makes WebP copies in your browser, for the original and for every size you choose in the Sizes panel. It is on by default at quality 75, effort 3 (set in the Media panel), and a WebP that comes out larger than its source is thrown away. The Sizes panel chooses which sizes get one.

Two ways to store WebP

• WebP beside the JPEG (Free and Pro): each image keeps its JPEG or PNG, with a WebP copy next to it named photo.jpg.webp. Something has to serve the WebP copies to browsers, see below.
• WebP only (Pro, on by default): the image and every size are stored as WebP, with no JPEG or PNG kept. Browsers get the WebP directly, with nothing extra to set up.

Getting the WebP copies to visitors

The Delivery panel handles this. If a plugin that serves WebP is already active, the panel names it and leaves it in charge. If nothing is serving them, Set up delivery for me tests your server and turns on a rewrite in the site's .htaccess (Apache and LiteSpeed), or wraps images in a <picture> tag where the host will not honor the rewrite. You can undo it from the same panel.

Plugins that serve Flying Pigs' WebP copies

These serve the standard photo.jpg.webp files Flying Pigs writes:

✅ LiteSpeed Cache (see its image optimization settings)
✅ Imagify
✅ EWWW Image Optimizer
✅ Images to WebP
✅ ShortPixel Image Optimizer
✅ WebP Express

These keep their own copies in their own places and do not serve Flying Pigs' files:

❌ Converter for Media
❌ Optimole
❌ CompressX

There may be other plugins that work.