A media file can look unused in the Media Library and still power a hero, an Elementor background, a product variation, a reusable block, or a CSS rule. That is why deleting every unattached image is unsafe.
Reliable cleanup separates attachment relationships from actual references. It also considers the underlying original file, generated image sizes, caches, and offloaded storage.
Unattached does not mean unused
WordPress stores a parent relationship for some attachments, but modern sites use media through many other paths. Blocks, builders, theme options, custom fields, products, menus, and CSS can reference an ID or URL without assigning an attachment parent.
Where references hide
References can live in post content, post meta, term meta, options, widget settings, WooCommerce records, and page-builder documents. Some systems store IDs while others store absolute URLs. A useful scanner checks several evidence sources and reports why an asset appears used.
- Block and classic-editor content
- Elementor and builder metadata
- Featured images and galleries
- WooCommerce products and variations
- Theme options, widgets, terms, and custom fields
Duplicates need a migration plan
Hashing can identify exact binary duplicates, but deletion is only safe after references move to a canonical attachment. Generated sizes and responsive image markup also need verification. Keeping an identical file elsewhere does not prevent a broken URL.
Use a reversible cleanup workflow
Begin with a complete backup and a report. Review uncertain results, protect recent uploads, delete small batches, purge caches, and inspect important templates. Mediachecker combines multiple usage signals, duplicate discovery, protected cleanup, and backups.
- Back up files and database
- Generate a report before deletion
- Exclude protected and recent assets
- Delete in small logged batches
- Validate frontend, feeds, emails, and products
Measure the right outcome
Cleanup can reduce storage, backup size, migration time, and editorial confusion. It does not automatically improve page speed if visitors never requested the deleted files. Our safe media cleanup guide explains how to match the workflow to the goal.
Understand false positives and false negatives
A false positive labels a used asset as unused, creating deletion risk. A false negative keeps an unused file, reducing the storage benefit but not breaking the site. Safe cleanup systems should prefer false negatives when evidence is uncertain. Confidence labels are more honest than a single definitive status because WordPress sites can store references in custom code and external systems a scanner cannot fully understand.
Include offloaded media and multisite
CDN rewriting, object storage, translated domains, and multisite networks complicate reference matching. A database may store the original URL while the frontend serves a transformed URL. Network-activated plugins and shared uploads can also create cross-site dependencies. Confirm how URLs are normalized, how offloaded originals are restored, and whether the cleanup scope is one site or the whole network.
Validate beyond visible pages
After a batch, check responsive breakpoints, social previews, feeds, transactional emails, PDFs, structured data, product exports, and integrations that consume media URLs. Review server logs for missing files and keep the backup until normal business cycles have exercised the affected content. A homepage spot check will not reveal every delayed or external use.
Frequently asked questions
Can I delete every unattached image?
No. It may still be referenced by a builder, block, custom field, product, option, or CSS rule.
Does media cleanup speed up WordPress?
It can reduce storage and backup overhead, but frontend speed changes only when requested assets or delivery behavior change.
How do I verify that a file is unused?
Check relationships, content, metadata, options, builder data, products, and URL references. Use multiple signals and review uncertain cases.
Should generated thumbnails be deleted separately?
Normally they should be managed with the parent attachment. Removing sizes independently can break responsive output or require regeneration.
Official references
Need help with a production WordPress plugin? Discuss the requirement with WPStack.
