If AutoSave did not protect a workbook, do not start by opening every spreadsheet result you can find. First confirm whether Excel was actually saving to a cloud-backed location: AutoSave depends on the file being in OneDrive or SharePoint, the right account being signed in, and sync not being paused.
First move: Leave the workbook and sync folder alone. Check the AutoSave switch, the signed-in Office account, and cloud version history before testing recovery candidates.
The useful clues are the storage path, account, last modified time, file size, and the worksheet you remember changing. A familiar workbook name is not enough if Excel silently saved a blank or older copy.
Protect the clues before clicking
Preserve the scene: close replacement drafts, leave deleted-item storage alone, and write down the path that last held the file.
That short note keeps the search anchored. If AutoSave was off because the workbook lived only on the desktop, use AutoRecover. If it was in OneDrive or SharePoint, check the browser version history before trusting the local sync folder.
Check the places that still keep versions
Use the likely owner of the file as the first filter. The places worth checking are:
File > Info > Manage Workbook > Recover Unsaved WorkbooksFile > Info > Version Historyfor OneDrive or SharePoint workbooks- Excel AutoRecover location from
File > Options > Save - Copy workbook candidates before enabling repair or recalculation
Before opening a candidate, duplicate it and add the source to the filename. That small label prevents a confusing pile of almost-identical documents.
What to check before reopening Excel
- 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.
- Check the section you remember editing last before judging the file by its name.
- Restore only after the best copy is clear.
The holding folder is your comparison table in file form. It lets you decide with evidence instead of trusting the first readable document.
One more check is worth doing before you decide the workbook is gone: search by extension and modified time, not only by the old filename. Temporary names can be ugly, but the timestamp may point to the missing work.
The recovery path I would use here
A good Office check leaves behind a candidate copy and a source note before restore, repair, or merge.
When time is short, create a reversible pause point: current file copied, candidate saved, source written down.
A real-world recovery pass
After a crash, the first visible file is a blank replacement. Close it, preserve the recovery clues, and compare candidates outside the live folder so the blank copy does not become the new truth.
Quick triage 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 |
Keep AutoSave candidates reversible
- Typing new work into the recovered window before saving a separate copy.
- Closing the document recovery pane because the first file name looks unfamiliar.
- Searching only the original filename when the recovery file may have a temporary name.
- Opening a cloud-synced folder before checking whether the browser version has a draft.
- Deleting tiny-looking candidates before confirming whether they are pointers or partial files.
When to stop and preserve candidates
Stop the Excel AutoSave trail search if sync is still running or the app keeps reopening a blank replacement. Preserve candidates first; troubleshooting can wait.
Record the trail you already checked
Before closing tabs, write down the recovery trail. Include the expected file path, the account used, the candidate names, and whether each came from recovery folders, Trash, version history, backup, or local search.
When filenames are vague, the source is the clue. Record where each candidate came from before the folder gets closed or sync changes the view.
Before you stop searching
Choose the recovered workbook only after the edited sheet, formula areas, and modified time all make sense together.
Before you close the Excel AutoSave not working search
Check that the promising files were copied out of the live folder and opened from the copy location. Then compare the section that matters most, not just the filename.