Something went wrong on your WordPress site. Maybe you deleted half a post, published the wrong draft, restored an older version and regretted it, or updated a plugin and watched the layout fall apart.
If you’re trying to work out how to undo changes in WordPress, don’t start by trying to restore WordPress from a backup. Start by figuring out what changed. WordPress has a few different ways back, and using the wrong one can replace good work with older work you didn’t mean to bring back.
For recent edits, use the editor’s Undo feature. To recover saved post or page content, use Revisions or Autosave. Deleted posts and pages can usually be restored from the Trash. For plugins, themes, databases, menus, or broader site changes, the safest option is a backup plugin with selective restore functionality.
Before bigger edits or updates, backup your WordPress site so you have a known-good version to return to if WordPress history can’t help.
Pick the recovery path
Most recovery problems in WordPress get worse when you treat them all the same. If the damage is small, keep the fix small. If the damage came from code, settings, or the database, don’t waste time hunting through post history.
Trash also gets its own lane. A deleted page belongs there first, before you try anything more dramatic. Use this as the quick map:
| What happened | Try this first |
|---|---|
| You just deleted text, moved a block, or changed formatting | Editor Undo |
| You saved, updated, or published the wrong post/page version | Revisions |
| The browser crashed or the tab froze before you saved | Autosave |
| You deleted a post or page | Trash |
| A plugin, theme, or WordPress update broke the site | Rollback path or backup restore |
| A menu, setting, database edit, or site-wide design change went wrong | Backup restore or careful manual repair |
The narrowest fix is usually the safest one. Get one paragraph back if one paragraph is missing. Restore one post if one post is wrong. Save the full-site restore for problems that really did reach the full site.
Undo a change you just made
If the mistake happened in the editor and you’re still in the same session, try Undo first.
For small, fresh mistakes, this is the first thing I’d try: a deleted paragraph, a block dragged into the wrong place, a heading changed by accident, a list that suddenly looks strange. WordPress isn’t restoring an old saved copy here. The editor is just walking backward through the changes it still remembers.
Stop when you can’t tell what each undo is changing. Past that point, you’re not really recovering anymore. You’re guessing.
Undo is also temporary. If you refreshed the page, closed the tab, opened the post somewhere else, or already saved over the work, don’t waste time fighting the toolbar. Move to Revisions or Autosave.
Restore a saved post or page revision
WordPress revisions are the main built-in way to revert changes in WordPress after you’ve saved a draft, updated a post, or published a page. They are saved checkpoints for one piece of content.
I checked this on WordPress 6.9.4 running PHP 8.3. Two separate saves on the same draft produced two retrievable revisions, and each one kept the content from that save. That’s the version history you’re looking for when a published page needs to go back. To restore a revision:
- Open the WordPress dashboard.
- Go to the post or page list for the content you need to fix.
- Open the item in the editor.
- Open Revisions from the editor settings. In the classic editor, look in the publish area.
- Compare the saved versions on the revision screen.
- Click Restore This Revision when you’re sure that version is the one you want.
Don’t restore only from the timestamp unless you have no other choice. The comparison view is there for a reason. It usually marks removed and added content differently, which is much more useful than trying to remember what happened at 2:14 p.m. when three people were editing the same page.
For a partial recovery, use the older revision as a reference. Copy the paragraph, heading, or block you need, then paste it into the version you want to keep. It’s slower than pressing one restore button, but it’s the move I’d make if today’s page is mostly right.
If you restored the wrong revision, don’t panic and start rebuilding from memory. Go back to Revisions. The version you replaced often remains in the history as a newer checkpoint, which means you can usually move forward again.
Recover interrupted work with Autosave
WordPress autosave is for the draft that almost got away. Maybe the browser crashed. Maybe your login expired. Maybe the Wi-Fi dropped after you rewrote the introduction but before you clicked Update. Come back to that editor screen and WordPress may show an autosave notice with an option to restore that version.
Treat that notice with a little suspicion. Autosave can be extremely useful, but I wouldn’t trust it the same way I’d trust a version you deliberately saved. What I would do:
- Reopen the same post or page.
- Look for the autosave notice near the editor.
- Compare the autosaved copy with the current content.
- Restore it only if it clearly contains the missing work.
- Check any other open editor tabs before saving again.
Multiple tabs can turn a small recovery into a confusing one. One tab may hold the newer text, while another is sitting on the older copy. Save from the wrong tab and you can accidentally keep the version you were trying to escape.
Autosave is best for interrupted writing. Once you’ve intentionally clicked Update or Publish, open the revision history first.
Restore deleted posts and pages from Trash
If a post or page disappeared because it was deleted, go to Trash before you try anything more dramatic.
In the dashboard, open the list where the item used to live: Posts for a post, Pages for a page. Open the Trash view, find the item, hover over it, and click Restore.
In testing, a draft post moved to Trash took on trash status, and changing it back restored it as a draft. In normal dashboard terms, that simply means WordPress keeps deleted posts and pages recoverable unless they have been permanently deleted or cleaned out.
After restoring, check the item status. A restored draft may still be a draft. A restored published page may need a front-end check, especially if it belonged in a menu, category, template, or page builder layout.
Trash won’t help if someone clicked Delete Permanently, if a cleanup tool removed the item, or if the content was deleted outside the normal WordPress flow. Then you’re looking for a backup, export, cached copy, or another place where the content still exists.
What to do when Revisions are missing
When the Revisions option isn’t there, it doesn’t always mean WordPress is broken. Sometimes there just isn’t a useful history yet.
A brand-new draft saved once won’t have much to compare against. Revisions also depend on the content type; a custom type may not be set up to store them. Your user role may not show you the history you need. A host, plugin, or developer may also have limited or disabled revisions to reduce database growth. Before editing files, check the simple things:
- Was this item saved more than once?
- Are you editing the right post or page?
- Does your login have permission to edit this content?
- Is this a normal WordPress post/page, or a custom content type?
- Did your host, plugin stack, or developer limit revision storage?
You may see advice to enable revisions by editing wp-config.php and setting WP_POST_REVISIONS. That can work, but it’s not a casual setting change. A typo in wp-config.php can turn one bad edit into a site that won’t load.
Take a backup before touching that file. If the edit goes wrong, you’ll want a restore point ready before you start fixing the original problem. And keep your expectations straight: enabling revisions now won’t create the revision you needed from yesterday. It only affects what WordPress saves from this point forward.
Use a backup for site-wide changes
This is where a lot of WordPress revision tutorials get too vague, right when the site already looks wrong.
Revisions belong to individual posts and pages. A plugin update or database search-and-replace sits outside that lane. So does a theme setting, template edit, or cleanup job. If the change touched more than one piece of content, the revision screen probably isn’t the tool you need.
Use a backup or rollback path when the problem came from an update or database work. A setting change or template edit may need the same treatment. So does permanently deleted content, missing page builder history, or a revision record that simply doesn’t exist.
Before restoring, check what came in after that backup time. Orders matter most on stores. On publishing and lead-generation sites, check comments and form entries first, then look for uploads or editorial changes.
Make the next recovery easier
Once the immediate problem is fixed, spend a few minutes making the next one less painful. There will be a next one. WordPress sites are edited by humans, updated by software, and occasionally rearranged under pressure.
Keep revisions enabled, but don’t let them grow forever on a busy site. A sensible revision limit gives you recent checkpoints without storing every edit for years. Deleting old revisions can clean up the database, but it also removes restore points, so do it after a backup and not during an emergency.
Before risky work, take a fresh backup and write down the time you started. Updates count. So do cleanup jobs, bulk edits, database work, and large redesigns. That timestamp is boring until you need it. Then it saves you from guessing which backup is the right one.
After any recovery, check the front end too. The editor can look fixed while a cached page, shortcode, menu item, template, or page builder section still shows the old problem.
My rule is simple: use WordPress history for one piece of content, and use a backup plan when the change may have reached the wider site.
FAQs
Can I undo changes after clicking Update or Publish?
Yes, if the change was made to a post or page and WordPress saved revisions for it. Open the item, review its Revisions, compare the saved versions, and restore the right one. Need just a paragraph? Pull that text from the older revision and leave the rest of the current page alone.
Can I bring back one section from a revision?
Not with a one-click partial restore. WordPress brings back the full saved version. For a smaller fix, use the older revision as a reference and move the missing text back by hand.
Why are WordPress revisions not showing?
There may be no older saved version yet. Revisions may also be disabled, limited by your host or site setup, unsupported for that content type, or unavailable to your current user role.
Can I undo Restore This Revision?
Usually, yes. Go back to the revision history and look for the newer version that existed before you restored the older one. If it is still there, restore that version back.
Can WordPress revisions undo plugin or theme updates?
No. Revisions mostly protect post and page content. If an update caused the problem, start with a proper rollback route. Host support or a recent backup may be faster than editing files by hand.
Conclusion
The recovery habit worth building is simple: pause, name what changed, and restore only that. Use Undo, Autosave, Revisions, or Trash when the problem is limited to content. Use a backup or roll back WordPress, a plugin, or a theme when the change reached plugins, themes, settings, files, or the database. After the fix, check the page the way a visitor would see it, because the editor can look fine while a cached page, menu, shortcode, template, or page builder section still needs attention.
Shivani enjoys crafting guides that make every aspect of using WordPress simple and easy to follow. When she's not glued to her laptop, you can find her buried in a good book or occasionally, painting.
