- Article
- Intermediate
- 2 minutes read
- Reviewed August 4, 2026
- WordPress maintenance and troubleshooting
Unused data can increase storage, backup time, confusion and attack surface.
Cleanup should begin with ownership and evidence. An unfamiliar table or option is not automatically safe to delete.
Software
Remove:
- Inactive plugins no longer required.
- Unused themes except an intentional fallback.
- Old manual copies.
- abandoned custom code.
- installers and archives left in public directories.
Record licences and data behavior before uninstalling.
Content and Media
Review:
- Drafts and abandoned pages.
- Duplicate imports.
- Unused taxonomies.
- unattached or unreferenced media.
- obsolete downloads.
- generated image sizes.
- old form entries.
- expired temporary content.
Media usage can exist in blocks, options, CSS, custom fields and external systems, not only attachment relationships.
Database Data
Potential cleanup areas include:
- Revisions.
- expired transients.
- sessions.
- queues.
- logs.
- orphaned metadata.
- plugin tables.
- unused autoloaded options.
Use plugin documentation, code ownership and backups before deletion.
A Safe Cleanup Process
- Inventory the candidate.
- Identify its owner.
- Confirm retention requirements.
- Back up files and database.
- Test on staging.
- Remove a bounded set.
- verify functionality.
- monitor errors.
- document the change.
Frequently Asked Questions
Does deleting revisions always improve speed?
Not necessarily. Revisions affect storage and selected queries, but broad performance depends on actual access patterns.
Can a database-cleaner plugin decide everything automatically?
It can identify candidates, but ownership and business requirements still need human review.
Continue Learning
Previous: Maintaining the WordPress Database