YoOhw Studio

<p>Thumbnail Manager helps you take back disk space from oversized Media Libraries.</p>
<p><strong>What it does</strong><br />
– <strong>Prune Files:</strong> Select the image sizes you want to <strong>KEEP</strong>. The plugin scans your <code>/uploads/</code> folder and targets all <em>non-selected</em> registered sizes for removal. It shows a <strong>dry-run</strong> summary first, then lets you delete in <strong>batches</strong> with a live <strong>progress bar</strong>.<br />
– <strong>Orphan discovery:</strong> Finds on-disk files that match <code>-WxH</code> patterns (including <code>.jpg.webp</code>, <code>.bak.jpg</code>, retina <code>@2x</code>, and duplicate <code>-1</code> suffixes) even if those sizes are no longer registered. Aggressively deletes <strong>any</strong> <code>-WxH</code> files that don’t exactly match the sizes you chose to keep (use with care).<br />
– <strong>Subfolder scope:</strong> Limit scans to a specific year/month inside <code>uploads/</code> for faster, safer runs on large libraries.<br />
– <strong>Thumbnail Sizes:</strong> Choose which sizes should be <strong>generated for future uploads</strong>. Disabled sizes won’t be created at upload time (and are hidden from size pickers).</p>
<p><strong>What it doesn’t do</strong><br />
– It <strong>does not regenerate</strong> thumbnails. Use a regeneration plugin if you need to rebuild sizes after changing settings.<br />
– It never deletes original full-size images.</p>
<p><strong>Who is it for?</strong><br />
Site owners, editors, and developers who’ve accumulated many custom image sizes (themes, page builders, sliders) and want to reduce storage bloat safely.</p>
<h3>Features</h3>
<ul>
<li>Two-tab UI: <strong>Prune Files</strong> & <strong>Thumbnail Sizes</strong></li>
<li><strong>Dry-run</strong> mode with sample matches before any deletion</li>
<li><strong>AJAX progress bar</strong> and <strong>batch deletes</strong> to avoid timeouts</li>
<li><strong>Orphan <code>-WxH</code> discovery</strong> report and delete found dimensions</li>
<li><strong>Limit to subfolder</strong> (All, year, or year/month)</li>
<li><strong>Disable sizes for future uploads</strong> (does not unregister core sizes; simply prevents generation)</li>
<li>Hides disabled sizes from Media size dropdowns (optional filter)</li>
<li>Works per-site on single and multisite (run on each site as needed)</li>
</ul>
<h3>Usage</h3>
<h3>Prune Files</h3>
<ol>
<li>In the table, <strong>check</strong> the sizes you want to <strong>KEEP</strong> (e.g., <code>thumbnail</code>, <code>medium</code>, <code>large</code>, and optionally <code>medium_large</code>).</li>
<li>(Optional) Choose a <strong>subfolder</strong> (e.g., <code>2024/11</code>) for a quicker, safer trial run.</li>
<li>Make <strong>Orphan discovery</strong> ON to see a report or do a deletion of found dimensions.</li>
<li>Click <strong>Run</strong> with <strong>Dry-run</strong> selected to preview matches.</li>
<li>Review results <span aria-hidden="true" class="wp-exclude-emoji">→</span> switch to <strong>Delete</strong> when you’re confident.</li>
</ol>
<p><strong>Tip:</strong> Enable <strong>Orphan discovery</strong> only when you want to remove any extra <code>-WxH</code> sizes not exactly matching your KEEP list (great for cleaning legacy sizes like <code>-1200x860</code> or <code>.bak.jpg</code> files).</p>
<h3>Thumbnail Sizes</h3>
<ol>
<li>Uncheck any sizes you no longer want generated for <strong>future</strong> uploads.</li>
<li>Click <strong>Save changes</strong>.<br />
(This prevents those sizes from being created going forward; existing files are unaffected until you prune them in Prune Files Tab.)</li>
</ol>
<h3>Technical Notes</h3>
<ul>
<li>Prevent generation via: <code>intermediate_image_sizes_advanced</code> (removes disabled sizes at upload time).  </li>
<li>Optionally hide in UI via: <code>image_size_names_choose</code> and reduce the base list via <code>intermediate_image_sizes</code>.  </li>
<li>Auto-scaled big image can be disabled with <code>big_image_size_threshold</code> if desired (not enabled by default).  </li>
<li>Requires capability <code>manage_options</code>.</li>
</ul>
<h3>Privacy</h3>
<p>This plugin does not collect personal data or send data to external services. It only reads and modifies files within your <code>/uploads/</code> directory based on your actions.</p>


Thumbnail Manager

Clean up unused thumbnails with progress; find orphan -WxH files; disable sizes for future uploads.

Marcin Pietrzak

<p>The <strong>Orphans</strong> plugin automatically improves the typography of your WordPress site by preventing single-letter or very short words—known as <em>orphans</em>—from appearing alone at the beginning of a line. By replacing the space after these words with a non-breaking space, the plugin ensures cleaner, more professional-looking text layouts, especially for languages like Polish where such typographic rules are important.</p>
<h4>What are Orphans?</h4>
<p>An <em>orphan</em> in typography is a short word (often a single character) left isolated at the beginning of a line, separated from the rest of the sentence. This is considered a composition error and can negatively affect readability and the visual appeal of your content.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Automatic Orphan Fixing:</strong> Scans your content and replaces spaces after short words (orphans) with non-breaking spaces, preventing them from being separated by line breaks.</li>
<li><strong>Customizable:</strong> Easily modify which words are treated as orphans using filters, or provide your own list of orphan terms.</li>
<li><strong>Non-Destructive:</strong> The plugin does not alter your original content in the database; changes are applied only when content is displayed.</li>
<li><strong>Builder and Plugin Integration:</strong> Seamless compatibility with popular page builders like Bricks, Divi, Muffin (beTheme), WPBakery, and Advanced Custom Fields.</li>
<li><strong>Flexible Usage:</strong> Apply orphan fixes to custom fields or any string using provided filters.</li>
</ul>
<h4>How It Works</h4>
<p>Once activated, Orphans automatically processes your posts, pages, and other content post types, fixing orphaned words on the fly. You can customize its behavior through the settings panel found under Appearance > Orphans, or extend functionality with WordPress filters for advanced use cases.</p>
<h4>Ideal For</h4>
<ul>
<li>Bloggers, publishers, and editors seeking to maintain high typographic standards.</li>
<li>Sites in languages (like Polish or Czech) where orphan control is a common publishing requirement.</li>
<li>Anyone wanting to enhance the professional appearance and readability of their WordPress content.</li>
</ul>
<h4>Open Source & Developer Friendly</h4>
<p>Orphans is open source, actively maintained, and available on <a href="https://github.com/iworks/sierotki" rel="nofollow ugc">GitHub</a> for those interested in contributing or extending its features.</p>
<h4>Asset image</h4>
<p><a href="http://www.flickr.com/photos/calliope/306564541/" rel="nofollow ugc">Manuscript by Muffet, on Flickr</a></p>


Orphans

Supports the grammar rule for orphan words at the end of a line.

Thumbnail Manager vs Orphans