When you are looking for an unsaved Word document on Mac, the first clue is usually not the Recent list. It is the gap between the last edit, the app's recovery folder, and any cloud draft that existed before the next save. Work from copies so a promising document can be tested without changing the source.
First move: Create a separate recovery-candidates folder and copy every plausible file there before opening, repairing, syncing, or restoring it.
Freeze the recovery scene first
Make the workspace quiet. Do not keep editing a replacement with the same name. Do not empty Trash or Recycle Bin. Do not run cleanup utilities. Do not restore a folder backup over the live folder. If the file is important for work, legal records, school, or a client, take screenshots of error messages and write down the last device, app, folder, and approximate edit time.
That record is not busywork. It tells you which system probably has the best evidence. A crash points toward AutoRecover and temporary files. A cloud delete points toward web recycle bins. An overwrite points toward version history. A corrupted file points toward copy-first repair.
Check the places that still keep versions
Start with the place that could still have a newer copy, then move outward. For this case, check:
File > Info > Manage Document > Recover Unsaved Documents%AppData%\Microsoft\Word\and theUnsavedFilesfolder for.asdor.wbkfilesFile > Info > Version Historywhen the file was saved to OneDrive or SharePoint- Recycle Bin, then File History or Time Machine if a saved copy was deleted
When a result looks promising, copy it into the holding folder before double-clicking. Rename the copy with its source, such as from-autorecover, from-version-history, from-trash, or from-file-history. Keep the original candidate where it was found until the recovery is complete.
Label each recovery candidate
- Sort candidates by modified time, then by file size.
- Copy each likely file into the holding folder.
- Open copies read-only when the app allows it.
- Compare the first page, the last edited section, and any formulas, comments, or images that matter.
- Restore only after the best copy is clear.
The point is to avoid turning one loss into two. If a candidate opens badly, the untouched source still exists. If version history has two useful branches, both can be downloaded and compared. If a cloud service is still syncing, you have not forced the wrong version to spread.
Where this recovery tends to succeed
For macOS, the safest order is evidence first, restore second. In a desktop Office file, that means checking the app recovery picker and AutoRecover location before saving a new version. In a cloud file, it means opening the browser version of the service and checking activity, Trash, and version history before trusting the local sync folder. In a damaged file, it means preserving the original before repair.
If you only have five minutes, do this: copy the current file or folder, check the web version of the service, and download the best candidate separately. That gives you a reversible checkpoint even if you need help later.
A realistic recovery sequence
A laptop restarts after a long editing session. The user opens macOS, sees no useful Recent entry, and almost starts a new document with the same name. The safer sequence is to close the replacement, make a recovery-candidates folder, check the recovery picker, then copy any .asd, .tmp, or cloud draft before opening it. If one candidate has the last paragraph and another has the formatting, both copies are preserved for comparison.
Recovery likelihood table
| What you see | Best first check | Risk to avoid |
|---|---|---|
| The app crashed before a save | AutoRecover, unsaved files, and temp locations | Reopening and saving a blank replacement |
| The file was deleted from a synced folder | Web Trash or recycle bin for the cloud service | Letting the synced deletion become the only story |
| The content is older than expected | Version history and downloaded copies | Restoring over the live file before comparing |
| The file opens with errors | Duplicate first, repair only the duplicate | Damaging the only original with repeated repair attempts |
| Search finds many odd names | Sort by date, extension, and size | Opening every result and accidentally saving changes |
Clicks to avoid while evidence exists
- Restoring the first visible result because the filename looks right.
- Trusting Recent files instead of checking the actual storage location.
- Opening candidates directly from a temp folder and then saving over them.
- Running third-party recovery tools before copying cloud and backup evidence.
- Waiting until cloud Trash, version history, or backup retention windows expire.
Signs you should pause
Stop if the missing document is legally important, business-critical, the only copy of a major project, or stored on a drive that is making noise or disconnecting. Also stop if every repair attempt makes the file smaller or less readable. At that point, a clean handoff with copied candidates and notes is more valuable than another random tool.
Record the trail you already checked
Leave the session with notes another person could understand. Write down the original file name, the folder where it should have been, the device used, the cloud service involved, the last known edit time, and every candidate you copied. Include the source of each candidate: AutoRecover, version history, Trash, backup, local search, or a colleague's copy.
This record helps even when the recovery works. If the restored document later turns out to be incomplete, you can return to the candidate list instead of starting over. It also makes a professional handoff cleaner because the next person can see what was already checked and which version looked strongest.
Sources and further reading
- Microsoft Support: recover Office files
- Microsoft Support: view previous versions of Office files
- Google Drive Help: find or recover a file
The safe restore principle
Recover first by preserving choices. A copied candidate, a timestamp, and a clear source label give you room to compare; a rushed restore takes that room away.