Every WordPress site accumulates digital clutter. Old theme demos leave orphaned images, page builders generate intermediate sizes nobody views, abandoned plugins leave files behind, and every “test upload” from two years ago still sits in your hosting bill. Media Cleaner Pro, from Meow Apps, exists to clean that up without the fear that normally comes with deleting media files. Related reading: our image compression layer overview covers the adjacent workflow.
The problem with cleaning a media library is reference detection: an image that looks unused may be referenced by a shortcode, a widget, a theme option, a page builder layout, or custom CSS. Delete blindly and your site breaks in places you will not notice for weeks. Media Cleaner’s approach is a full scan of both the uploads directory and the live site content — matching every file against every reference it can find, then presenting only genuinely unreferenced items for deletion, with a trash stage in between so nothing disappears permanently.
Competitive Features
Filesystem scan (Pro-exclusive). Beyond comparing Media Library entries, the Pro version matches every physical file in your uploads directory against the library and site references — catching files that were never registered as attachments at all, which the free tier cannot see.
Live-site analysis. The scanner reads your rendered pages — not just the database — so references baked into widgets, theme options, and builder layouts count as “used.”
Page-builder parsers. Dedicated parsers for Divi, SiteOrigin, Elementor-adjacent content, and more; recent releases added SiteOrigin gallery-widget parsing and Divi base64-encoded JSON reference handling. Generic scanners miss exactly these.
Duplicates detection with Inspect. A duplicates scan compares files and marks candidates, with an Inspect button to review and resolve each case from one view instead of guessing.
Trash before deletion. Deleted items land in a managed trash with recovery available regardless of scan state, plus a Force Clean Trash tool for stubborn leftovers in both the database and the filesystem.
Scan safety rails. Files that fail fingerprinting get marked unsafe rather than aborting the scan; unreadable duplicates are skipped; oversized references no longer kill the whole run. This is tooling designed by someone who has broken sites before.
Key Features
- Smart scan — Media Library entries compared against posts, pages, widgets, shortcodes, and builder content.
- Orphan file detection — physical uploads files with no library record identified via filesystem scan.
- Plugin-aware analysis — references from WooCommerce, forms, and known plugins recognized as valid uses.
- Advanced buffer control — an Auto Buffer helper tunes scan batching from server tests, with warnings for slow items.
- Real-time logs — a Live Logs panel shows scan, trash, and delete activity as it happens.
- Error summaries — failed items group into one summary instead of interrupting with modal after modal.
- AI site analysis — a dashboard view that profiles the site and flags cleanup opportunities.
Comparison with Competitors
Media Cleaner Pro vs Media Deduper Advanced
Both target library bloat, but their emphasis differs: deduplication versus full unused-file detection.
| Media Cleaner Pro | Media Deduper Advanced | |
|---|---|---|
| Core job | Find unreferenced media (library + filesystem) | Find and merge duplicate media |
| Reference detection | Live-site analysis + builder parsers | Hash-based duplicate matching |
| Builder support | Divi, SiteOrigin, and more | General |
| Trash stage | Managed trash with recovery | Preview-based |
| Best for | Deep cleanup of years of clutter | Libraries flooded with duplicate uploads |
If your problem is ten copies of the same hero image, a deduplicator is the sharper tool. If your problem is “half my uploads folder belongs to nothing,” Media Cleaner’s reference scanning is the answer.
Media Cleaner Pro vs ShortPixel
ShortPixel optimizes and compresses images; Media Cleaner removes them. They solve different halves of media bloat and stack cleanly.
| Media Cleaner Pro | ShortPixel | |
|---|---|---|
| Primary job | Delete unused files | Compress kept files |
| Disk space | Reclaims whole files | Shrinks every file |
| Risk model | Trash stage, reference checks | Non-destructive optimization |
| Combined effect | Smaller library | Faster pages |
Run the cleanup first, then let ShortPixel compress what remains — the ordering matters, since compressing files you are about to delete wastes quota.
Recommended Stack: a media cleanup pairs naturally with a performance layer — fewer bytes on disk usually means fewer bytes on the page. Pairing the library cleanup with an optimization stack like image optimization layer keeps the gains permanent.
Official Changelog
Version 7.2.8
Release Date: September 14, 2026
- Fix: resolved a PHP warning that could appear during scans
Version 7.2.7
Release Date: September 7, 2026
- Added: Inspect button for duplicates; Unlock Scan maintenance tool; Soliloquy parser
- Fixed: duplicates scan skips unreadable files instead of stopping; Force Clean Trash now checks both physical and database leftovers
- Updated: SiteOrigin parser supports the gallery widget; Divi parser handles base64-encoded JSON references
Version 7.2.6
Release Date: August 17, 2026
- Added: SiteOrigin Page Builder support; Auto Buffer helper with server tests; plugin board and AI site analysis on the dashboard
- Fixed: query handling and logging for unbounded database queries
- Updated: minimum PHP version is now 8.1
Frequently Asked Questions
Is it safe to delete what it finds?
The tool is built around safety: items go to a managed trash before real deletion, references from known plugins and page builders count as “used,” and scans fail safe — a file that cannot be verified gets marked unsafe rather than deleted. Still, take a backup first; that is standard practice for any media deletion.
What does the Pro version add over the free Media Cleaner?
The decisive feature is the filesystem scan: matching physical uploads files against library and site references, which catches orphaned files never registered in the Media Library. The free version only compares library entries, so a large share of real clutter stays invisible to it.
Will it understand my page builder’s references?
Recent releases ship dedicated parsers for Divi (including base64-encoded JSON) and SiteOrigin (including gallery widgets), and the live-site analysis catches references rendered on the page regardless of source. Builder ecosystems change constantly, which is why the changelog keeps adding parsers.
Can I recover files after deleting them?
Yes. Trash recovery works regardless of scan state — recovered files stay available even before you run a new scan. A Force Clean Trash option exists for leftovers that resist normal removal.
How does it handle very large media libraries?
Batching is the answer: the Auto Buffer helper tunes buffer sizes from live server tests, failed items group into summaries instead of aborting runs, and attachment lookups for multilingual references were specifically optimized for large sites. Minimum PHP is now 8.1.
Should I clean the library before or after optimizing images?
Clean first. Deleting files you would otherwise compress saves optimization credits and processing time, and tools like ShortPixel work best on the library that actually remains.
Leave a Reply