aiwatech

<p>Every time you upload an image, WordPress doesn’t just store your file — it generates a separate cropped copy for every registered image size. A fresh install already creates three (thumbnail, medium, and large) on top of the original, so a single upload becomes four files on your server.</p>
<p>Themes and plugins add many more. A typical site might register hero, slider, product thumbnail, team member, and testimonial sizes — and WooCommerce adds several of its own. With six registered sizes, one upload turns into seven files, even when the page only ever displays one of them. The rest sit on disk doing nothing but consuming space.</p>
<p>Multiply that across hundreds of posts, pages, and products and the waste adds up fast: bloated storage, slower backups, and longer upload processing. It’s especially painful on WooCommerce sites, where uploading a single banner or hero image also generates the full set of product thumbnail sizes you’ll never use for that image.</p>
<p><strong>WP Image Sizes fixes this by letting you decide which sizes WordPress is allowed to create.</strong></p>
<ul>
<li><strong>Per post type control</strong> — Assign the exact image sizes that matter to each post type from a simple settings page. A slider post type might only need one large size; testimonials might only need a thumbnail.</li>
<li><strong>Choose sizes at upload time</strong> — When you add media, the uploader shows the available sizes so you can pick what gets generated for that specific upload.</li>
<li><strong>Disable thumbnails entirely</strong> — Skip generating any additional sizes for a post type or a single upload when you only need the original.</li>
<li><strong>No lock-in</strong> — WP Image Sizes never caches or alters your files. Any images already generated stay intact, even if you deactivate or remove the plugin.</li>
</ul>
<p>The result is a leaner media library, less wasted disk space, and a faster, lighter WordPress site.</p>
<h3>PRO</h3>
<p>The free plugin controls which sizes get generated on new uploads. <strong>WP Image Sizes Pro</strong> extends this to your <em>existing</em> media and adds automation:</p>
<ul>
<li><strong>Bulk Create Image Sizes</strong> — Generate selected image sizes for all existing images of a chosen post type. Perfect after registering a new size or switching themes.</li>
<li><strong>Bulk Delete Image Sizes</strong> — Remove unwanted image size files from existing media to reclaim server space in one click.</li>
<li><strong>Create Images on Runtime</strong> — Automatically generate a missing image size the moment it is first requested on the front end, instead of pre-creating every size.</li>
</ul>
<p><a href="https://aiwatech.com/product/wp-image-sizes-pro/" rel="nofollow ugc">Get WP Image Sizes Pro</a></p>


WP Image Sizes

Take control of the image sizes WordPress generates. Pick only the sizes you actually use, per post type, and reclaim wasted server space.

YoOhw Studio

