Steve Grunwell

<p>Unless post revisions are explicitly limited, WordPress will build up a hefty sum of revisions over time. While it’s great to have revision history for some recent content, the chances that old revisions will be necessary diminish the longer a post has been published. Revision Strike is designed to automatically remove these unneeded revisions on older, published posts.</p>
<h4>How does it work?</h4>
<p>First, a threshold is set, with a default of 30 days. Once a day, Revision Strike will run and find any post revisions in the database attached to published posts with a post date of at least 30 (or your custom threshold) days ago, and “strike” (tear-down and remove) them from the WordPress database.</p>
<h4>Contributing</h4>
<p>If you’d like to help build Revision Strike, please <a href="https://github.com/stevegrunwell/revision-strike" rel="nofollow ugc">visit the plugin’s GitHub page</a>. Contributors are welcome, and <a href="https://github.com/stevegrunwell/revision-strike#contributing" rel="nofollow ugc">details can be found in the repo’s README file</a>.</p>


Revision Strike

Periodically purge old post revisions via WP Cron.

Revision Strike vs WP Document Revisions