WordPress Revisions vs Autosaves: Recover the Right Text

- What is the difference between revisions and autosaves?
- Which record should you inspect?
- Where do you open the comparison?
- How can you recover a paragraph without reverting everything?
- Is Undo the same as restoring a revision?
- Why might the expected revision be unavailable?
- What should the final review record say?
- Sources
What is the difference between revisions and autosaves?
WordPress revisions record saved drafts and published updates; autosaves preserve recent work without providing a history of every keystroke. Choose the recovery point by its contents, not merely its age. Before restoring anything, preserve the current text and confirm the effect on publication: WordPress.com warns that Restore applies the selected revision to the public site.
This is a documentation-based guide for editors recovering text from a page or post. WordPress.com instructions are identified separately. It does not cover database restoration or promise that a particular site's history contains the missing passage.
Which record should you inspect?
The WordPress revisions documentation says there is at most one autosave per user for a given post; later autosaves replace earlier ones. Autosaves do not overwrite published content. That makes them different from a collection of deliberately saved versions.
| Record | What it gives you | Editorial question |
|---|---|---|
| Saved revision | A record of a saved draft or published update | Does this contain the approved wording? |
| Autosave | Recent automatically preserved work | Does this contain the unfinished passage? |
| Your recovery note | An account of the intended correction | What must stay unchanged? |
An autosave can be useful without being the version you want to publish. Likewise, an older saved version may contain the missing paragraph alongside wording that has since been corrected. Read both sides of the comparison.
Where do you open the comparison?
Open settings, choose Page or Post, then the revisions count. WordPress documents a new screen from 7.0; 6.9 and earlier use classic comparisons. Follow the instructions for your installed version.
Treat inspection and restoration as separate decisions. Our recommendation is to write down the page title, public URL, version being inspected and passage sought before changing anything. If you cannot identify the site or page confidently, stop and ask its editor or administrator.
How can you recover a paragraph without reverting everything?
Restoration can replace current content. WordPress.com's revision guide says its Restore button applies the chosen revision to the public site. Use the site's approval process before that action.
For partial recovery on WordPress.com, its documented method is to select and copy the desired blocks from a revision, exit without restoring, then paste them into the editor. Review the resulting page before saving changes to published content. Do not assume an interface on another host behaves identically.
Consider this original fictional example. A workshop announcement once contained an accessibility contact paragraph. A later edit corrected its start time but accidentally removed that paragraph. The editor wants the contact information back while keeping the corrected time.
| Part of the announcement | Intended decision | Check before approval |
|---|---|---|
| Accessibility contact paragraph | Recover the missing text | Confirm the contact details remain current |
| Start time | Keep the corrected version | Compare against the approved event information |
| Remaining announcement | Preserve current wording | Check that no unrelated sentence changed |
The task is not “make the page older.” It is “recover this passage while retaining these corrections.” That sentence gives a reviewer something concrete to approve. It also explains why a whole-version restoration needs more review than finding one familiar paragraph.
Is Undo the same as restoring a revision?
The block editor documentation describes Undo and Redo as reversing an action and reapplying an undone action. It separately describes saving a draft without publishing. These controls serve different editing decisions; do not treat their labels as interchangeable.
For an accidental change you are still reviewing, identify the action you want reversed before using Undo. For a passage from another saved version, inspect the version history. In either case, compare the result with your intended correction rather than assuming that a successful button click proves the page is right.
Why might the expected revision be unavailable?
WordPress's revision-retention reference documents a configurable retention limit and filters that can change it. A site's available history therefore needs checking; do not promise that every past save remains recoverable. Ask the administrator about the site's actual settings. Changing configuration is not an editorial recovery step.
For WordPress.com, the missing-content guide recommends checking whether content was saved as the other content type, under another author, or on another site. Record what you checked before concluding that something was deleted. Keep private drafts within approved access and storage arrangements.
What should the final review record say?
Our suggested recovery note names the missing passage, the version used, the newer corrections retained, the reviewer and the outcome. Write “not checked” for any unresolved item. A screenshot of a version list is evidence of available history, not evidence that the final wording is accurate.
Run the relevant pre-publish checks on the combined result. After an authorized publication change, verify the public page and record the check time with its time zone. If another editor is working on the same page, agree who owns the change before proceeding.
Finally, keep this separate from whole-site recovery. The WordPress backup handbook says a typical site's full restoration needs both files and database. Revision history is not that package. The export-versus-backup comparison covers the distinction; the migration inventory covers wider changes. Database restoration and deletion belong to authorized administrators using a tested recovery plan.