You’ve probably landed here because WordPress changed on you and your stomach dropped a little. A paragraph is gone. A page looked better yesterday. Someone on the team clicked Update, and now you’re hoping WordPress revisions kept the version you actually wanted.
In a lot of ordinary editing accidents, they did.
Open the changed post or page, go to Revisions, compare the versions, and restore only when the whole older version is better. If you only need one paragraph, table, shortcode, or block back, copy that piece from the old revision instead of restoring the entire page. If the loss happened before you saved, check WordPress autosave first.
That’s the main judgment call. Revisions are excellent for post and page content. They’re not a full-site undo button. They won’t roll back a plugin update, rebuild a deleted media file, fix a theme setting, or clean up damaged database data.
Start small: check autosave, then revision history, then WordPress backups if the damage has moved beyond the editor. I wouldn’t disable revisions just because they create database rows. For most real sites, they’re too useful to throw away.
What WordPress revisions save
A WordPress revision is an older saved version of a post or page. When you save a draft, update a published post, or publish a page, WordPress can store that version under the original item so you can compare it later.
By default, revisions track the title and main editor content. They also keep author and excerpt data. In a WordPress 7.0 test site, a new draft post and draft page started with 0 revisions. After two saved updates, each showed 2 revisions. The saved records were attached to the original item, with the old title and content available for comparison. That matches the way revisions feel in the editor. They’re built for human content mistakes:
- a paragraph or page got deleted
- a draft was overwritten
- a live page was changed by mistake
- two editors made different changes and you need to compare them
- an older version simply read better
Page builders deserve extra caution here. Some store layout data in custom fields or separate structures. You may still see a revision, but that doesn’t guarantee every visual setting will return exactly as it was. Restore to a staging copy if the page matters, or at least preview carefully before you treat the job as done.
How to find revision history in WordPress
Start with the item itself. WordPress revisions live with the post or page they belong to, so opening a nearby draft or a similar landing page won’t help much.
- Go to Posts or Pages, then open the exact item you’re trying to recover. Check the title and URL first, especially if your site has translated pages, old campaign drafts, or several pages with almost the same name.
- In the block editor, look at the settings sidebar on the right. If WordPress has saved revisions, you’ll see a Revisions option with a number beside it.
- Click that number to open the revision history screen.
- Use the slider at the top to move through saved versions. WordPress marks inserted content in green, deleted content in red, and changed content in yellow.
- If you know roughly when the bad update happened, start around that timestamp. It’s much faster than reading every old version from the beginning.
WordPress 6.9 and earlier may show the classic revisions screen instead. That view compares versions side by side and can compare any two revisions with two slider handles. The exact interface can also change if you’re using the classic editor, a builder, or a plugin that changes the edit screen. Don’t worry too much about matching a screenshot perfectly. You’re looking for the same thing either way: the saved version that explains what changed.
Restore a revision without losing newer work
The tempting move is to find the missing sentence and click restore. Sometimes that’s right. Sometimes it’s how you bring back an old price, an outdated headline, or a support instruction someone already fixed. Slow down for two minutes here. It’s annoying, but it’s cheaper than fixing the same page twice.
- Check the title, URL, and publish status before touching Restore. On sites with similar landing pages, old campaign drafts, or translated versions, it’s very easy to repair the wrong item.
- Read the author and timestamp together. A version saved by the content editor probably means one thing; a version saved by an admin during a design fix may mean another.
- Compare the whole revision around the missing sentence. Look at the visible page copy, the important blocks, and any form or button that affects conversions.
- Restore only when the older version should become current. If you only need one paragraph, copy that paragraph instead.
- After restoring, return to the editor and preview the page if it’s already published.
- If the page earns money, gets legal review, or carries support instructions, copy the current version into a temporary draft or take a manual backup first.
Restoring an older revision usually doesn’t erase all newer history. It makes that older content the current version, and you can often go back into revision history and choose a newer version again if you picked the wrong one. I still wouldn’t treat that as permission to click around casually. A live page with the wrong information is still live.
Copy from a revision when a full restore is too blunt
Most recovery work isn’t a full rollback. The current page is usually mostly right. You just need the missing block, shortcode, or paragraph back. Use revision history as a reference in that case.
Find the older version that contains the missing content. Copy only the part that still belongs on the page. Paste it into the current version, then read the surrounding section out loud enough to catch the joins. Old copy often needs one sentence adjusted so it fits the page as it exists now.
Be especially careful with prices, legal copy, product promises, and support steps. Old content can look familiar enough to feel safe and still be wrong. On team-edited sites, this is the recovery method I reach for most often. It protects the good work that happened after the revision you’re borrowing from.
Autosave helps with a different kind of loss
Autosave and revisions get confused because WordPress stores autosaves as a special type of revision. In practice, they answer different moments of panic.
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.
