by
Muhammad Zeeshan Ejaz
1 (0 reviews)
ZEJ Mediatidy - Media Library Cleanup: Unused Images, Duplicates, WebP & Compression
Find unused images, catch duplicates, convert to WebP and compress. Runs on your own server. Free, unlimited, no account, no API key.
ZEJ Mediatidy ranks #66,345 among WordPress.org plugins with 1+ active installations, a 1/5 rating from 0 reviews, and was last updated Aug 12, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7 (Current: 7.1.1)
v1.0.1
Current Version v1.0.1
Updated 1 month ago
Last Update on 12 Aug, 2026
Refreshed 13 hours ago
Last Refreshed on
Rank
#66,345
—
No change
Active Installs
1+
-75%
KW Avg Position
N/A
—
No change
Downloads
168
+2 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
60,343
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 9 more installs to reach 10+
Rank Changes
Current
#66,345
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.1
- Last Updated
- Aug 12, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- Muhammad Zeeshan Ejaz
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about ZEJ Mediatidy - Media Library Cleanup: Unused Images, Duplicates, WebP & Compression
That is the failure I designed hardest against. An image is only reported unused after Mediatidy has checked post content across all statuses, post meta, the options table, theme mods, the site logo, the site icon, custom CSS, widgets, term meta, user meta, menu items, reusable blocks, template parts and WooCommerce product galleries, including the resized variants of the file. Checking post content and post meta alone is what makes a scanner report a site logo as unused, so Mediatidy checks all of the above instead. It also re-verifies at the moment of deletion, and deletion is recoverable anyway.
Deletion moves the attachment into the Mediatidy trash, where the post row, the metadata and the files are all preserved. Restore puts it back with the same attachment ID, so anything still pointing at it keeps working. Compression and resizing back up the original file before writing, and there is a restore for those too. The only irreversible action in the plugin is emptying the trash, which you have to do on purpose.
Yes. Page builders store their layouts in post meta, and Mediatidy scans post meta including serialized builder data. WooCommerce product galleries and product images are checked specifically, since those live in meta keys a plain content scan misses entirely.
No. Nothing leaves your server. Every scan, hash, conversion and compression happens locally through GD or Imagick on your own host. There is no outbound request to any service, mine or anyone else's.
No. Install it and use it. There is nothing to sign up for and nothing to enter.
It is free and unlimited. Because the processing happens on your hardware rather than on a server I pay for, a 50,000 image library costs me the same as a 50 image one, so there is no image count to meter.
That is the case it was written for. Scans are batched, cursors are stored between requests, duplicate detection compares file sizes before it hashes anything, and results stream in as they are found. Libraries in the tens of thousands are the design target rather than the edge case.
Yes, and I would rather say so plainly. Compression and resizing rewrite the file in place, which is the only way the savings are real. Mediatidy copies the original to a backup location first, marks the attachment as already processed so a second pass cannot compound the quality loss, and gives you a restore action. If that copy cannot be made, for instance because the disk is nearly full, the edit does not happen at all and Mediatidy tells you why. WebP conversion is different: it writes new files and leaves your original alone.
Mediatidy converts the picture and every size your theme generated from it, then serves those copies in place of the originals. Your original files stay on disk untouched, so this costs disk space and saves your visitors download size. If a picture is later shrunk, resized, cleaned or restored, its WebP copies are deleted, so nobody is ever served a copy of a version you replaced.
Yes. Metadata removal rewrites the file container and copies the compressed image data across byte for byte, so the picture itself is never re-encoded and never loses quality. The original is still backed up first, so the restore action covers it either way. A file laid out in a way Mediatidy cannot rewrite safely is reported and left alone.