Optimize Database after Deleting Revisions vs WP-Sweep
Updated 11 Oct 2026. 22 features compared side by side.
Free one-click database optimiser that deletes revisions (keeping the newest if you like), trash, spam and transients, with scheduling and multisite support.
Free, settings-free database sweeper by Lester Chan that removes revisions, orphaned meta and junk using WordPress's own delete functions, with WP-CLI.
Choose Optimize Database after Deleting Revisions if…
- You need scheduled cleanup and limit future revisions
- You also want keep recent data
- You want the more complete feature set (53/100 vs 44/100)
Choose WP-Sweep if…
- You need WP-CLI
- You prefer the more widely used option
Optimize Database after Deleting Revisions includes 3 features that WP-Sweep lacks, including Limit future revisions, Scheduled cleanup and Keep recent data; WP-Sweep has 1 that Optimize Database after Deleting Revisions lacks, including WP-CLI. Both include 10 of the 22 features we track.
At a glance
Feature comparison
Click a screenshot to see both plugins side by side.
Optimize Database after Deleting Revisions WP-SweepCleanup5/85/8
Deletes revisions of posts, pages and/or custom post types.
Revision sweep deletes all revisions using wp_delete_post_revision().
Deletes trashed posts and pages; auto-drafts are removed as orphan post items.
Separate sweeps for auto-drafts and trashed (deleted) posts.
Removes spam and trashed comments plus pingbacks/trackbacks, but not unapproved comments.
Sweeps unapproved, spam and trashed comments.
Optionally deletes expired transients or all transients.
Transient sweep clears transient options via delete_transient() and delete_site_transient().
Deletes orphaned post meta and orphaned term relationships only; no comment, user or term meta.
Removes orphaned and duplicated post, comment, user and term meta plus orphaned term relationships.
Does not detect tables left behind by removed plugins.
Does not detect or remove tables left by uninstalled plugins.
No detection of leftover options or cron events.
No detection of leftover options or cron events from removed plugins.
No Action Scheduler cleanup.
No Action Scheduler cleanup sweep.
Optimisation2/51/5
Optimises tables after cleanup; InnoDB tables included only if enabled.
Optimise sweep runs OPTIMIZE TABLE on tables with this install's prefix.
No table repair function listed.
No repair function among the sweeps.
No autoload reporting or switches.
No autoload reporting or toggles.
Can optimise InnoDB tables but does not convert MyISAM to InnoDB.
No storage-engine conversion.
Each run keeps only the newest X revisions, but it does not change WordPress's own revision limit.
No setting to cap future revisions.
Automation & safety4/52/5
Runs hourly, twice daily, daily or weekly, optionally at a set time; Unix crontab also supported.
Schedules no events; sweeps run manually, via WP-CLI or REST (which you could cron yourself).
Analyze buttons give a summary or detailed report of what would be cleaned.
Shows counts and a Details sample (up to 500 items by default) of what each sweep removes.
Keep the newest X revisions or delete only revisions older than X days.
No option to keep recent revisions or items newer than X days.
No backup feature; the plugin advises making backups first.
No backup; the readme says sweeps are irreversible and advises backing up first.
Exclude specific tables from optimisation and protect posts with a keep_revisions field.
Code filters whitelist meta keys, term IDs and taxonomies; no admin UI for exclusions.
Insights & admin2/43/4
Reports savings per run and in an exportable log, but no detailed table-size browser.
Shows item counts and their percentage of each table, not sizes in bytes.
Does not show which plugin created tables or options.
Does not identify which plugin created tables or options.
Network-activate and one run optimises every site in the network.
Runs per site; uninstall cleans the whole network but no network-wide sweep is documented.
No WP-CLI commands; a PHP file can be called from the Unix crontab instead.
wp sweep command runs all sweeps or named ones.
Statuses: Yes Pro Add-on Partial 3rd-party No ?
Pricing compared
Optimize Database after Deleting Revisions Free
| Free | $0 |
|---|---|
| Free | Free per year, Unlimited |
WP-Sweep Free
| Free | $0 |
|---|---|
| Free | Free per year, Unlimited |
Downloads trend
Optimize Database after Deleting Revisions
1,208 downloads last week
WP-Sweep
5,756 downloads last week
Verdict
Optimize Database after Deleting Revisions scores higher on our feature checklist (53/100 against 44/100) and includes scheduled cleanup, limit future revisions and keep recent data that WP-Sweep does not. WP-Sweep still has the edge on WP-CLI. Check the features you rely on in the table below before deciding.
Biggest differences
Optimize Database after Deleting Revisions: included. WP-Sweep: not included. Runs hourly, twice daily, daily or weekly, optionally at a set time; Unix crontab also supported.
Optimize Database after Deleting Revisions: partial. WP-Sweep: not included. Each run keeps only the newest X revisions, but it does not change WordPress's own revision limit.
Optimize Database after Deleting Revisions: included. WP-Sweep: not included. Keep the newest X revisions or delete only revisions older than X days.
Optimize Database after Deleting Revisions: not included. WP-Sweep: included. wp sweep command runs all sweeps or named ones.
Written from the feature, pricing and install data on this page, not from hands-on testing. How we compare.
Which would you choose?
0 votes so far. Vote to see the results.
Compare something else
Optimize Database after Deleting Revisions vs others
Database Cleaner/Optimize Database after Deleting Revisions
Advanced Database Cleaner/Optimize Database after Deleting Revisions
Optimize Database after Deleting Revisions/Perfmatters
Optimize Database after Deleting Revisions/WP-Optimize
Optimize Database after Deleting Revisions/WP Rocket Best Optimize Database after Deleting Revisions alternatives →
FAQ
Which is better, Optimize Database after Deleting Revisions or WP-Sweep?
Optimize Database after Deleting Revisions scores higher on our feature checklist (53/100 against 44/100) and includes scheduled cleanup, limit future revisions and keep recent data that WP-Sweep does not. WP-Sweep still has the edge on WP-CLI. Check the features you rely on in the table below before deciding.
Which has more features?
Optimize Database after Deleting Revisions includes 13 of the 22 features we track, against 11 for WP-Sweep. Feature count is only part of the picture; check which of the differences matter to you.
Is Optimize Database after Deleting Revisions free?
Optimize Database after Deleting Revisions has a free version on WordPress.org.
Is WP-Sweep free?
WP-Sweep has a free version on WordPress.org.
Feature data last changed 11 Oct 2026. Spotted something wrong? Suggest an edit to Optimize Database after Deleting Revisions or WP-Sweep. Some links are affiliate links. We may earn a commission at no cost to you; it never affects our data or rankings.