You’ve rewritten a paragraph, hit update, and realised the original was better. Or your browser crashed mid-edit, and you’re staring at a blank screen. Don’t panic. You can recover a previous version of a WordPress post. WordPress quietly keeps a history of your post every time you save, and a separate safety net for unsaved work.
To recover a previous version of a WordPress Post, open the post you want to recover, find the Revisions panel in the right sidebar of the editor, click through to the revisions screen, choose the version you want, and click Restore This Revision. Then click Update to lock the change in.
What Are WordPress Revisions?
Revisions are saved snapshots of your post content. WordPress creates one every time you click Save Draft, Update, or Publish, and stores them indefinitely by default. Each revision records what changed, when it changed, and which user made the change. This means a single post can collect dozens, sometimes hundreds, of versions over its lifetime. You can roll back to any of them.
Revisions are most useful in two situations. The first is the obvious one. You’ve made a change you regret and want the old version back. The second is collaboration. If more than one person edits the same post, revisions show exactly who changed what and when, which is the difference between a productive conversation and a finger-pointing exercise.
One thing to be clear about. Revisions are not a backup. They live inside your WordPress database, on the same server as the post itself. If your database is corrupted, your site is hacked, or your hosting fails, your revisions go with everything else. For real protection, you need proper backups. Revisions are for editorial mistakes, not disasters.
How Do I Restore a Previous Version of a WordPress Post?
If you know where to look, you can get your content back in under a minute. Use revisions to bring back any saved version of a post. The detailed steps are below.
Step 1. Open the post in the editor
From your WordPress dashboard, go to Posts and click the post you want to roll back. The block editor (Gutenberg) will open.
If you’re editing a block when you open the post, the right sidebar will show block settings rather than post settings. Click Post at the top of the sidebar to switch back to post-level settings. The Revisions panel only appears here.
Step 2. Find the Revisions panel
In the right sidebar, scroll down to find the Revisions section. You’ll see a number next to it. That’s how many revisions WordPress has stored for this post.
If you don’t see Revisions at all, the post probably hasn’t been saved twice yet. WordPress needs at least two saved versions before it has anything to compare. New drafts that have only been saved once won’t show a revisions panel.
Click on the number, or on the word Revisions, to open the revision history.
Step 3. Browse the revisions
The revisions screen shows two versions of your post side by side. The current version sits on the right, and the previous version on the left. Newly added content is highlighted in green, while the deleted part is red. You can also view who made the changes and when.
Use the slider at the top of the screen to move between revisions. As you slide, the comparison updates. You’ll see the timestamp and the author for each version.
By default, WordPress shows sequential revisions, meaning the version you’ve selected and the one immediately before it. If you want to compare two non-adjacent versions, tick the Compare any two revisions box at the top. You’ll get two slider handles, one for each version, so you can compare a draft from this morning with one from last week.
Step 4. Restore the version you want
Once you’ve found the version you want, click Restore This Revision in the top right. WordPress will replace the current content with the version you selected and take you back to the editor.
Step 5. Update the post
The restoration isn’t live yet. The change has only been made in the editor. Click Update in the top right to save and publish the restored version. If the post was a draft, click Save Draft instead.
A quick note. Restoring a revision does not delete any of the other revisions. The version you just replaced becomes another entry in the revision history. So if you restore the wrong version, you can simply roll forward again.
What About Restoring Just Part of a Revision?
Sometimes you don’t want to roll the whole post back. Maybe you’ve spent an hour reworking the introduction, and you just want one paragraph from a week ago. You can copy individual blocks from a revision without replacing the entire post.
From the revisions screen, use the slider to find the version containing the content you want. Click the Exit button to return to the editor showing that revision’s content. Select the block or blocks you want to keep, click the three-dot menu in the block toolbar, and choose Copy. Then click Exit again to leave the revision view without restoring, navigate to where you want the content, and paste.
This is the cleaner option when you’re rescuing a single section rather than reverting wholesale. The rest of your current work stays intact.
How Does WordPress Autosave Work?
Autosave is a separate feature from revisions. It runs in the background while you’re editing and exists to save your unsaved work if something goes wrong, like a browser crash, a closed tab, or a power cut.
Here’s the key difference. WordPress automatically saves the current version of a post. But unlike revisions, only one autosave is kept at a time. Each new autosave replaces the previous one. So autosave is your most recent unsaved state, not a history.
If you close the browser, lose power, or your editor crashes, your last 10 seconds of work might be gone, but anything before that should still be there in the autosave.
How Do I Recover an Autosaved Draft?
Reopen the post. If WordPress detects an autosave that’s newer than the last saved version, it’ll show a notice at the top of the editor letting you know.
The notice gives you a link to view the autosaved version. Click it to open a comparison screen, much like the revisions view, showing your last saved version against the autosaved one. If the autosave has the content you want back, click Restore This Autosave. Then click Update or Publish to save it properly.
If you don’t see the notice when you reopen the post, that’s usually because there is no autosave to recover, either because nothing changed since the last save or because the autosave matches the current saved version.
A small but important detail. Autosaves expire. If you don’t reopen the post within a reasonable window after the crash, the autosave can be overwritten or cleared. If you’ve just had a crash, don’t wait. Reopen the post straight away.
Why Don’t I See Any Revisions on My Post?
A few reasons. The most common is that the post is too new. WordPress needs at least two saved versions before the revisions panel appears.
Another possibility is that your site has been configured to limit or disable revisions. Some hosts cap revisions to keep database sizes down. Others disable revisions entirely. WordPress stores an unlimited number of revisions by default. That’s great for recovery, but it can bloat your database on busy sites. If you suspect your site is limiting revisions and you’d rather it didn’t, that’s a conversation for your developer or hosting provider.
A third possibility is that a plugin has cleaned them up. Performance plugins like WP-Optimize can delete old revisions to reduce database size, sometimes automatically. Useful for site speed, less useful when you want to roll back to last Tuesday.
Comparison: Revisions vs Autosaves
People confuse the two features often, so here’s a clean side-by-side.
| Revisions | Autosave | |
|---|---|---|
| When it saves | When you click Save Draft, Update, or Publish | Every 10 seconds (block editor) or 60 seconds (classic) |
| How many are kept | Unlimited by default, configurable | One only, overwritten each time |
| What it protects against | Editorial mistakes, regretted changes | Browser crashes, closed tabs, power loss |
| How long it lasts | Indefinitely (unless cleaned up) | Until overwritten by the next autosave or save |
| Where to access it | Revisions panel in post settings | Notice at the top of the editor on reopen |
Both features run in parallel. You don’t choose between them. Together, they cover most of the “I lost my work” scenarios you’ll run into.
Should I Be Using Revisions as a Backup Strategy?
No. And it’s worth being direct about this because the question comes up often.
Revisions live in your WordPress database. If your site goes down, gets hacked, or your hosting drops, your revisions go with everything else. They’re an editorial safety net, not a disaster recovery plan.
A proper backup strategy backs up your entire site, files and database to a separate location, on a schedule. Daily for an active site. Stored off-server. Tested occasionally to make sure the restore actually works. If you’re running a business website without that in place, revisions are not going to save you on the day it matters. We’ve covered this in more detail in our WordPress security guide, which is worth a read if your site doesn’t have proper backups yet.
For most Mettro clients, backups are part of our ongoing support and maintenance work. Revisions are useful inside that, not instead of it.
Practical Tips for Working With Revisions
A few things we’ve learned from years of editing WordPress sites.
Save often, deliberately. Autosave catches your recent work, but only saved versions become revisions you can roll back to. If you’ve just finished a meaningful section, hit Save Draft. You’re creating a checkpoint you can return to.
Use revisions in collaboration. If multiple people edit the same post, get into the habit of checking revisions before assuming someone deleted something. History will tell you what happened. This is especially worth knowing if content management is shared across a team.
Don’t leave too many revisions on a busy site. If your post has hundreds of revisions and you’ve got thousands of posts, that’s database overhead. A reasonable cap, around 10 to 20, is a sensible default for most sites. Your developer can set this in wp-config.php.
Test your backup, not your revisions. Revisions are useful, but they’re not a backup. Make sure your real backup works.
Revisions are one of the small WordPress features that suddenly become very important the moment you need them. Once you know where to look, the recovery is straightforward. The bigger lesson is the one underneath. A revision can save you from a bad edit, but only a proper backup can save you from a bad day.
If you’re not sure your site is properly backed up, or you’d like someone to take WordPress maintenance off your plate entirely, we’re happy to talk.
Talk to us about WordPress maintenance.
