In short: Media Cleaner and Mediapapa both detect unused media, but they take opposite approaches to safety. Media Cleaner moves unused files to an internal trash and lets you delete them after review — the safety net is the trash. Mediapapa maps every file to every reference before you act — the safety net is the usage index. If you manage sites with ACF, Elementor or serialised data, that distinction matters: Media Cleaner can miss references in those contexts, Mediapapa scans them explicitly.
What Media Cleaner does
Media Cleaner (Meow Apps, 4.4M+ downloads) scans your WordPress site for media files and database entries that appear unused, moves them to an internal trash, and lets you delete them after review. It also scans the filesystem for files not registered in WordPress at all — an edge case Mediapapa does not currently cover. A WP-CLI integration is available in the Pro version.
The plugin’s philosophy is cleanup-first: it assumes files that appear unused are safe to move to trash, and provides a restore mechanism as a safety net. It does not score files, does not produce a library health view, and does not handle metadata, duplicates or compression.
The core difference: delete-first vs governance-first
Media Cleaner identifies what looks unused and moves it to trash. You discover errors after the fact if something breaks. Mediapapa maps every file to every reference — posts, pages, Gutenberg blocks, ACF fields, Elementor meta, widget areas, nav menus — before you act. You see exactly what is referenced before deciding anything.
In practice, Media Cleaner has a documented limitation with serialised data and complex field structures: it can miss references stored in ACF, custom post type meta or page builder data. Mediapapa’s usage index scans all of these explicitly. Both approaches have edge cases, but Mediapapa’s approach is to surface information before deletion rather than discover broken references after.
Feature comparison
| Feature | Media Cleaner Pro | Mediapapa (free) | Mediapapa Pro |
|---|---|---|---|
| Unused media detection | ✓ | ✓ | ✓ |
| Internal trash before deletion | ✓ | — | — |
| Filesystem scan (files outside WordPress) | ✓ | — | — |
| ACF / Elementor / serialised data scanning | Partial | ✓ | ✓ |
| Usage index (per-file reference map sitewide) | — | ✓ | ✓ |
| Deletion Warnings | — | ✓ | ✓ |
| Library Health (library-wide score) | — | ✓ | ✓ |
| Media Score (per-file health) | — | ✓ | ✓ |
| Duplicate detection | — | ✓ | ✓ |
| Safe Replace (sitewide ID and URL swap) | — | ✓ | ✓ |
| Image compression (WebP, AVIF) | — | — | ✓ |
| AI-assisted alt text, title and caption | — | ✓ (credits) | ✓ (credits) |
| Media tagging and advanced search | — | ✓ | ✓ |
| Pre-publish health checks | — | ✓ | ✓ |
| WP-CLI support | ✓ | — | ✓ |
| Pricing | From 39$/yr | Free | from $49/yr (1 site) |
Key differences
The philosophical difference is where the safety net sits. Media Cleaner puts the safety net after the action — you move files to trash, and if something breaks you restore them. Mediapapa puts the safety net before the action — the usage index shows what is referenced, and Deletion Warnings block removal of any file still in use. For teams that prioritise knowing the full picture before touching anything, that is a meaningful distinction.
The scope difference is also concrete. Media Cleaner’s primary value is identifying and removing files that do not appear to be in use. Mediapapa’s scope is broader: Library Health, Media Score, Safe Replace, duplicate detection, metadata quality, compression and pre-publish checks. If you need a cleanup tool only, Media Cleaner is narrowly effective. If you need ongoing governance across the whole library, Media Cleaner covers only one part of that.
The one area where Media Cleaner has a genuine advantage over Mediapapa is filesystem scanning: it can identify files on disk that are not registered in the WordPress database at all. Mediapapa only scans registered attachments. For sites with a history of FTP uploads or manual file transfers, Media Cleaner’s filesystem scan reaches files Mediapapa cannot see.
Can you use both?
Yes. A practical setup is to use Mediapapa for ongoing governance — usage tracking, health scoring, Deletion Warnings and metadata — and Media Cleaner for a one-time filesystem scan to surface files outside the WordPress database. They do not conflict. Once the filesystem is clean, Mediapapa’s usage index handles the ongoing work.
Who should choose what
Choose Media Cleaner if
You need to scan the filesystem for files outside the WordPress database — FTP uploads, leftover files from theme changes or manual transfers.
You prefer a trash-based undo model where files are moved before deletion and can be restored if something breaks.
Cleanup is a one-time project rather than ongoing governance, and you need the lightest possible footprint.
Choose Mediapapa if
You want to know exactly where every file is referenced — including in ACF, Elementor, custom post types and serialised data — before deciding whether to delete it.
You use complex field structures where Media Cleaner’s detection can miss live references and produce false positives.
You need ongoing governance beyond cleanup: health scoring, duplicate detection, metadata quality, compression and pre-publish checks in a single plugin.
Frequently asked questions
Yes. They do not conflict. A practical combination is to use Media Cleaner for a one-time filesystem scan — to surface files on disk that are not registered in WordPress — and Mediapapa for ongoing governance. Once the filesystem is clean, Mediapapa’s usage index handles unused media detection, health scoring and deletion protection going forward.
Partially. Media Cleaner scans standard WordPress attachment references but can miss files stored in serialised data, ACF field values, Elementor widget meta and some custom post type structures. This is a documented limitation — files that appear unused to Media Cleaner may still be actively referenced in content. Mediapapa’s usage index scans all of these contexts explicitly before any action is taken.
No. Mediapapa’s approach is to prevent accidental deletion through Deletion Warnings rather than provide a recovery mechanism after the fact. When you attempt to delete a file that is still referenced in content, Mediapapa blocks the action and shows you exactly where it is used. Files you delete through Mediapapa go to the standard WordPress media trash, not an internal one.
Yes, in one specific case. Media Cleaner scans the server filesystem and can surface files on disk that are not registered as WordPress attachments at all — files uploaded via FTP, leftover from theme changes or created outside WordPress. Mediapapa only scans registered attachments. If your site has a history of manual file transfers, Media Cleaner’s filesystem scan reaches files Mediapapa cannot see.
Yes. Deletion Warnings trigger automatically when you attempt to delete a file that is still referenced in content, preventing accidental breakage without requiring a manual audit. Media Cleaner’s safety net is the internal trash — files are moved there before permanent deletion, and you can restore them if something breaks after the fact.
No. Media Cleaner’s scope is cleanup only. It has no health scoring, no metadata editing, no duplicate detection and no compression. Mediapapa covers all of these as part of a governance layer built around the usage index.
Related comparisons
Curious what is hiding in your library?
Scan it for free. See exactly what is used before you delete anything.