Muhammad Zaki

ProgMaze

Muhammad Umar

Need to know which posts, builders, or meta fields still reference an image—or which uploads are safe to remove?
ProgMaze Media Scanner runs a deep scan of your site: it walks public post types (including templates), reads <code>post_content</code> and <code>post_meta</code>, parses Gutenberg-style block data, URLs, featured images, and nested serialized or JSON values so you get a clear picture of where each file is used and what is unused.
<h4>Key Features</h4>
<ul>
<li>Full site scan — Scans all post types, pages, custom post types, templates, and reusable blocks.</li>
<li>Gutenberg aware — Parses block JSON attributes (core/image, core/gallery, core/cover, core/video, core/file, core/media-text, and more) to find media IDs.</li>
<li>Page builder support — Scans media used in Gutenberg, Avada, Elementor, and similar setups that store IDs or URLs in content or meta.</li>
<li>Featured image tracking — Detects when a media item is used as a featured image on any post or custom post type.</li>
<li>Post meta scanning — Finds media in ACF fields, WooCommerce product galleries, and other plugins that store attachment IDs or URLs in meta.</li>
<li>Usage detail view — Open any item to see every post that uses it, with Edit and View links and usage type (content, featured image, meta, gallery, setting).</li>
<li>Safe deletion — Only unused media can be deleted directly; used items can be detached first or removed with Detach & Delete.</li>
<li>Bulk delete — Remove multiple unused items in one action.</li>
<li>Incremental updates — Saving a post re-scans that post only, keeping the cache fresh without a full rescan.</li>
<li>Filters — All / Used / Unused, mime type filters, and search by filename.</li>
<li>Library overview — On the main screen: total storage, image vs non-image space, space by file type (bars), largest uploads, and most-referenced media (cached for performance).</li>
</ul>
<h4>Supported for</h4>
<ul>
<li>WordPress Gutenberg (core blocks)</li>
<li>Elementor</li>
<li>Avada</li>
<li>ACF (Advanced Custom Fields)</li>
<li>WooCommerce (featured image + gallery)</li>
<li>Builders that store media URLs or IDs in <code>post_content</code> or <code>post_meta</code></li>
</ul>
<h3>How it works</h3>
When you run Scan All Media, the plugin rebuilds its usage cache: it inspects content and meta for attachment IDs, upload URLs, <code>_thumbnail_id</code>, WooCommerce galleries, and nested structures. Each link is stored with a usage type. Saving a post triggers a targeted re-scan for that post only.
On Media → ProgMaze Media Scanner, filter by used or unused, narrow by type, search by filename, use View Usage for details, and delete or Detach & Delete as needed. Deletions are permanent—back up first.

ProgMaze Media Scanner

Deep scan of where media is used site-wide; find unused library files and delete or detach them safely.

Junaid Bhura

<a href="https://github.com/junaidbhura/fly-dynamic-image-resizer" rel="nofollow ugc">Check out the Github Repository ♥</a>
One of the biggest problems theme developers face is the problem of multiple image sizes. When you upload an image in the media library, WordPress automatically creates thumbnails based on all the image sizes you have defined using <code>add_image_size()</code> whether you want to use them or not. So the vast majority of the images in wp-content/uploads directory are a waste, and are never used. This is not the optimum way of creating image sizes.
With this plugin, you can create as many image sizes as you want without the guilt of unnecessary image sizes taking up your disk space!
This is because the images created using this plugin are dynamically created when the image is called for the first time, rather than when it is uploaded. You can also delete the cached images for each image individually, or all the cached images.
<h4>How this plugin works</h4>
<ol>
<li>You either define an image size in your code using the <code>fly_add_image_size()</code> function, or directly call the image size in the code</li>
<li>The admin uploads the image in the media library, but the fly dynamic images are not created</li>
<li>The user visits the page for the first time, and the image is dynamically created and is stored</li>
<li>The user visits the page again for the second time, and the stored version of the image is served</li>
</ol>
<h4>Documentation</h4>
Here are some functions and example code to get you started!
fly_get_attachment_image_src( $attachment_id, $size, $crop )
<ul>
<li>attachment_id (integer)(required) : The ID of the image attachment</li>
<li>size (string/array)(required) : Either the name of the pre-defined size defined using <code>fly_add_image_size</code>, or an array with the width and height. Ex: array( 500, 500 )</li>
<li>crop (boolean/array)(optional) : Whether the image should be cropped, or the crop position</li>
</ul>
Returns an array:
<pre><code>array(
 'src' => string,
 'width' => integer,
 'height' => integer
)
</code></pre>
 
