The Complete Guide to WordPress Post Revisions: Never Lose Content Again
Imagine spending hours crafting the perfect blog post—polishing sentences, refining arguments, adding images—only to accidentally delete a critical paragraph, lose power, or have your browser crash. Panic sets in: all that hard work, gone. But what if there was a safety net built into WordPress that automatically saves your progress, tracks every change, and lets you revert to any previous version of your content?
That safety net is WordPress Post Revisions.
Whether you’re a solo blogger, a content marketer, or part of a team managing a website, post revisions are an indispensable tool for protecting your work, collaborating effectively, and maintaining content quality. In this comprehensive guide, we’ll demystify WordPress post revisions: what they are, how they work, how to access and manage them, and advanced tips to optimize their use. By the end, you’ll be able to leverage revisions to avoid data loss, streamline workflows, and take full control of your content’s history.
WordPress Post Revisions are a built-in feature that automatically saves copies of your posts and pages as you edit them. Think of revisions as a “time machine” for your content: they record every change you make—additions, deletions, formatting edits, and even media insertions—allowing you to revisit, compare, or restore previous versions at any time.
The primary purpose of revisions is to prevent data loss. Whether you accidentally delete a section, your internet cuts out, or a plugin conflict corrupts your content, revisions let you roll back to a working version. They also facilitate collaboration by letting you track who made what changes (and when) if multiple authors edit the same post.
It’s important to distinguish between two types of saved versions in WordPress: autosaves and manual revisions.
Autosaves: These are temporary, automatic saves that WordPress creates while you edit. By default, WordPress autosaves your post every 60 seconds (you can adjust this interval). Autosaves are tied to your user session—meaning if you log out or close the editor without manually saving, the autosave will be discarded. Autosaves are labeled “Autosave” in the revision history and are overwritten by new autosaves every minute.
Manual Revisions: These are permanent saves created when you click the “Save Draft,” “Update,” or “Publish” button. Unlike autosaves, manual revisions are stored indefinitely (unless you limit or disable them) and appear in the revision history with a timestamp, author name, and the label “Revision.”
Revisions are stored in your WordPress database, specifically in the wp_posts table. Each revision is treated as a separate “post” with a post_type of revision and a post_parent value equal to the ID of the original post. This means revisions don’t clutter your main post list—they’re only accessible via the post editor.
For example, if you have a post with ID 123, all its revisions will appear in wp_posts with post_parent = 123 and post_type = revision. This structure ensures revisions are linked to their original content but don’t interfere with your site’s frontend or main post management.
Here’s a step-by-step breakdown of how revisions are generated:
Start Editing: When you open a post in the editor (Gutenberg or Classic), WordPress loads the latest saved version.
Autosave Triggers: As you type, WordPress autosaves every 60 seconds. This autosave is stored temporarily and only visible to you (the current user).
Manual Save: When you click “Save Draft,” “Update,” or “Publish,” WordPress creates a permanent revision and updates the post’s status (e.g., from “Draft” to “Published”).
Revision History Builds: Each manual save adds a new revision to the post’s history. Over time, this creates a timeline of edits you can browse.
By default, WordPress does not limit the number of revisions it stores. This means every manual save (and every autosave that becomes a revision after a manual save) is kept indefinitely. While this is great for safety, it can bloat your database over time—especially if you edit posts frequently or have long-form content. Later in this guide, we’ll show you how to limit revisions to prevent database bloat.
Accessing revision history varies slightly depending on whether you use the Gutenberg Editor (WordPress’s default block editor) or the Classic Editor (the older, TinyMCE-based editor). Here’s how to do it in both:
Open the Post/Page Editor: Go to Posts → All Posts (or Pages → All Pages) and click “Edit” on the post you want to check.
Open the Settings Sidebar: If the sidebar isn’t visible, click the gear icon ⚙️ in the top-right corner of the editor.
Navigate to Revisions: In the sidebar, scroll down to the “Revisions” tab (it may be collapsed under “Status & Visibility” or “Summary”). Click “Revisions” to open the revision history.
Note: If you don’t see the “Revisions” tab, revisions may be disabled for your site (see Configuring Settings).
Open the Post/Page Editor: Go to Posts → All Posts (or Pages → All Pages) and click “Edit” on the post.
Locate the Revisions Meta Box: In the Classic Editor, revisions are typically displayed in a meta box labeled “Revisions” below the editor (you may need to scroll down or expand the “Screen Options” tab at the top to enable it).
View Revisions: Click “Browse” to open the revision history interface.
In the revision interface, click on a revision in the timeline or use the slider to select it. The editor will display the content as it existed at that point.
To compare two specific revisions:
In the revision timeline, check the boxes next to two revisions (labeled “Compare” below each entry).
The interface will update to show the differences between the selected versions, with changes highlighted.
Pro Tip: Use the “Previous” and “Next” buttons to navigate sequentially through revisions, or jump to the oldest/newest revision using the “First” and “Last” buttons.
Restoring a revision replaces your current post content with the selected version. Here’s how:
Select the Revision: In the revision interface, navigate to the version you want to restore.
Review the Content: Double-check that this is the correct revision—restoring will overwrite your current edits!
Click “Restore This Revision”: A confirmation prompt will appear. Click “OK” to proceed.
WordPress will then reload the editor with the restored revision. Your current content (before restoring) will be saved as a new revision, so you can revert again if needed.
By default, WordPress stores unlimited revisions, which can slow down your database over time (especially for large sites with many posts). Fortunately, you can customize revision behavior by editing your wp-config.php file (located in your WordPress root directory).
To restrict WordPress to storing a specific number of revisions per post, add the following line to wp-config.phpbefore the line that says /* That's all, stop editing! Happy publishing. */:
define( 'WP_POST_REVISIONS', 5 ); // Keep the last 5 revisions
Replace 5 with your desired number (e.g., 10 for 10 revisions).
If you want to disable revisions entirely (not recommended—revisions are a safety net!), set WP_POST_REVISIONS to false:
define( 'WP_POST_REVISIONS', false );
Warning: Disabling revisions removes all existing revision history for future posts. Existing revisions will remain in the database but won’t be accessible.
Get in the habit of checking revisions before publishing or updating a post. This helps catch accidental deletions, formatting errors, or unwanted changes (e.g., from a collaborator).
If multiple authors edit the same post, revisions let you track who made what changes. Check the author name and timestamp in the revision timeline to see contributions and resolve conflicts.
Revisions are not a substitute for full backups! Revisions are stored in your database, so if your database is corrupted or hacked, revisions may be lost. Use a backup plugin like UpdraftPlus or VaultPress to create regular offsite backups.
WordPress doesn’t let you name revisions by default, but plugins like Revision Control or WP Revisions Control let you add notes (e.g., “Final draft for review”) to revisions, making them easier to identify later.
Permissions Issue: Ensure your web server has write access to your WordPress files and database.
Large Post Size: Revisions for posts with many images or large content may fail to restore. Try restoring a smaller revision or disabling plugins temporarily.
Autosave Conflict: If you’re editing with autosaves enabled, try manually saving first, then restoring.
By default, revisions are enabled for posts and pages but not for custom post types (CPTs). To enable revisions for a CPT, add 'revisions' => true to your CPT registration code:
By default, revisions track post content but not media (e.g., image changes) or custom fields. Plugins like Advanced Custom Fields (ACF) with the ACF Revisions add-on let you include custom fields in revisions, while Media Revisions tracks image edits.
WordPress Post Revisions are a powerful, underutilized tool that can save you from data loss, streamline collaboration, and keep your content history organized. By understanding how revisions work, configuring them to suit your site, and following best practices, you’ll ensure your content is always protected—no matter what editing mishaps come your way.
Remember: revisions are your safety net, but they work best when combined with regular backups and database maintenance. With the tips in this guide, you’ll master revisions and take full control of your WordPress content.