Excel crashed mid-edit. Power blinked at the wrong moment. You clicked Don't Save by reflex without thinking. Whatever broke the chain — the panic afterwards is the same. You lost work and you need it back fast.

Maybe an hour of forecasting. Maybe a week of reconciliation work. And every minute you spend Googling generic advice is another minute the file might overwrite itself or expire from the temp cache. Here is the short version first.

Most lost Excel files are recoverable through one of three built-in features. Not all of them, but most. The difference between the two outcomes is what you do in the first five minutes after you realise something went wrong.

Excel document recovery is a built-in workflow inside Microsoft 365, Excel 2021, Excel 2019, and Excel for the web. It pulls from three different sources depending on what triggered the loss in the first place.

AutoRecover snapshots stored on your local disk. AutoSave cloud versions held on OneDrive or SharePoint. And the temp-file cache that Excel writes silently in the background. Each one fires at a different trigger condition.

Each one stores files in a different folder structure. And each one expires on its own independent clock. Miss the clock and you lose the file forever, with no support ticket that will bring it back from Microsoft.

I'll walk through the five most common loss scenarios in order of frequency. Excel crashed before you had a chance to save. You closed the file without saving by accident. The file opened blank, garbled, or threw a strange error.

You overwrote a good copy with a bad one and saved it. The file vanished from the folder entirely and is nowhere to be found. For each scenario, there is a recovery path that works reliably and a path that wastes precious time.

Pick the right path on the first try and you keep your data largely intact. Pick the wrong one and you may corrupt the only copy that still holds your work. The five scenarios share some tools but each has a specific fastest route.

AutoRecover is the feature you want when Excel crashes unexpectedly. It silently saves a copy of your workbook every 10 minutes by default. You can drop that interval to one minute if you want stronger protection.

Most heavy Excel users do drop it. When Excel relaunches after a crash, a Document Recovery pane appears on the left side of the screen. It lists all unsaved versions in the order Excel found them in the temp cache folder.

The top entry is almost always the freshest version, the one you actually want to recover. Click it once to open it in read-only mode. Save it under a new filename. Done with that part of the recovery process.

Trouble is, the Document Recovery pane only appears once per session. Close it, dismiss it, click the wrong file in the list — and Excel assumes you don't need the recovery anymore. The pane will not come back automatically.

The temp files themselves still exist for a while on disk, but you'll have to dig them up by hand from the AppData folder. The first lesson of Excel document recovery — treat that pane like a fire alarm. Act on it now. Don't snooze it.

Closed without saving is the second scenario, and it happens to everyone eventually. You hit the X button without thinking. You clicked Don't Save because you thought you were on a different unrelated file. Or your toddler did.

Either way — the file is gone from view in your folders, but not gone from disk yet. Open Excel without a file. Click File menu. Click Open. Click Recent on the left. Scroll all the way to the bottom of the recent list.

There's a button labelled Recover Unsaved Workbooks at the very bottom. Click it. A File Explorer folder pops open. Every unsaved file Excel ever held onto sits inside that folder, named with random alphanumeric characters.

Open them one at a time. The freshest one — sort the folder by Date Modified in descending order — is usually the file you want back. Use Save As immediately to give it a real name and store it somewhere you'll find again later.

Excel keeps these temp files for only four days by default. After day four, the temp files are scrubbed during routine Windows or macOS cleanup. So if you lost something on a Friday and only remember to look on Wednesday, you might already be too late.

Scenario three is corruption — the file opens but something is clearly wrong with it. Cells are full of #NAME or #REF errors that weren't there yesterday. Formulas show as plain text instead of calculating. The workbook freezes on open and never finishes loading.

Could be corruption from a bad save during a crash. Could be a damaged add-in trying to load broken DLLs. Excel has a hidden Open and Repair option that fixes a surprising share of these problems without any third-party software involvement.

From the File then Open dialog, pick the broken file from your folder list. Don't double-click on it — click once to select it instead. Then look closely at the Open button in the lower-right corner. There's a tiny dropdown arrow next to it most people never notice.

