WP Revisions Control
View on WordPress.orgScores higher than 17% of indexed plugins
About
Control how many revisions are stored for each post type.
What It Does
WP Revisions Control lets you set a custom limit on the number of revisions WordPress keeps for every post type, including custom post types. It adds a simple settings page where you can pick how many revisions to retain per content type, and it also provides a one-click button to purge old revisions from the database. This keeps your wp_posts table lean without needing to write custom code or wp-config.php edits.
Who It's For
This plugin is a good fit for content-heavy sites, editorial teams, or any WordPress installation where the default revision behaviour is bloating the database. It is particularly useful for agencies managing several client sites who want a predictable, GUI-driven way to cap revisions per post type rather than editing wp-config.php on every project.
Who Should Skip It
If you are comfortable adding a single line to wp-config.php or you only run a small personal blog where revisions are not a concern, this plugin is overkill. Sites using a version control workflow or a custom revision strategy already do not need another layer of plugin overhead.
The Bottom Line
WP Revisions Control does one thing and does it well, with a clean settings UI and recent updates that justify its strong user ratings. The overall quality score of 69.54 sits lower because of the tiny rating sample and the absence of any public support thread history, but functionally it is a sensible pick for any site fighting database bloat. Just verify it on a staging copy first if you rely on older PHP versions.
Related Plugins
Pick Loginizer if your real priority is hardening login security across many sites rather than trimming revision bloat.
Pick Redux Framework if you are building admin options panels and want a heavier, more flexible settings framework than this single-purpose tool.
Pick Admin Menu Editor when your main admin customization need is reorganizing menus, not controlling database growth.
Pick White Label CMS if you want to rebrand the WordPress admin for clients more than you want to manage revision storage.
Pick ACF Extended when your site's complexity revolves around custom fields and dynamic content, where revision tuning is only a side concern.