Regenerate Thumbnails (by Alex Mills) does not maintain its own tables. It works against wp_posts attachments and the _wp_attachment_metadata postmeta key, where WordPress stores the per-size file map (thumbnail, medium, large, plus any theme-registered sizes). The default plugin admin offers a list with progress and a global regenerate button.

SleekView reads the attachment rows and unpacks _wp_attachment_metadata so each registered size becomes a column. Image dimensions, file size, MIME type, missing sizes, and parent post turn into first-class fields ready for sort and filter. Saved views like "images missing the large size", "images uploaded before the new theme size was added", or "PDF cover thumbnails missing" replace a global rebuild with a precise, scoped pass.

Regeneration actions route through Regenerate Thumbnails' own background job so its hook integrations (WP-CLI, Action Scheduler) still apply. The filtered set becomes the queue for the job, which avoids reprocessing the whole library when only a subset needs new sizes.

Regenerate Thumbnails scales technically because it leans on WordPress core APIs and a background job, which keeps regeneration safe and resumable. The default admin does not scale operationally because it cannot answer "which attachments are missing the new large size" or "which PDF covers never got a thumbnail" without code. A global regenerate is wasteful when only a subset of files actually changed, and editorial teams cannot filter the queue by parent post or dimensions.

SleekView changes that by reading _wp_attachment_metadata and exposing each registered size as a column, with multi-condition filtering across dimensions, file size, parent post, and missing-size status. The filtered set becomes the queue for the plugin's background job so the rebuild scopes precisely to what needs it. Inline edits for alt text and caption use standard WordPress so existing hooks fire normally.

The result is a single audit-and-queue screen for the regeneration work that previously required either a global rebuild or custom WP-CLI.