<p>Thumbnail Manager helps you control WordPress thumbnail generation, regenerate image sizes, and clean unused thumbnail files from the Media Library.</p>
<p>Use it after changing themes, installing WooCommerce, disabling custom image sizes, or cleaning up years of generated media files. The plugin focuses on predictable thumbnail management: choose which image sizes should stay enabled, rebuild the thumbnails you need, preview cleanup results, then delete only reviewed generated files.</p>
<p>Cleanup is metadata-aware and safety-focused. Thumbnail Manager validates uploads paths, protects original full-size images, runs prune/delete actions in batches, and updates attachment metadata after deleted thumbnail sizes are removed.</p>
<h4>Key Features</h4>
<ul>
<li>Regenerate WordPress thumbnails for existing image attachments</li>
<li>Generate only missing thumbnails or force-regenerate all selected images</li>
<li>Disable unwanted registered image sizes for future uploads</li>
<li>Prune unused thumbnails while keeping selected sizes</li>
<li>Run Dry-run previews before deleting generated thumbnail files</li>
<li>Detect legacy thumbnail sizes stored in attachment metadata</li>
<li>Report disk-only orphan matches without deleting unmapped files by default</li>
<li>Scan recommendations based on protected sizes, WooCommerce-related sizes, generated metadata, and common content references</li>
<li>Process large Media Libraries with cursor-based AJAX queues and folder scoping</li>
<li>Manage everything from Tools > Thumbnail Manager</li>
</ul>
<h4>Common Use Cases</h4>
<ul>
<li>Clean WordPress thumbnail bloat after theme or page builder changes</li>
<li>Regenerate thumbnails after changing Media Settings or custom image sizes</li>
<li>Reduce WooCommerce image storage by reviewing generated product thumbnails</li>
<li>Disable image sizes that should no longer be created for new uploads</li>
<li>Rebuild missing thumbnails after migration, restore, or failed image processing</li>
<li>Audit legacy thumbnail sizes left behind by old themes and plugins</li>
</ul>
<h4>Safety First</h4>
<p>Thumbnail Manager is designed for controlled cleanup, not blind filesystem deletion.</p>
<ul>
<li>Original full-size images are not deleted</li>
<li>Delete mode requires a fresh delete token and a completed scan</li>
<li>Dry-run mode never deletes files</li>
<li>Cleanup targets files from attachment metadata</li>
<li>Disk-only orphan matches are reported, not deleted by default</li>
<li>Paths are validated under the WordPress uploads directory before deletion</li>
<li>Attachment metadata is updated after generated thumbnail sizes are removed</li>
</ul>
<h4>What It Does Not Do</h4>
<ul>
<li>It does not compress or optimize image quality</li>
<li>It does not replace image optimization or CDN plugins</li>
<li>It does not automatically delete media without confirmation</li>
<li>It does not delete original uploaded images</li>
<li>It does not unregister image sizes from themes or plugins</li>
</ul>
<h3>Usage</h3>
<h4>Recommended Workflow</h4>
<ol>
<li>Open Tools > Thumbnail Manager.</li>
<li>Scan Recommendations to review likely keep/remove sizes.</li>
<li>Apply recommended sizes if they match your site.</li>
<li>Open Thumbnail Sizes and save the sizes you want generated for future uploads.</li>
<li>Run Regenerate to rebuild missing or selected thumbnails.</li>
<li>Open Prune Files and run Dry-run before any deletion.</li>
<li>Review matched files, then switch to Delete only when the preview is correct.</li>
</ol>
<h4>Regenerate Thumbnails</h4>
<p>Use Regenerate when you need to rebuild WordPress image sizes for existing attachments. You can process all media, the current year, a specific uploads folder, or specific attachment IDs.</p>
<h4>Prune Files</h4>
<p>Use Prune Files to clean generated thumbnails for sizes you no longer want to keep. Always run Dry-run first. If orphan discovery is enabled, metadata-backed legacy sizes can be included, while unmapped disk-only matches are reported for review.</p>
<h4>Thumbnail Sizes</h4>
<p>Use Thumbnail Sizes to control which registered image sizes WordPress should generate for future uploads. This setting does not remove existing files until you run Prune Files.</p>
<h3>Technical Notes</h3>
<ul>
<li>Uses <code>intermediate_image_sizes_advanced</code> to control future thumbnail generation</li>
<li>Uses cursor-based AJAX queues for regenerate and prune scans</li>
<li>Uses attachment metadata for prune candidates</li>
<li>Validates filesystem paths under the uploads directory before deletion</li>
<li>Updates attachment metadata after generated thumbnail files are removed</li>
<li>Requires the <code>manage_options</code> capability</li>
<li>Works per site on multisite installations</li>
</ul>
<h3>Privacy</h3>
<p>Thumbnail Manager does not collect, store, or transmit personal data. All thumbnail scans, regeneration actions, and cleanup actions run locally on your WordPress site.</p>


Thumbnail Manager

Regenerate WordPress thumbnails, disable image sizes, and safely clean unused media library thumbnails with dry-run previews.

WP Image Sizes vs Thumbnail Manager