Have you rewritten a page, removed an important paragraph or published a version that no longer says what you intended? Before trying to recreate the text from memory, check the page history. WordPress revisions may help you recover earlier content, provided those versions have been retained. The key is to choose the right version and understand what restoring it will change.
1. WordPress revisions and autosaves: what is the difference?
Revisions are stored versions of a page or post. In a typical setup, WordPress creates a revision when you save or update content and there are relevant changes. This history lets you review what changed and return to an available earlier version.
An autosave serves a different purpose: it helps reduce the risk of losing recent work if a browser tab closes, your connection drops or something goes wrong while editing. Depending on the editor and circumstances, recovery may use data saved on the server or a local copy held in the browser.
- A revision is a reference point in your content history, useful for comparison and restoration.
- An autosave is a recovery measure for recent work, not a complete record of every change.
- A draft is a page or post status, not another name for a revision or an autosave.
None of these features means that every keystroke remains available indefinitely. WordPress configuration and plugins can affect how many revisions are stored and how long they are retained.
2. Where to find a page’s revision history
Open the page in the WordPress administration area. Look for Revisions in the document or page settings. Its location and exact label can vary with your WordPress version, interface language and editor. In the classic editor, revision history may also appear in a separate box.
- Confirm that you have opened the correct page, particularly if several pages have similar titles.
- Open the page settings and look for its revision history.
- Select a version to see a comparison with another available version.
- If you see a notice about a more recent autosave, review it before continuing to edit.
If no revisions appear, that does not necessarily mean the interface is faulty. The page may not have any stored versions yet, revisions may be restricted or disabled, or a clean-up tool may have removed them. Some visual page builders also maintain their own history, separate from standard WordPress revisions.
For general guidance about hosting services, you can browse the frequently asked questions. Whether a particular revision exists must still be checked within your own WordPress installation.
3. How to compare versions without losing context
The revisions screen displays differences between versions. You can usually move through the history with a slider or controls for the previous and next revision. If the interface offers a way to compare any two revisions, use it to examine changes between two chosen points.
Additions and deletions are highlighted. Pay attention to the difference markers rather than relying only on colour. Check the date, time and author too: these details help you identify the editing session, but they do not prove that a version is correct.
What to look for in the comparison
- The title, introduction and paragraphs containing the information you need.
- Links and any changes to their destinations.
- Lists, subheadings and the order of sections.
- Blocks, shortcodes or HTML fragments within the content.
The comparison is primarily text-based. It does not always show how the page will look on the website. A block may look different in the revision history without making the visual effect obvious, and the final appearance also depends on your theme, plugins and available resources.
4. What to check before restoring a revision
Before restoring content, keep a separate copy of anything useful in the current version. You could copy the text into a document or preserve a working copy using a method suitable for your site. This gives you a reference if you later realise that you still need a recently added paragraph.
- Check the scope of the change. Do you need the entire old version or just one sentence? For a small correction, copying the relevant passage back into the editor may be more appropriate.
- Check whether the information is still current. An old version can bring back outdated links, expired terms or incorrect contact details.
- Check elements outside the main text. The featured image, custom fields and SEO settings are not necessarily covered by standard revision history. Some may support revisions, depending on their implementation.
- Check whether someone else is editing. Coordinate with other editors to avoid overwriting recent work.
Restoring a revision of a published page can change the public content immediately. Do not assume that the action only creates a preview or will wait for another click on “Update”. If the change is sensitive, test it in a working copy or staging environment first, if one is available.
5. How to restore content and check the result
Once you have identified the right version and preserved important current content, you can proceed. Button labels vary between interfaces, but the general process is similar.
- Open the chosen revision and check its differences, date and author once more.
- Use the restore command for that version. If you are recovering an autosave, follow the specific messages shown by the editor.
- Return to the editor and review the text, block structure and any warnings.
- Open the public page and check its appearance, including on a narrow screen.
- Test relevant links and interactive elements, such as forms and buttons.
If you chose to copy only an older passage into the editor, save or update the page as appropriate for its status. If the public page appears unchanged after restoration, check the caching mechanisms used by your site and browser before repeating the process.
Do not assume that restoring a revision will also recover a file deleted from the media library. The content may still reference an image even though the file no longer exists. Similarly, a shortcode may depend on a plugin that is no longer active.
6. Why revisions do not replace a backup
Revisions track certain page and post data. A website backup has a broader purpose: depending on its scope, it may cover the database, uploaded files, themes, plugins and configuration needed to recover the site.
If the database is lost, the revisions stored within it may be lost too. A page’s history does not repair corrupted files, automatically resolve a security compromise or rebuild an entire installation. You need a separate backup strategy, with appropriately stored copies and a tested restoration procedure.
If you are reviewing your site’s infrastructure, explore the WordPress hosting services and use the contact page to ask about available options and administration responsibilities.
A practical takeaway
For safer page editing, compare before restoring, preserve useful recent information and check the public result. Use revisions to recover content, autosaves to help protect recent work and backups for broader site recovery. These tools complement one another; they are not interchangeable.
