Recover an Unsaved Word Document

You were three hours into a document, Word vanished, and the file was never named. Or worse — the Save prompt appeared and you hit Don’t Save on autopilot.

In most cases the work still exists. Word has been quietly writing recovery copies the whole time you were typing, and those copies live in folders that Word never shows you unless you ask. The catch is that they expire, and some recovery routes close the moment you restart the computer.

So before anything else: stop. Do not restart. Do not open a dozen other documents. Work through this now.

Which situation are you in?

The recovery route depends on how the document was lost. Find your row.

The three scenarios below cover the overwhelming majority.

Scenario A — Word crashed

When Word closes unexpectedly, it marks the AutoRecover file as pending recovery. Reopening Word should trigger the Document Recovery pane down the left side, listing each file it rescued.

1. Reopen Word normally. Do not open a specific document — just launch the app.
2. If the Document Recovery pane appears, click each entry to preview it.
3. When you find the right one, use Save As immediately and give it a real name in a folder you will remember.

If the pane does not appear, Word may have already dismissed it — that pane is shown once. Go to the AutoRecover folder directly:

%AppData%\Microsoft\Word

Paste that into the File Explorer address bar and press Enter. You are looking for files ending in .asd (AutoRecover snapshots) or .wbk (Word backup copies, if Always create backup copy was ever enabled).

To open one, go to File → Open → Browse in Word, navigate to that folder, and change the file-type dropdown in the bottom right from All Word Documents to All Files. Otherwise the .asd will be invisible.

On a Mac the equivalent folder is ~/Library/Containers/com.microsoft.Word/Data/Library/Preferences/AutoRecovery.

Scenario B — Word closed normally and you never saved

This is the Don’t Save case. Word still wrote a draft, and it put it somewhere different from the crash copies.

1. Open Word.
2. Go to File → Open.
3. Scroll to the very bottom of the recent documents list and click Recover Unsaved Documents.

That button opens Word’s UnsavedFiles folder:

%AppData%\Microsoft\Word\UnsavedFiles

Alternatively, if you have the document partly open or know its name, try File → Info → Manage Document → Recover Unsaved Documents — the same folder, reached a different way.

Filenames here are not helpful. They look like Document1 or a long string of characters, with the extension .asd. Sort by Date modified and work from the newest down, previewing each until you find yours.

Save it immediately once found. These are temporary files. Opening one does not make it permanent.

Files in UnsavedFiles are purged after four days. That is the single most important number in this guide.

Scenario C — the file was in OneDrive

If the document lived in OneDrive or SharePoint, you have a better option than AutoRecover, because the cloud kept its own history.

1. Open OneDrive in a browser, or find the file in File Explorer under your OneDrive folder.
2. Right-click the file and choose Version history.
3. Each saved version is listed with a timestamp. Preview them, then restore the one you want.

In Word itself the same thing lives under File → Info → Version History.

This also rescues the case where the file exists but its contents are wrong — you saved over good work. AutoRecover will not help there; version history will. We cover that case in more depth in get back an older version of a file you saved over.

One caveat worth knowing: if AutoSave was on, your mistakes were saved too, continuously. AutoSave is not an undo button. Version history is the undo button.

If none of that worked

A few lower-odds routes remain, in rough order of usefulness.

• Search the whole drive for recovery files. In File Explorer search for *.asd and then *.wbk. Word occasionally writes these next to the original document rather than in the AppData folder.
• Check the Temp folder. Open %Temp% and look for files beginning with a tilde (~WRD or ~WRL followed by numbers) with a .tmp extension. Copy one to the desktop, rename it to .docx, and try opening it. This works more often than it should.
• Check the Recycle Bin, if the file existed and was deleted rather than never saved.
• Check email and Teams. If you ever attached a draft, that copy is intact.

If the document was never saved and no .asd exists, there is genuinely nothing to recover. Data-recovery software will not help, because the content was never written to disk as a document in the first place.

What not to do

• Do not restart the PC “to see if that fixes it.” A reboot can clear the Temp folder and destroy the recoverable fragments.
• Do not create a new document with the same name and save it in the same place. You risk overwriting the very file you are trying to recover.
• Do not run a disk cleanup or a “PC optimiser”. Temporary file cleanup is exactly what those tools do, and your draft is a temporary file right now.
• Do not assume the Document Recovery pane will come back. Word shows it once per crash. If you close it without saving, go to the folder manually.
• Do not pay for recovery software before checking the folders above. The free routes find the file in most cases, and paid tools cannot recover something that was never written.

Make this a non-event next time

Three settings, two minutes, and this stops being a crisis.

Go to File → Options → Save in Word and set the following:

Then turn on AutoSave (the toggle in the top-left of the Word window) for anything stored in OneDrive. AutoSave plus version history is the only combination that protects against both crashes and bad edits.

Finally, get into the habit of pressing Ctrl+S within the first minute of starting a document. An unnamed document is the one case where Word’s recovery is weakest — once a file has a name and a location, almost every scenario above becomes recoverable.

If you are regularly short on disk space and suspect that is contributing to Office misbehaving, a full C drive is worth ruling out too — AutoRecover cannot write snapshots to a drive with no room on it.