Convert existing WordPress images to WebP and AVIF retroactively
A newly installed plugin initially converts only new uploads. The biggest effect is in the existing stock – that needs a bulk run across the whole media library.
A newly installed image optimization plugin initially converts only what is uploaded from then on. But the biggest effect is in the existing stock: the hundreds or thousands of images already in the media library. For that you need a bulk run that goes through the existing files once and creates a WebP and AVIF variant for each.
Why the existing stock is often the bigger lever
Anyone who has blogged for years or runs an established shop uploaded most images long ago – often as large JPEGs, sometimes without suitable intermediate sizes. These are exactly the images that still appear in old posts, in the category overview, in the archive. Without retroactive conversion, half the site stays slow.
What matters in a bulk run
- Convert all registered image sizes, not just the original – the intermediate sizes are what gets served.
- Control server load: run the conversion in blocks, ideally at a low-traffic time.
- Keep the originals: create WebP/AVIF as additional variants, do not overwrite the original – in case you want to reconvert later.
- Automatic fallback: older clients still get the original or WebP.
- Large libraries: a command-line route (WP-CLI) is far more robust than the browser for tens of thousands of images.
Where IMG Performer fits in
The Pro version of IMG Performer includes exactly this retroactive scan: it goes through the existing media stock, creates WebP and AVIF for all sizes, and can script this via WP-CLI even for very large libraries. Processing runs locally, with no per-unit cost. The free version converts new uploads; the bulk run for the existing stock is part of Pro. Background: Image optimization without the cloud.
Disclaimer
As of September 2026. Details on IMG Performer: img-performer.enfants.de.
Frequently asked questions
Are my posts updated automatically, or do I have to re-insert the images?
The posts stay unchanged. On delivery, the WebP or AVIF variant is served instead of the original – without you touching the post.
How long does a bulk run take?
That depends on the number of images and the server performance. As an order of magnitude: a few minutes for a small blog, several hours for a large shop – which is why it runs in blocks.
Does this take up twice the storage?
WebP and AVIF are added as extra files, but they are considerably smaller than the original. The growth is moderate; the load-time gain clearly outweighs it.