Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsIf WordPress changes seem to have vanished, keep the editor tab that contains the work open and do not refresh or close it. In a separate tab, check for a newer autosave, then compare the post’s revisions and restore the version that contains the intended text. If the edit was saved but is not visible, verify the page, template and site environment before investigating caches. Editing the same post in two tabs, another user’s autosave, an invalid block and a site-wide template edit each require a different response.
The sequence below separates unsaved browser work from recoverable WordPress versions, explains the differences between the current WordPress 7.0-and-newer revisions screen and the classic interface in WordPress 6.9 and earlier, and gives a diagnostic path for conflicts that look like lost content.
As an Amazon Associate I earn from qualifying purchases.
Start with the safest recovery sequence
Work from the least destructive action to the most deliberate restore. The first minutes matter because unsaved text may exist only in the browser tab.
- Leave the original editor tab open. Do not reload, close, navigate away from, or overwrite the tab that shows the missing work. WordPress.com Support warns that a refresh or close can discard content held in the browser. This instruction comes from WordPress.com’s support workflow, but it is a sensible precaution for self-hosted editors as well: preserve the browser state before testing anything else. See Recover a lost or missing page or post in WordPress.
- Open the same post or page in a new tab. Use the new tab to inspect recovery options while the original remains untouched. If WordPress reports that a newer autosave exists, follow its view autosave link and inspect that copy before loading or restoring it.
- Compare revisions. Open the item’s Revisions interface, move through versions around the time the text disappeared, and inspect additions and removals. Choose the revision that matches the intended work rather than automatically choosing the newest entry.
- Check for competing editors or tabs. Ask colleagues whether someone else was editing the same item. Close duplicate editing tabs only after you have preserved any text they contain. WordPress.com Support specifically warns that two tabs can compete through autosaves, allowing one tab’s autosave to replace typing in the other.
- Restore only after comparison. A restore changes the editable post to the selected version; it does not prove that every intended keystroke was in that revision. Copy distinctive text from the current and candidate versions before clicking Restore if you may need to combine them manually.
What WordPress can and cannot recover
WordPress has two related but different recovery records: revisions and autosaves. Revisions are saved drafts and published updates that you can compare and restore. Autosaves are special revision records created while editing. The official documentation states: “Autosaves are enabled for all posts and pages but do not overwrite published content.” Read the full explanation at WordPress Revisions documentation.
| Recovery record | What it contains | Important behavior | How to use it |
|---|---|---|---|
| Revision | A saved draft or published update | Can be compared with other versions and restored | Open Revisions, inspect the diff, then restore the matching version |
| Autosave | An automatically saved editing state | Does not overwrite the published post; there can be one autosave per user for a given post | Use the newer-autosave notice and its view-autosave link, then compare before loading |
| Browser-only unsaved text | Keystrokes that have not reached WordPress | May disappear when the tab is refreshed or closed | Keep the original tab open and copy the text out before troubleshooting |
Autosaves are per user. In a multi-user site, each editor can therefore have an autosave for the same post. The newest record may belong to another person, so check the timestamp and editor identity before deciding which copy is yours. WordPress may also offer a backup after a browser crash or connection loss, but that is a recovery aid, not a guarantee that every unsaved keystroke survived.
Recover a lost post or page step by step
1. Preserve and copy what is still visible
With the original tab still open, select and copy any text, block content or settings that are not safely stored elsewhere. Paste the copy into a plain-text document or another safe editor. Do not replace the original page with a guessed revision while you are still trying to capture browser-only work.
2. Inspect the newer autosave
Open the post or page in a separate tab. A notice about a newer autosave normally offers a link to view it. Compare that autosave with the current content: confirm its time, the user who created it and the actual additions and deletions. Load it only when it contains more of the intended work than the current editor state. Because an autosave is a revision record, loading it does not publish the content by itself.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Compare the surrounding revisions
Open Revisions for the post or page. Move through entries immediately before and after the loss. A useful candidate is the one whose timestamp falls after the last successful save but before the content disappeared, whose author matches the person editing, and whose diff contains the missing paragraphs or blocks.
The comparison view highlights what was added and removed. Read the complete context around a highlighted change: a later revision may contain the missing paragraph but also remove a heading, image or block you still need. If no single revision is complete, copy the needed sections from multiple versions into a new draft instead of repeatedly restoring and undoing.
4. Restore the best match
After comparing, choose Restore for the appropriate revision. Reopen the editor and check headings, links, images, embeds and custom fields before saving. If the restored version is close but not complete, use your preserved copy to add the remaining material and save a new revision.
Use the correct Revisions interface for your WordPress version
The official Revisions article says WordPress 7.0 introduced a new revisions screen; WordPress 6.9 and earlier use the classic screen. The article was updated September 28, 2026, and includes screenshots and a video for 7.1. Labels and the position of comparison controls can therefore differ from what you see on an older installation.
WordPress 7.0 and newer
Open the item’s Revisions screen from the editor, select versions in the new comparison view and inspect the change display before restoring. If the screen shows an autosave separately from ordinary revisions, evaluate it by user and timestamp rather than assuming it is the newest complete draft.
Rank #3
WordPress 6.9 and earlier
Use the classic Revisions screen for the same process: move between versions, review the diff, and restore the selected entry. If a tutorial’s controls do not match your installation, follow the labels shown by your own editor instead of forcing the newer workflow onto an older interface.
Resolve conflicts caused by duplicate tabs or other editors
Two browser tabs editing one item
Keep one editing tab per post or page. When two tabs are open, each can send autosaves for its own editing state. WordPress.com Support documents a case in which one tab’s autosave overwrites the typing in the other. If both tabs contain unique text, copy each into a safe document, identify the most complete WordPress revision, and merge the missing passages manually.
Another user has the post open
WordPress can display a post-locked notice identifying another editor and may offer a takeover action. The developer reference documents that notice at _admin_notice_post_locked(). Treat it as coordination information, not as proof that edits will merge or that every save will be blocked. Contact the named editor, let that person save or exit, and take over only after confirming that no unsaved work remains in the other session.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Different users’ autosaves
Because WordPress keeps at most one autosave per user for a given post, the correct recovery copy may be associated with the colleague who was editing. Ask who made the last changes, then compare that user’s autosave and revisions with your own. Do not delete or overwrite a colleague’s draft while trying to recover yours.
When the Site Editor says changes are unsaved
The Site Editor can list unsaved changes and prompt you to save or review them when you leave an editing view. Read that prompt instead of navigating away. WordPress documents the Site Editor workflow at Site Editor.
Page content versus a template
Determine what you edited before judging the result. A page’s content affects that page; a header, footer or other template-part change can apply to every page using the template. If a change appears on several pages, you may have edited a site-wide template rather than the individual post. Review the listed unsaved changes and save only the items you intend to publish across the site.
Leaving the editor safely
- Review the Site Editor’s unsaved-change list.
- Open each listed item and verify whether it is page content, a template or a template part.
- Save the intended changes before leaving, or discard only the entries you have confirmed are unwanted.
- Visit an affected page and verify the result after the save completes.
Why a saved change may not appear on the front end
A successful save and a visible front-end update are separate checks. Before restoring anything, verify the basics:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Open the exact post, page or template that you edited, not a similarly titled item.
- Confirm that the browser is viewing the same site environment where you saved: production, staging or a local copy can contain different content.
- Check whether the edit was to a template or template part that controls the page you are viewing.
- Test in a private window or a different browser session to rule out a stale browser cache.
- Consider server-side caching and caching plugins only after confirming the edit and location. WordPress’s troubleshooting FAQ lists browser and server caches, plugin caches and editing the wrong filesystem location as possible causes; it does not establish that caching is the cause in every case. See FAQ: I make changes and nothing happens.
Do not overwrite a good saved revision merely because an old cached page is still displayed. First establish that the editor shows the new content, then clear or bypass the relevant cache according to your site’s configuration and check again.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix an invalid or unexpected block without losing content
If the editor reports invalid or unexpected block content, preserve the current content before attempting repair. Copy the block’s visible text and, where practical, its code or markup into a safe document. Then use the recovery action that matches the problem:
- Attempt Block Recovery: let WordPress reconstruct the block when the stored content can be parsed.
- Resolve: review the differences WordPress identifies and choose the version that keeps the intended attributes and text.
- Convert to HTML: retain the markup when the structured block cannot be repaired but the HTML is usable.
- Convert to a Classic block: preserve editable content in a less structured form when block recovery is unsuitable.
These options are not useful in every case, including invalid syntax or code placed in a block that does not support it. WordPress lists theme or plugin interference as one possible source of invalid content, not as a diagnosis you can make from the error alone. The official troubleshooting steps are at Block Error: Unexpected or Invalid Content.
Choose the right recovery action
| Symptom | First action | Evidence to compare | Safe next step |
|---|---|---|---|
| The open tab still shows missing text | Do not refresh or close it | Visible browser-only text versus stored revisions | Copy the text, then inspect recovery in a new tab |
| A newer autosave notice appears | View the autosave | Timestamp, user and added or removed content | Load it only if it is the more complete working copy |
| The post reverted after another tab was used | Stop editing in duplicate tabs | Autosaves and revisions from each user or session | Merge unique text manually after preserving both copies |
| The post is locked | Contact the named editor | Who is editing and whether that session has unsaved work | Take over only after coordination |
| The editor reports invalid block content | Preserve the block first | Block structure, markup and the visible text | Try recovery, Resolve, HTML or Classic conversion as appropriate |
| The editor shows the save but the site does not | Verify item and environment | Editor view, template scope and cache layers | Test without stale caches before changing content again |
Prevent future editing conflicts
Adopt a one-tab rule
Use one editor tab for each post, page or template. If you need a reference, open it in a separate browser window without loading the same item in edit mode. Close old editor tabs at the end of a session.
Coordinate handoffs
Tell other editors when you begin and finish a post. A lock notice helps identify the active editor, but it is not a collaborative merge system. A short handoff that names the item and confirms the save is safer than assuming WordPress will reconcile simultaneous typing.
Save deliberately in the Site Editor
Before leaving, inspect the unsaved-change prompt. Pay special attention to headers, footers and template parts because one save can affect every page that uses them.
Verify the result in context
After saving, open the intended front-end URL and check the relevant template, not just the editor canvas. If the change is missing, diagnose the location and cache before editing again; repeated edits can create confusing extra revisions.
Keep a local fallback for substantial work
For a long article, copy the draft to a plain-text or document file at meaningful milestones. This does not replace WordPress autosaves or revisions, but it gives you a source when a browser crash, connection loss or invalid block leaves no complete revision.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
A practical decision path
- Is the original tab still open? Keep it open and copy its visible work. If it is gone, proceed to stored autosaves and revisions.
- Does WordPress offer a newer autosave? View it, check its user and timestamp, and compare the diff.
- Is there a suitable revision? Restore the best match only after reviewing additions and removals.
- Was another tab or editor involved? Preserve each copy, coordinate with the other editor and merge unique content manually.
- Was the edit made in the Site Editor? Check unsaved changes and determine whether a template or template part was changed.
- Is the saved editor content correct but the front end stale? Verify the site and item, then test browser, server and plugin caches.
- Is a block invalid? Preserve it, then try Attempt Block Recovery, Resolve, HTML or Classic conversion based on whether structured block data can be retained.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
