How to Get Back an Unsaved Word Document
Losing a Word document before saving it is one of those moments that feels catastrophic — but it doesn't have to be permanent. Microsoft Word has several built-in recovery mechanisms designed specifically for this situation, and understanding how they work gives you a real chance of getting your work back.
Why Unsaved Documents Don't Always Disappear Forever
Word doesn't just hold your text in memory while you type. In the background, it runs an AutoRecover process that periodically saves a temporary snapshot of your work — even if you've never manually hit Save. These snapshots are stored in a hidden system folder, not in your regular documents location.
There's also a separate feature called AutoSave, available in Microsoft 365 subscriptions, which continuously syncs your document to OneDrive or SharePoint in near real-time. These are two distinct features with different behaviors, and which one applies to your situation depends on your version of Word and your setup.
When Word closes unexpectedly — due to a crash, power failure, or accidental closure — it flags the AutoRecover files for the Document Recovery pane, which typically appears automatically the next time you open Word.
Method 1: Check the Document Recovery Pane
When you reopen Word after a crash or forced close, look for the Document Recovery panel on the left side of the screen. This panel lists recently auto-saved versions of files that were open when Word closed.
- Click any listed file to open and review it
- If it contains your work, immediately Save As to a permanent location
- If the pane doesn't appear, the recovery files may have already been cleaned up, or Word closed cleanly (which sometimes clears the temp files)
This is the fastest first step and works across most modern versions of Word on Windows and Mac.
Method 2: Search for AutoRecover Files Manually
If the Document Recovery pane doesn't appear, you can hunt for the temporary files yourself.
On Windows, AutoRecover files typically use the .asd extension and are stored in a path like:
C:Users[YourName]AppDataRoamingMicrosoftWord
The AppData folder is hidden by default. You'll need to enable hidden folders in File Explorer (View → Hidden Items) or paste the path directly into the address bar.
On Mac, the location is typically:
/Users/[YourName]/Library/Containers/com.microsoft.Word/Data/Library/Preferences/AutoRecovery/
The Mac Library folder is also hidden by default. You can access it by holding Option and clicking Go in Finder, then selecting Library.
Once you find .asd files, you can open them directly in Word or change the extension to .docx to access the content.
Method 3: Use "Recover Unsaved Documents" from Within Word
Word has a built-in path to unsaved drafts that doesn't require manual file hunting:
- Open Word and go to File → Info
- Look for Manage Document (Windows) or Manage Versions (older versions)
- Select Recover Unsaved Documents
This opens a file browser pointed directly at Word's unsaved drafts folder — a separate location where Word stores files that were closed without saving. Files here are typically kept for a short window (around 4 days by default) before being automatically deleted.
Method 4: Check OneDrive Version History 🔄
If you're using Microsoft 365 with AutoSave enabled and the file was linked to OneDrive or SharePoint, you may have access to version history even without a local AutoRecover file.
- Open OneDrive in a browser or File Explorer
- Right-click the file and select Version History
- Browse earlier versions and restore the one closest to your lost work
This method only applies if AutoSave was active and the file was stored in OneDrive — not a local drive. It's one of the more reliable recovery options when it's available, because versions are saved continuously rather than at set intervals.
Method 5: Look for Temporary Files
Word occasionally creates temporary files in the same folder as your document, using a ~ prefix (e.g., ~WRD0001.tmp). These aren't always recoverable as documents, but in some cases they contain readable text.
On Windows, you can search for ~*.tmp in File Explorer. On Mac, temporary files may appear in /tmp or the app's container directory. These are a last resort — their contents aren't guaranteed to be complete or in order.
What Determines Whether Recovery Is Possible
Not every unsaved document can be recovered, and the outcome varies based on several factors:
| Factor | Impact on Recovery |
|---|---|
| AutoRecover interval | Shorter intervals (default is 10 min) mean less lost work |
| How Word closed | Crash vs. clean close — clean close may delete temp files |
| Word version | Microsoft 365 has more recovery options than standalone versions |
| Storage location | OneDrive-linked files have version history; local-only files don't |
| Time elapsed | Unsaved drafts folder clears after a few days |
| OS and permissions | Hidden folder access varies by system configuration |
Adjusting AutoRecover Settings to Reduce Future Risk 💾
Once you've resolved the immediate situation, it's worth checking your AutoRecover configuration:
- Go to File → Options → Save (Windows) or Word → Preferences → Save (Mac)
- Reduce the AutoRecover interval — setting it to every 2–5 minutes captures more frequent snapshots
- Confirm the AutoRecover file location path so you know where to look if this happens again
- If using Microsoft 365, enabling AutoSave by default removes most of the risk entirely for cloud-stored files
The right interval and storage setup depend on how you work — a writer drafting long-form content in short sessions has different needs than someone editing heavily formatted documents over hours.
The Variable That Changes Everything
Word's recovery tools are genuinely capable, but what's actually recoverable in your specific situation depends on a combination of your Word version, subscription type, how the file was lost, where it was stored, and how your AutoRecover settings were configured at the time. Two people asking the same question can end up with completely different outcomes — one recovering everything, one recovering nothing — based entirely on those variables in their own setup.