Do WordPress Post Revisions Slow My Database?

Why Revisions Exist

Revisions provide a genuinely useful safety net, letting an editor restore an earlier version of content if a recent edit was a mistake, or simply review how content evolved over time. The tradeoff is that WordPress core doesn't limit revision count by default, so a frequently edited post accumulates a new full copy with every single save, which adds up meaningfully on a site with years of active editing.

When This Becomes a Real Issue

• A long-running site with content edited frequently over years can accumulate a genuinely large number of revision rows, adding real, measurable bloat to the database.
• A newer or infrequently edited site generally has much less to worry about here, since revision count scales with editing frequency and time, not simply content volume.
• Database bloat from revisions can slightly slow certain queries and definitely increases backup size and time, even if it rarely causes dramatic, obvious performance problems on its own.
• Autosave drafts (WordPress's periodic automatic save while editing) also contribute to this accumulation, separate from manually triggered saves.

Managing Revisions

1. Set a revision limit via the WP_POST_REVISIONS constant in wp-config.php, capping how many revisions are kept per post going forward.
2. Clean up existing excess revisions using a dedicated database cleanup plugin, carefully, on an established site with a long history.
3. Take a full backup before any bulk revision cleanup, since it's a database-modifying operation.

Need database cleanup and optimization done safely? See WordPress speed optimization.