Skip to content

WordPress.com Changes Lost After Closing a Tab: What Can Autosaves and Revisions Recover?

Blank paper sheets layered on a desk, with one sheet lifted from beneath another.

A browser-tab backup cannot be recovered after that tab has closed. WordPress.com keeps that particular backup with the open tab, so reopening the post or page in a new tab does not restore it. Earlier edits may still exist in an online autosave or a saved revision, though. Check those before rewriting anything.

Three places your edits may have existed

WordPress.com uses separate safeguards while you edit a page or post. They do not retain the same material for the same length of time.

Where the edits were stored What WordPress.com says What happens after the tab closes
Browser backup Saved locally every 15 seconds and tied to the browser tab The backup is unavailable after that tab closes
Online autosave Saved online about once per minute It may appear as a newer autosave in the editor or revision history
Saved revision Created when you manually save a draft, save, or publish It remains available in revision history when WordPress.com has stored it

The first distinction matters most. A browser backup can protect work during a temporary loss of connection or an accidental move away from the editor. When you return to the same editor tab, WordPress.com can show a message saying that the browser backup differs from the saved version. You can then open the comparison, restore the backup into the editor, and save it.

Closing that tab ends this route. Opening the same post in another tab creates a new editing session; it does not reopen the closed tab’s local backup. If the missing passage only lived there, revisions cannot promise to recover it.

Check for a newer online autosave

Open the affected page or post in the WordPress.com editor. Watch for a notice that an autosave is newer than the version currently shown. The notice links to “View the autosave,” which opens that version through the revision history.

WordPress.com separates this online autosave from the browser backup. The online version is stored on WordPress.com, while the browser backup belongs to the open tab. That distinction explains why an online autosave may still be recoverable after a tab closes.

Use the editor status at the top right as a clue for future edits. WordPress.com describes a progression from “Save Draft” to “Autosaving” and then “Saved.” A status showing “Saved” means the editor completed that save step. It does not prove that every keystroke made after the last save reached the online version.

For a published post or page, autosave does not overwrite the version visitors see. WordPress.com says the changes appear publicly only after you click Save. This gives you room to inspect a recovered autosave before changing the live page.

If WordPress.com offers the newer autosave, open it before editing the current draft. Read the title, the opening paragraph, and the missing section. A short check can prevent you from restoring an older version by mistake.

Find manually saved revisions

When no newer-autosave notice appears, open the saved revision history:

  1. Go to your site dashboard and open Pages or Posts.
  2. Open the page or post you need.
  3. Open the settings sidebar.
  4. Select the number beside “Revisions.”

If no revisions number appears, WordPress.com says there are no saved revisions to view yet. A revision is created when you manually save a draft or click Save or Publish. WordPress.com does not create a separate revision for every autosave; only the last autosave the system captured may appear.

The WordPress.com revision guide marks autosaves with an Autosave label. That label helps when the missing words may have been written shortly before the tab was closed. Saved versions and autosaves can sit beside each other in the same history, but they mean different things.

The revision screen opens in the editor. Move the slider to inspect older versions. WordPress.com highlights additions in green, deletions in red with a strike-through, and formatting changes in yellow-gold. The scrollbar also contains coloured markers, which can help locate a deleted paragraph on a long page.

A revision history is evidence of what was saved. It is not a complete recording of every moment spent typing. WordPress.org makes the same general distinction: saved drafts and published updates create revision records, while autosaves are a separate special type of revision that replaces an earlier autosave for the same user and post.

Compare before you restore

Do not press Restore as soon as you spot familiar text. First compare the candidate version with the current editor content. Look for the exact missing paragraph, heading, link, or block. Check whether the candidate also lacks changes you made later.

WordPress.com gives you two recovery choices.

Restore the whole revision

Select the version with the slider and click Restore. WordPress.com restores that version to the public site when you restore a revision. If you restore the wrong version, you can return to a newer saved revision and restore it again.

This method suits a page where an earlier version is plainly the one you want back. It is less suitable when only two sentences disappeared from an otherwise current draft.

Recover only the missing blocks

For a partial recovery, open the revision containing the text. Select the relevant block, or select adjacent blocks by clicking the first one and Shift-clicking the last. Use the block toolbar’s Copy option. Exit the revision view without restoring the full version, paste the copied blocks where they belong, then save the page or post.

This route keeps later edits that are already correct. It also gives you a chance to remove an outdated sentence before saving.

WordPress.com also provides a code-editor comparison from the menu beside Restore. It shows markup and highlights added or removed lines. Use it when a block setting changed but the visual page looks almost identical. The classic revisions screen can compare HTML versions side by side and has a “compare any two revisions” option for non-adjacent versions.

When the missing text is absent

If neither the newer autosave nor revision history contains the passage, stop expecting the revision tool to reconstruct it. The text may have remained only in the tab-specific browser backup, which WordPress.com says disappears when the tab closes.

Check the content location before assuming the page was lost. WordPress.com points to several possibilities: the item may be in Trash, saved under another content type, or located on a different site. Confirm that you opened the right site and then check whether the text was created as a page, post, or template.

The user role can also affect what you can view. WordPress.com says administrators and editors can access all available revisions; authors can view revisions for posts they authored; contributors can view revisions on their own drafts. If the revision count or a version seems missing, verify the role attached to the account before drawing a conclusion.

For future work, the practical habit is plain: save significant edits manually before closing the editor. A manual save creates a revision according to WordPress.com. Keep the tab open while checking a browser-backup notice, because that notice refers to the backup held by that tab.

Did the missing text appear before or after the editor last showed “Saved”? Does the revisions slider show an autosave label near the time you lost the changes?