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.

CaphLabs

Keep Originals Safe, convert JPEG/PNG images to WebP and makes WebP the canonical file. WP returns <code>.webp</code> URLs, Keeping originals safely archived.
<h3>How it works (high level)</h3>
<ol>
<li>
Convert
<ul>
<li>For a JPG/PNG attachment, the plugin generates a WebP for the full image and all WordPress-generated sizes.</li>
<li>Conversion is done through WordPress’ image editor system (WP_Image_Editor), meaning it uses GD or Imagick (whichever your server supports) with WebP support enabled.</li>
</ul>
</li>
<li>
Move originals
<ul>
<li>The original JPG/PNG files are moved to:
<ul>
<li><code>wp-content/uploads/_originals/...</code></li>
</ul>
</li>
<li>The folder structure mirrors your uploads structure.</li>
</ul>
</li>
<li>
Update WordPress to serve WebP
<ul>
<li>Attachment “file” + metadata are updated so WordPress serves <code>.webp</code> as the attachment file.</li>
<li>Attachment mime type is updated to <code>image/webp</code>.</li>
</ul>
</li>
<li>
Optional: Replace old URLs everywhere
<ul>
<li>If enabled, the plugin can replace old <code>.jpg/.png</code> URLs across:
<ul>
<li>post content</li>
<li>postmeta</li>
</ul>
</li>
<li>Replacement is serialized-safe (does not break serialized arrays).</li>
</ul>
</li>
</ol>
<h3>Background jobs (keeps running after page reload)</h3>
Conversion/repair/sweep jobs are designed to run in the background. They keep ticking even if you refresh the page or close the tab.
The plugin uses multiple loopback methods (admin-post / REST / public tick fallback) so it can keep working even on restrictive hosting setups.
<h3>Log + “it looks frozen” note</h3>
A rolling “terminal style” log is written to: 
– <code>wp-content/uploads/hsbc-webp-only/logs/webp-only.log</code>
If the log appears to freeze in the admin page: 
– click Refresh Log, or 
– refresh the page
The job may still be running server-side; refreshing the log/page usually catches up.
<h3>Usage</h3>
Go to Media → WebP Only.
<h3>Settings</h3>
<ul>
<li>Quality
<ul>
<li>WebP quality for conversion (0–100).</li>
</ul>
</li>
<li>Batch size
<ul>
<li>How many items to process per tick. Smaller batches reduce server load.</li>
</ul>
</li>
<li>Replace old .jpg/.png URLs across content + postmeta (serialized-safe)
<ul>
<li>Recommended if your site content contains hard-coded image URLs.</li>
</ul>
</li>
<li>Sweep Include / Exclude
<ul>
<li>Used by the Sweep tools to control which folders are scanned.</li>
</ul>
</li>
</ul>
<h3>Conversion Jobs (buttons)</h3>
Start Bulk Convert 
– Converts Media Library attachments (JPG/PNG) in batches. 
– Moves originals to <code>uploads/_originals/</code>. 
– Updates attachment metadata so WordPress serves <code>.webp</code>. 
– Optional URL replacement (content + postmeta).
Start Repair/Cleanup 
– Repairs inconsistencies if something was partially converted or moved. 
– Useful after restores/migrations or if some attachments have mismatched metadata. 
– Optional URL replacement.
Start Folder Sweep 
– Scans the filesystem for eligible images (based on your Sweep Include/Exclude rules). 
– Designed for sites with additional image folders beyond standard uploads. 
– Optional URL replacement.
Stop Job 
– Stops the currently running job.
<h3>Maintenance / Cleanup (buttons)</h3>
Delete duplicate _originals 
– Deletes backup files in <code>uploads/_originals/</code> *only when* an identical file already exists in <code>uploads/</code>. 
– This is a cleanup tool for situations where originals were restored back into uploads and you no longer need the archived duplicate.
Delete duplicate _webp 
– Removes orphaned WebP cache files in: 
 – <code>uploads/_webp/</code> 
– Only deletes WebP files that no longer match anything in <code>uploads/</code> or <code>uploads/_originals/</code>.
Delete duplicate sweep _originals 
– Maintenance cleanup for non-uploads roots (folders under <code>wp-content/</code>) that contain their own <code>_originals/</code> folders. 
– It uses your Sweep Include list to find those roots. 
– Only deletes a file from <code><root>/_originals/</code> when the same file exists at <code><root>/</code> AND the file size matches (safe duplicate).
Revert Everything 
– Restores original JPG/PNG files from <code>uploads/_originals/</code> back into <code>uploads/</code>. 
– Reverts attachment metadata so WordPress serves the originals again.
<h3>Log controls</h3>
Refresh Log 
– Pulls the latest log tail into the admin screen.
Reset Log 
– Clears the log file.
<h3>Requirements</h3>
<ul>
<li>WordPress’ image editor must support WebP.
<ul>
<li>GD with WebP support, or</li>
<li>Imagick with WebP support</li>
</ul>
</li>
<li>If WebP conversion is not supported on your server, conversion/repair/sweep will refuse to run (revert tools can still work).</li>
</ul>

OrigiSafe — Advanced Image Optimizer (WebP) — Keep Originals Safe

Convert JPG/PNG uploads (and existing library) to WebP, move originals to /uploads/_originals/, and update Media Library metadata - WP serves .webp

ProgMaze Media Scanner vs OrigiSafe — Advanced Image Optimizer (WebP) — Keep Originals Safe