fly_get_attachment_image( $attachment_id, $size, $crop, $attr )
<ul>
<li>attachment_id (integer)(required) : The ID of the image attachment</li>
<li>size (string/array)(required) : Either the name of the pre-defined size defined using <code>fly_add_image_size</code>, or an array with the width and height. Ex: array( 500, 500 )</li>
<li>crop (boolean/array)(optional) : Whether the image should be cropped, or the crop position</li>
<li>attr (array)(optional) : An array of attributes. Ex: <code>array( 'alt' => 'Alt text', 'title' => 'Title text', 'class' => 'my-class', 'id' => 'my-id' )</code></li>
</ul>
Returns a HTML IMG element string:
<pre><code><img src="http://yoursite.com/wp-content/uploads/fly-images/10/your-image-500x500-c.jpg" width="500" height="500" alt="Alt text" />
</code></pre>
 
<h4>Example 1: Pre-defined Image Sizes</h4>
In this method, you define as many image sizes as you want in your functions.php file.
<pre><code>if ( function_exists( 'fly_add_image_size' ) ) {
 fly_add_image_size( 'home_page_square', 500, 500, true );
 fly_add_image_size( 'home_page_square_2x', 1000, 1000, true );
 fly_add_image_size( 'cropped_top_left', 1000, 1000, array( 'left', 'top' ) );
}
</code></pre>
Now, lets get the post thumbnail using the image sizes we just defined:
<pre><code><?php echo fly_get_attachment_image( get_post_thumbnail_id(), 'home_page_square' ); ?>
</code></pre>
Here’s another way you can do this:
<pre><code><?php $image = fly_get_attachment_image_src( get_post_thumbnail_id(), 'home_page_square' ); echo '<img src="' . $image['src'] . '" width="' . $image['width'] . '" height="' . $image['height'] . '" />'; ?>
</code></pre>
Let’s get the image from our example above which has a crop position defined:
<pre><code><?php echo fly_get_attachment_image( get_post_thumbnail_id(), 'cropped_top_left' ); ?>
</code></pre>
 
<h4>Example 2: Dynamic Image Sizes</h4>
Lets get the post thumbnail using some dynamic image sizes:
<pre><code><?php echo fly_get_attachment_image( get_post_thumbnail_id(), array( 500, 500 ), true ); ?>
</code></pre>
Here’s another way you can do this:
<pre><code><?php $image = fly_get_attachment_image_src( get_post_thumbnail_id(), 'home_page_square', array( 500, 500 ), true ); echo '<img src="' . $image['src'] . '" width="' . $image['width'] . '" height="' . $image['height'] . '" />'; ?>
</code></pre>
Lets get the post thumbnail cropped from the bottom right:
<pre><code><?php echo fly_get_attachment_image( get_post_thumbnail_id(), array( 500, 500 ), array( 'right', 'bottom' ) ); ?>
</code></pre>
 
<h4>A note on Crop Positions</h4>
Crop positions are set using an array. The first parameter of the array needs to be the x-axis crop and the second parameter needs to be the y-axis crop. This feature will not work the other way around.
For example:
✓ <code>fly_get_attachment_image( get_post_thumbnail_id(), array( 500, 500 ), array( 'right', 'bottom' ) )</code> Will work! 🙂
✘ <code>fly_get_attachment_image( get_post_thumbnail_id(), array( 500, 500 ), array( 'bottom', 'right' ) )</code> Will not work! 🙁
<h4>Detailed Documentation</h4>
Check out the GitHub repository’s Wiki page for the full documentation: <a href="https://github.com/junaidbhura/fly-dynamic-image-resizer/wiki" rel="nofollow ugc">https://github.com/junaidbhura/fly-dynamic-image-resizer/wiki</a>

Fly Dynamic Image Resizer

Since it generates images upon request, another hidden benefit for me has been being able to .gitignore the folder with the generated images. The source images still get added at three different sizes in the media library (which is still useful for things like internal images for blog posts), but a large portion of the images just get ignored by the repo but then re-created by the server when requested.

Very, Very Useful!

Hello,

thank you for this great plugin I use it on every web!

I have one question - is there a way to process image from URL from another web?
For example to download and crop youtube thumbnails... I can write script to do it store image locally and then use one of fly_ functions, but my question is if there is something in your plugin that can process URL directly

Great plugin! But 1 question:

I have clients with sites that are 1GB large because of image sizes I need to create for Pagespeed or just layout purposes. One client has a 20GB /wp-content folder.

That is ridiculous, but before this plugin, seemed necessary. This is an amazing, elegant solution and really should be included in core, i.e., "Don't create an image size until it's actually used."

Thank you!

Excellent plugin and should be a standard

One of my "go to" plugins for just about any site - straightforward and does the job well.  One modification that I have made is so that you can specify just the height OR width and are not required to specify both.  

Great Plugin

Dynamically create image sizes on the fly!

ProgMaze Media Scanner vs Fly Dynamic Image Resizer