iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If WordPress edits disappear, do not refresh or close the tab that contains them. Keep that browser state intact, then check for a newer autosave, compare the post’s revisions, and restore only the version that contains the intended work. If the edit was saved but is not visible, verify the page, site environment, and caches instead of immediately editing again. The workflow below covers the recovery paths for the block editor, Site Editor, WordPress.com, and self-hosted WordPress.
First response: protect work that may still be in the browser
The most valuable copy of your writing may be the one currently held in the editor tab. WordPress.com Support cautions that reloading or closing that tab can discard work that has not reached WordPress. This guidance is written for WordPress.com, but the same precaution is sensible on self-hosted sites.
- Leave the original editor tab open. Do not refresh, close it, navigate away, or use the browser’s back button while you investigate.
- Record what happened. Note the post or page title, the approximate time the text disappeared, your WordPress username, and whether another person was editing the same item.
- Open a separate tab for recovery checks. Use the new tab to open the same post or page and inspect autosaves and revisions. This keeps the tab that might still contain unsaved text untouched.
- Copy visible text before experimenting. If the original tab still shows any of the missing work, select and copy it into a plain-text file or another safe document. Do not overwrite that copy with a restored revision.
WordPress.com’s recovery instructions are at Recover a lost or missing page or post in WordPress. The page is specific to WordPress.com, so self-hosted administrators should use it for the browser-state precautions while following their own dashboard’s labels for the remaining steps.
Recommended Free Tools
Recover a newer autosave
Autosaves are special revision records. WordPress documentation states that they are enabled for posts and pages, do not overwrite published content, and are kept separately from the published version. There can be one autosave per user for a particular post; when several users edit the same post, each user can have an autosave. Consequently, the newest copy may belong to the person who was typing when the content vanished.
- In the separate tab, open the affected post or page in the editor.
- Look for a notice saying that a newer autosave is available.
- Choose the notice’s link to view the autosave. Read the proposed content carefully rather than loading it automatically.
- Compare the autosave with the text you copied from the original tab and with the point at which the loss occurred.
- Load or restore the autosave only when it contains the material you actually need. Save the post after checking the result.
An autosave is a recovery aid, not a recording of every keystroke. A browser crash, a dropped connection, or a tab that never completed an autosave can leave gaps. WordPress may offer a backup after a crash or connection loss, but it cannot guarantee recovery of all unsaved browser state.
For the underlying behavior and the official comparison workflow, see WordPress Revisions documentation.
Compare revisions before restoring anything
Revisions contain saved drafts and published updates, allowing you to inspect what changed and return to an earlier version. Use the Revisions interface on the post or page and compare versions around the moment the content disappeared.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors- Open the post or page and locate its Revisions link or panel in the editor.
- Move through the available versions in time order. Identify the revision immediately before the loss and any later revision created by you or another editor.
- Inspect the difference view. Additions and removals are highlighted so you can tell whether a revision contains a complete draft, only a paragraph, or an accidental overwrite.
- Check the timestamp and the user associated with the revision or autosave. A later timestamp is not proof that the version is the right one.
- When the correct version is clear, use Restore, then review the entire post and save it as a draft or publish it according to your normal workflow.
Do not assume that the newest revision is the best revision. A competing tab can create a newer save containing less text, and another author’s autosave may be the copy you need. Restoring changes the editable post to the selected version; it does not erase the revision history, so you can return to the comparison screen if you selected the wrong copy.
Which revisions screen will you see?
The interface depends on the WordPress version. The official documentation says WordPress 7.0 introduced a new revisions screen, while WordPress 6.9 and earlier use the classic screen. The documentation page was updated on September 28, 2026 and includes material for the 7.1 interface. If the controls or screenshots do not match your dashboard, confirm the version shown under Dashboard → Updates and follow the screen your installation provides rather than looking for a missing button.
| Version context | What to expect | Recovery decision |
|---|---|---|
| WordPress 7.0 and later | Newer revisions interface documented by WordPress | Use the version comparison and restore controls shown in that interface |
| WordPress 6.9 and earlier | Classic revisions screen | Use the classic comparison controls and verify the selected timestamp before restoring |
| Multiple editors | Each user can have an autosave for the same post | Check the user identity as well as the timestamp |
Why two tabs can overwrite each other’s work
Two editor tabs for the same post are a common source of apparent data loss. WordPress.com Support explains that one tab’s autosave can overwrite the other tab’s typing. For example, you might type a long section in Tab A, switch to an older copy in Tab B, and allow Tab B to autosave. The later autosave can then represent Tab B’s shorter content rather than the text still visible in Tab A.
Use one editing tab per post or page. If you already have duplicates open:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Stop typing in every tab except the one containing the most complete work.
- Copy the complete text to a safe document.
- Close or leave the other tabs untouched until you have inspected revisions and autosaves.
- Save from the chosen tab only after confirming that its content is complete.
This is different from collaborative real-time editing. WordPress can display a post-lock notice identifying another editor and may offer a takeover action, but the official developer reference documents the notice itself, not a universal merge system or guaranteed save blocking. Treat a lock as a coordination signal, not as proof that WordPress will reconcile two drafts.
The implementation reference for the lock notice is _admin_notice_post_locked().
Coordinate multi-user editing safely
Before taking over a locked post, contact the person named in the notice. Ask whether their unsaved work is still open and give them time to save or copy it. A practical handoff has three parts:
- Identify the editing window: agree on who is editing and when the handoff occurs.
- Save a checkpoint: the outgoing editor saves a draft and records what remains unfinished.
- Confirm the new owner: the incoming editor reloads only after the first editor confirms that the browser tab is safe to close.
For a post with substantial changes, retain a separate text copy during the handoff. Built-in revisions help recover saved states, but they are not a substitute for coordination when two people are typing at the same time.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCheck unsaved changes in the Site Editor
The Site Editor has a different failure pattern because you may be editing a template or template part rather than the content of one page. WordPress says the Site Editor prompts you to save or review unsaved changes when you leave an editing view.
Rank #3
- When leaving the Site Editor, read the save prompt instead of dismissing it.
- Review the list of changed items and save the changes you intend to keep.
- Identify whether the item is page content, a template, or a template part such as a header or footer.
- After saving, open a page that uses the template and verify the result.
A header or footer template can apply to every page that uses it. If a change appears to have affected many pages, it may not be lost content at all; it may be a site-wide template edit. Conversely, changing a page’s content will not necessarily change the template used around it. Separate those two scopes before attempting recovery.
WordPress documents the save prompt and template scope in the Site Editor documentation.
When the edit saved but is not visible
“Nothing changed” does not always mean that WordPress lost the edit. Diagnose the location and viewing path before restoring or retyping anything.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Verify the object and environment
- Confirm that you edited the intended post, page, template, or template part, not a similarly named item.
- Check the status: draft, pending review, scheduled, private, or published.
- Open the exact front-end URL generated by that item and confirm that you are logged into the expected site.
- If you maintain staging and production, verify which environment received the save.
- For file or design changes, confirm that the correct filesystem location was edited. WordPress lists an incorrect location as one possible reason a change appears ineffective.
Test caches without guessing
Browser cache, server-side cache, and caching plugins can serve an older copy of a page. First check the page in a private window or a second browser. Then use the site’s documented cache-clearing control, if available, and check again. If the new version appears only after a cache purge, record which cache layer was involved so future publishing checks include it. Do not declare caching the cause until the edit is present in the editor and the page changes after the cache is bypassed or cleared.
WordPress’s troubleshooting FAQ lists browser and server/plugin caches, along with editing the wrong location, among the possible causes: FAQ: I make changes and nothing happens.
Repair an invalid or unexpected block
If the editor shows “This block contains unexpected or invalid content,” preserve the current content before clicking a repair option. Copy the block’s text and, when practical, the surrounding post into a separate document.
Attempt Block Recovery
Choose Attempt Block Recovery when you want WordPress to rebuild the block from the markup it can still interpret. Review the result carefully; recovery may change formatting or remove attributes that the block no longer recognizes.
Free tools Windows power users keep installed
One-click scans. No signup required.
Resolve the block differences
Use Resolve when WordPress presents a comparison between the saved content and the block’s expected structure. Keep only the version that contains the intended text and settings.
Convert to HTML or a Classic block
Conversion can preserve readable content when maintaining the structured block is less important than keeping the text editable. Converting may remove block-specific controls, responsive settings, or other structured data, so use it only after saving a copy of the original.
Invalid syntax, code placed in a block that does not support it, and theme or plugin interference are possible causes. The recovery choices are not appropriate for every case. WordPress’s documented options and limitations are described in Block Error: Unexpected or Invalid Content.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A decision table for common symptoms
| Symptom | Most useful first check | Next action |
|---|---|---|
| The tab still shows the missing text | Do not refresh or close it | Copy the text, then inspect autosaves and revisions in another tab |
| A newer autosave notice appears | Open the autosave and compare its timestamp, user, and contents | Load it only after confirming it is the desired copy |
| The post has several competing revisions | Compare additions and removals around the loss time | Restore the complete version, not automatically the newest one |
| A lock notice names another editor | Contact that editor | Wait for a save-and-handoff checkpoint before taking over |
| Site Editor changes affect multiple pages | Check whether a template or template part was edited | Review and save the intended site-wide change |
| The editor contains the change but the front end does not | Verify URL, environment, status, and caches | Test privately, then clear the identified cache layer |
| A block is marked invalid | Copy the block and surrounding content | Try recovery, resolve differences, or convert with the trade-offs understood |
Prevent future conflicts and apparent loss
Adopt a one-tab rule
Keep one editor tab open for each post or page. Bookmarking the edit URL is safer than opening multiple copies from browser history. Close stale tabs before beginning a new session.
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 →Use explicit handoffs
In a team, assign one editor at a time. Save a draft at the handoff, tell the next person what changed, and wait for confirmation before taking over a lock. Do not rely on a lock notice to merge simultaneous work.
Make meaningful checkpoints
Save after completing a section, before changing complex blocks, and before switching between the visual editor and code views. A saved checkpoint gives Revisions a useful recovery point without pretending that every keystroke is preserved.
Review before leaving the Site Editor
Read the unsaved-change list each time you leave. Confirm whether a change is local page content or a template/template-part change before saving.
Separate recovery from backup
Autosaves and revisions recover saved editor states. They do not replace a full site backup, and they cannot reliably recover text that never reached WordPress. Maintain a backup process appropriate to your hosting arrangement, but use the built-in revision workflow first when the immediate problem is an editing conflict or a missing draft.
Keep a publishing verification step
After saving or publishing, open the intended URL in a private window, check the status and environment, and account for known cache layers. This catches “saved but not visible” problems before another editor starts reworking the same content.
When recovery is not possible
If the original tab was closed or refreshed before any autosave or revision was created, WordPress may have no copy of the missing browser state. Search the post’s revisions, drafts, trash, and other authors’ work, but distinguish an available saved version from text that existed only locally in the closed tab. If no saved copy contains the text, recovery tools cannot reconstruct it from WordPress alone.
When you do recover a partial version, preserve it, rebuild the missing section, and save a new checkpoint before making further structural or multi-user changes. That approach prevents a second overwrite while you finish the repair.
Quick Recap
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.
