KakapoWP KakapoWP
Log in Try for free
Kakapo Performance

Batch run for the media library

Yesterday's library gets what's switched on today.

WebP, AVIF and stripping the metadata take effect at the moment WordPress generates the image sizes — that is, from the next upload on. Anything already in the media library stays untouched. The batch run walks through that existing stock and applies exactly the settings switched on above: in sections with a fixed time budget, with a progress bar, pausable at any time. It does not process a single image itself — that is done by the same two modules as on upload, here they are merely driven and measured afterwards.

Batch run for the media library

Reprocess existing JPEG and PNG files · progress, pause, resume

RunningPause

What the batch run offers

Applies exactly what is switched on
Runs over the JPEG and PNG attachments in the media library
8 seconds time budget per run
Progress saved after every attachment
Pause, resume, reset
If nothing is switched on, the start button tells you what's missing

Here's how it works

1

Turn on WebP, AVIF or “Remove metadata”

2

Start the batch run and watch the bar

3

Read the closing line with the measured sizes

FAQ about the batch run

Does the browser tab have to stay open?
Yes. The run is driven from the admin area, not via WP-Cron — this plugin can switch off the WordPress pseudo cron itself, and a run built on it would then stand still. If you close the tab, the run pauses; nothing is lost. Open the page again and it carries on with the same attachment.
Does the run touch my original files?
The uploaded original file stays untouched. Additional WebP and AVIF files appear next to it, and metadata markers are removed from the sizes WordPress generated. Any result that is not smaller than its source is discarded and counted as skipped in the report.
Does the uploads folder end up smaller?
Only through removing the metadata — the report shows those bytes separately. WebP and AVIF files are added and take up extra space; the saving happens in the transfer to the visitor. Since a browser only ever fetches one of the two formats, the report lists WebP and AVIF in separate rows — you must not add them up.

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