Simple Revision Control
View on WordPress.orgScores higher than 28% of indexed plugins
About
Easily control and limit post revisions per post type to keep your WordPress database clean and optimized—no coding required!
What It Does
Simple Revision Control lets you set a maximum number of revisions stored per post type (or disable revisions entirely) directly from the WordPress settings screen, with no code edits required. It cleans up existing excess revisions on demand and keeps the wp_posts table from bloating with autosaved copies over time.
Who It's For
This plugin fits small-to-medium WordPress sites where database size and hosting costs matter, especially content-heavy blogs, news sites, and multisite networks that generate many revisions across custom post types. It is well suited for site owners who want a no-code, set-and-forget tool rather than a custom wp-config.php approach.
Who Should Skip It
If you already manage revisions via wp-config.php constants or `WP_POST_REVISIONS` in code, you do not need this plugin. Sites with very low editing activity, or those that intentionally rely on a long revision history for compliance or editorial review, should skip it to avoid losing recoverable copies.
The Bottom Line
Simple Revision Control does one focused job and does it well, with an active last-update date and clean WordPress 6.8.5 compatibility. The low install count and absent support history mean you should not expect rapid help if something breaks, but the surface area of the plugin is small enough that risk is limited. Score 59.96/100 places it in the mid tier, a reasonable pick for revision management but not a top recommendation overall.
Related Plugins
Pick Post Duplicator instead when your main need is cloning posts or pages, since revision control is a side benefit rather than its focus.
Pick Post Type Switcher when you need to reassign content between post types, a job unrelated to revision cleanup.
Pick Custom Post Type Permalinks when your concern is URL structure for custom post types, not database bloat from revisions.
Pick Header and Footer Scripts when you need to inject code site-wide, which has nothing to do with revision management.
Pick Page Links To when you want to point pages at external URLs, a completely different problem from revision storage.