Click the arrow. Pick Open and Repair from the menu that drops down. Excel scrubs through the file looking for recoverable structure. Two options appear in the dialog box. Repair tries to recover as much as possible while keeping formulas intact and functional.

Extract Data pulls values and any salvageable formulas — useful when Repair fails completely. Try Repair first as the gentler option. If you get less than 80 percent of your data back from Repair, run the process again and pick Extract Data instead.

You'll lose some formula logic with Extract Data but you'll keep numbers and rebuilt Excel formulas, dates, and text values intact and rebuilt Excel formulas where possible. That's still a meaningful win compared to the alternative of starting from scratch with no source data.

Scenario four is the overwrite — overwrote a good file with a bad save. This one stings the most because the file is technically fine, just wrong. You opened last week's report, made changes, saved, then realised you wanted last week's version after all.

If the file lives on OneDrive, SharePoint, or any synced cloud drive, version history is your rescue and it works beautifully. Right-click the file in File Explorer or on the web through the browser. Pick Version History from the context menu that appears.

A list of every save going back at least 30 days appears in a panel. Pick the version from before your bad save. Click Restore. The current bad version becomes a backup automatically. The older good version becomes current and the file is fixed.

If the file isn't stored on the cloud anywhere, you're stuck with Windows File History or macOS Time Machine — assuming you turned either of them on long before the disaster happened. Most home and small-business users haven't done that setup work yet.

There's also the Previous Versions tab on a Windows file's properties dialog, which pulls from System Restore points if any exist. Worth checking once. Often completely empty unless your administrator configured restore points to include file data, which is rare.

Scenario five — file vanished entirely from view. Not in the folder where you saved it. Not in the Excel recent list. Not on the desktop where you swear you dragged it last week. Just gone.

Three places to check before you panic and start scanning disks. Recycle Bin on Windows first, since accidental deletion is the most common cause. Trash on macOS for Mac users. OneDrive Recycle Bin if the file ever lived in a synced folder.

OneDrive has its own bin, separate from Windows. Files sit there for 30 days from the deletion date. After 30 days expire, OneDrive moves them to a second-stage recycle bin that lasts another 60 days before permanent erasure.

Even files you deleted three months ago might still be recoverable through that two-stage system. Beyond those built-in options, you'd need third-party file-recovery software like Recuva, Disk Drill, or EaseUS Data Recovery Wizard.

They scan raw disk sectors for deleted file fragments below the filesystem layer. They work surprisingly often on traditional spinning hard drives. They work much less often on SSDs because of how TRIM commands wipe deleted data the moment the OS marks it free.

Run the scan from a different drive than the one you lost the file from. Installing recovery software on the same drive you're trying to recover from will overwrite the very data sectors you want back. People do this all the time and destroy their chances.

Now to prevention. Once you've fixed today's crisis, the only sensible next step is making sure it doesn't happen again next month. Open Excel. Click File. Click Options. Click the Save tab on the left.

Three settings deserve your full attention here. AutoRecover save interval — drop it to one minute if your workbooks are small, five minutes if they're heavy with formulas. The default 10 minutes is too long for anyone doing real work.

Keep the last AutoRecovered version if I close without saving — leave that box ticked. AutoSave OneDrive and SharePoint files by default — turn it on. That last one is the single biggest upgrade you can make to your Excel spreadsheet habits to your Excel spreadsheet habits.

AutoSave only fires when the file lives on a cloud drive. Save your file to OneDrive, SharePoint, or a OneDrive for Business folder, and the moment you enable AutoSave at the top-left toggle, every keystroke is captured into the cloud as you work.

Version history records each save automatically without any user effort. You can go back to any minute of any day for the last 30 days at minimum. Crash, power outage, fat-finger overwrite — none of it loses data when AutoSave is on.

Local files don't get AutoSave, which is the strong protection. They get AutoRecover instead, which is weaker by design. AutoRecover snapshots only fire if Excel is open and idle long enough between saves to write a backup.

Crash mid-keystroke during heavy editing and you might lose the last nine minutes of work. Crash during a long calculation and you might lose everything you typed since you opened the file. There's nothing AutoRecover can do about it.

