Kakapo Performance

WebP and AVIF

Extra files alongside the original, not a replacement.

On upload, the kakapo places a WebP and an AVIF file next to every image size. The original and the JPEG or PNG sizes stay unchanged. In the frontend a <picture> element brings both together, and the browser takes the format it understands. A derivative survives only if, measured afterwards, it is smaller than its source.

Try it free for 24 hours All Performance features

WebP and AVIF

An extra file per image size · delivery via <picture>

ActiveSettings

What WebP and AVIF offer

WebP and AVIF for every image size

The original and the JPEG/PNG stay as they are

Delivered via <picture>, AVIF first

Anything not smaller than the original is discarded

Quality 30–100, upper limit in megapixels

Shows which formats the server supports

Here's how it works

Turn on WebP and AVIF

Upload an image, the files appear

The browser picks its format

FAQ about WebP and AVIF

Does this also apply to images already in the media library?

Those are handled by the batch run over your existing library. This function here works on upload and when image sizes are regenerated.

Can I enable AVIF on any server?

Only where PHP allows it. Without it the toggle is visible but not operable, and the reason stands next to it. The kakapo re-checks the capabilities against the running PHP and rejects switching it on even if someone tries it past the display. AVIF needs PHP 8.1 or newer with libavif, WebP a GD library with libwebp.

Do I need more storage space for this?

Yes. Files are added, nothing is replaced. If you delete an attachment, its companion files disappear with it — as long as the plugin is active.

More performance features

Ready?

Try Performance free for 24 hours.

No credit card, no risk. Up and running in 2 minutes.

Try it for free now