AJAX Thumbnail Rebuild

Description

AJAX Thumbnail Rebuild recreates the resized copies WordPress makes of every image in your media library. It does them one image at a time, so a library of any size gets through without running into the script timeout that stops the plugins which rebuild everything in a single request.

You need this whenever the sizes change: a new theme with different dimensions, a plugin that registers a size of its own, or a size you have edited yourself. WordPress applies those to images uploaded afterwards and leaves everything already in the library at its old dimensions. Rebuilding fills the gap.

On its screen under Tools you can:

• Pick which of the registered sizes to rebuild, so a single changed size does not mean redoing all of them.
• Rebuild only the images used as a featured image – which covers WooCommerce product images and product galleries – or only the file names matching a pattern, e.g. banner-*.jpg.
• Watch it run: a progress bar, the image being worked on, a Stop button, and a list of anything it had to skip.
• See every image size registered on the site with its dimensions and crop setting.
• Clean up the resized files left behind by sizes that no longer exist.

You can also work on one image at a time without leaving the media library: a row action rebuilds or optimises a single image, a bulk action hands a selection to the plugin’s screen, and the attachment details panel – wherever it opens – rebuilds, optimises, or replaces the file. A replaced image keeps its id, title and address, so every post and product already pointing at it shows the new picture.

Beyond rebuilding, each of these is off until you turn it on:

• Uploads. How hard WordPress compresses the copies it writes, and how large an image may stay before it is scaled down.
• Optimising. Makes files smaller without resizing them, using the optimisers installed on the server – jpegoptim, optipng, gifsicle, and pngquant where lossy PNG is allowed. Where a host has none, TinyPNG or ShortPixel can do the same job over their API. A file is replaced only when the new one is genuinely smaller.
• AVIF and WebP copies. Written next to every image WordPress generates and served through a picture element, AVIF first, WebP after it, the original as the fallback – which works behind a page cache.
• Background processing. Optimising and the copies are the slow half of an upload. Queue them instead, and the upload finishes as soon as the sizes are written – on Action Scheduler where the site has it, on WP-Cron where it does not.
• Image proxy. Front end image URLs can be served through wsrv.nl, which resizes and re-encodes on the fly and serves the result from a CDN. Your own files are never touched.
• Sizes on demand. An upload keeps only its own file, and each size is cut the first time something asks for it.

This plugin requires JavaScript to be enabled.

Contributions are welcome at Github

Technical details