The fix isn't to obsess over AutoRecover settings. It's to move your important files to OneDrive and let the cloud do the heavy lifting. The shift takes ten seconds and prevents nearly every data-loss scenario you'll ever face.

For users on Excel for the web — the browser version of Excel — every change saves automatically as you type. There is no Save button on the toolbar because there is no manual save process at all. The cloud handles it.

Close the tab, reopen tomorrow, your work is exactly where you left it. Version history goes back at least 30 days for personal accounts. Corruption is rare because the file lives on Microsoft's servers, not your potentially failing local hard drive.

If your workflow tolerates browser-based Excel, the document recovery problem mostly disappears. Worth thinking about if you've been burned by lost files before. The browser version lacks some advanced features but covers 90 percent of typical spreadsheet work.

Two final tips that save people hours when recovery does happen. First — when you open a recovered file, don't trust it blindly without checking. Compare formula totals to a known good number you remember from before the crash.

Check the most recent sheet you were editing for completeness. Make sure pivot tables refresh without errors when you press F5. Recovery isn't always lossless. The Repair option does its best but can silently drop entire ranges.

Sometimes Excel reconstructs a workbook that opens cleanly but has subtle data corruption on one sheet you don't immediately check. You want to catch that the same day, before you build a week of new work on top of broken underlying data.

Second — name your saved-recovered files clearly. Don't overwrite the original. Add a suffix like _recovered_2026-05-14 to the filename. Keep both copies for a few days at minimum, longer if the recovery was incomplete.

If you discover later that the recovery missed a chunk of data, you can go back to the broken original and try Extract Data instead of Repair. If you've already overwritten it, you've shut the door on a second attempt at recovery.

Disk space is cheap. Your time isn't. A note on shared files. When two people edit the same workbook through a shared drive simultaneously — without cloud co-authoring — Excel often produces a conflict copy that diverges from the original.

Your changes save under one name, theirs save under another, and the original becomes a Frankenstein with random edits from whichever session saved last. Tracking down which version holds the right numbers can take hours.

Recovery here is less about pulling deleted files and more about merging the three copies sheet by sheet. Tedious. Sometimes impossible if both editors changed the same cells with different formulas. The fix is always the same — switch to cloud co-authoring.

VBA and macro workbooks have their own quirks. If your .xlsm crashed mid-macro, AutoRecover may save a copy with the macro code intact but the data state mangled halfway through whatever the macro was doing.

Open in Excel, hit Alt+F11 to bring up the VBE, and verify your modules look right. Restore the data, save, test the macros one at a time before trusting the recovered file in a production workflow.

Don't run all of them in one go on a recovered file. If one macro made the original crash, running it again on the recovered copy will repeat the crash and you'll lose the recovery work too. Then you're back to square one.

Linked workbooks add another layer. If File A pulls data from File B and File B crashed, opening File A throws a wall of #REF errors. Recover File B first before touching File A or you risk breaking links beyond repair.

Save the recovered File B to the original location with the original name. Reopen File A. The links should re-resolve automatically. If they don't, use Data then Edit Links then Change Source to point manually at the recovered file.

If your office still saves to a shared network drive, talk to IT about Volume Shadow Copy or snapshot-based backups. Most enterprise NAS devices snapshot every hour automatically. Most home and small-business setups don't have anything similar configured.

That gap explains why corporate users almost always recover their files and small-business users almost never do. The technology is the same. The configuration is the difference. Ask the question before you need the answer, not during a crisis at 4pm on a Friday.

For accountants — month-end closing season especially — the recovery rules tighten further. Lock down the production workbook with a password. Edit a clone. Reconcile changes. Promote the clone to production only after sign-off from the right people.

This sounds heavy. It is, until the first time someone accidentally hits Save on the wrong version at 6pm on the last day of the quarter. Then it feels like the cheapest insurance you ever bought.

Last word — keep this article bookmarked. Recovery is one of those topics you study right after disaster and forget right before the next one. The five scenarios stay the same year after year. The buttons drift but the logic stays put.