Optimize Database after Deleting Revisions
View on WordPress.orgScores higher than 91% of indexed plugins
About
One-click database optimization with precise revision cleanup and flexible scheduling. Speeding up sites since 2011!
Security History
What It Does
Optimize Database after Deleting Revisions runs a one-click cleanup that strips old post revisions, auto-drafts, trashed comments, and orphaned metadata, then optimizes the underlying MySQL tables to reclaim space. It includes flexible scheduling so the cleanup can run hourly, daily, or weekly in the background without manual intervention. The plugin has been actively maintained since 2011 and focuses narrowly on database hygiene rather than full-site performance tuning.
Who It's For
This plugin is a strong fit for content-heavy sites that accumulate revision bloat fast, such as newsrooms, multi-author blogs, and WordPress multisite networks with thousands of posts. It is also useful on shared hosting where disk space and query speed are tight, and on legacy WordPress sites that have years of unreviewed revisions piling up in wp_posts.
Who Should Skip It
If your site has under 500 posts, infrequent edits, or you already use a managed host that handles database optimization at the server level, this plugin adds unnecessary complexity and scheduling overhead. Developers who need granular query-level tuning or transients/orphaned table inspection should look at Advanced Database Cleaner instead.
The Bottom Line
Optimize Database after Deleting Revisions is a focused, battle-tested tool that does one job well: removing revision clutter and reclaiming MySQL space. Its 60,000 installs, 94/100 user rating, and recent update give it real credibility, though the absence of public support threads means you will rely on documentation rather than community help. If your site is revision-heavy, this is a sensible pick; if you need broader database tooling or backup features, pair it with one of the alternatives above.
Related Plugins
Pick this if you need deeper cleanup of orphaned tables, transients, and cron options beyond just revisions, and you want a larger install base of 100,000.
Choose this when your main problem is finding and replacing leftover strings in the database after a migration, rather than trimming revision bloat.
Pick this for a one-time URL swap after moving a site to a new domain, a different task than ongoing database optimization.
Choose this if your database bloat comes specifically from Contact Form 7 submissions rather than post revisions, since it manages form entries directly.
Pick this as a companion tool when you need scheduled database backups before running any cleanup, since Optimize Database does not include backup functionality.