Restore an Excel File You Saved Over by Mistake

You opened last month’s budget, edited a column, pressed Ctrl+S, and only then noticed you had the wrong file open. The version you needed vanished from the screen in under a second, and Undo stopped mattering the moment the workbook closed. The previous copy may still exist in one of four places on your machine — but the order you try them in decides whether it survives.

Why the old version disappears so fast

Modern Excel does not rewrite the existing file byte by byte. It writes a complete new copy to a temporary file in the same folder, closes that file cleanly, and only then replaces the original name. The reason is sound: a crash halfway through an in-place save used to leave truncated workbooks that would not open at all.

The side effect: the previous contents are unlinked from the filename in one atomic step. No leftover .bak file, nothing in the Recycle Bin, because nothing was deleted — it was replaced.

Undo history lives in the memory of the running Excel process, so while the workbook is still open you can press Ctrl+Z and walk the change back. Close the file and that history is gone. If you have not closed it yet, do this first: File → Save As, give it a new name, keep both files. Everything below depends on copies made by something other than Excel itself.

Fix 1 — Check File → Info before touching anything else

In Microsoft 365 on Windows, open the workbook and go to File → Info. If the file is stored in OneDrive or SharePoint and sync is healthy, you get a Version History panel listing timestamped saves.

Pick the entry from before your mistake. Excel opens that version read-only in a separate window. Compare the cells you care about, then either click Restore — which makes that version current and pushes your bad save into history, so it is recoverable — or use Save As to keep both. Save As is the safer habit when you are unsure which copy is authoritative.

On Excel 2021 and 2019 the pane is called Manage Workbook and only lists AutoRecover drafts, not server versions. In that case go straight to Fix 2.

Fix 2 — Right-click the file → Properties → Previous Versions

This path uses Volume Shadow Copy, the same service that backs System Restore. In File Explorer, right-click the .xlsx, choose Properties, open the Previous Versions tab. Each entry is a snapshot of the whole folder from that date.

Open the snapshot read-only first, then use Copy to place it in a different folder. Do not use Restore in place: replacing the current file with a week-old snapshot throws away newer content that may be the only record of the work since.

An empty tab is common, not a bug: shadow copies are off on many consumer installs, are never created for removable drives, and usually do not exist for network shares. The other Windows-side option is File History (Control Panel → File History → Restore personal files), if it was ever switched on.

Fix 3 — Look at the browser, not the desktop

The web side is clearer. Sign in at onedrive.com or open your SharePoint document library, right-click the workbook, and choose Version history.

Personal accounts keep a shorter window than work accounts, and the list starts only from the day syncing began. If the file was cloud-only and you edited it through File Explorer, OneDrive uploaded each save as its own version, which means a mistaken save from ten minutes ago is almost always still sitting there. This is the single most reliable recovery path for anyone using Microsoft 365.

Fix 4 — Find the backup copies Excel already wrote

Two file types confuse people constantly, and only one is useful.

• ~$budget.xlsx — a lock file, usually 1–2 KB, recording who has the workbook open. It holds no cells. Renaming it to .xlsx produces a corrupt file and wastes an afternoon.
• .xlk — the real backup, created when File → Options → Save → Always create backup copy is ticked. It sits in the same folder under the same base name. Copy it, rename the copy’s extension to .xlsx, and open that.

Then check %LocalAppData%\Microsoft\Office\UnsavedFiles and %AppData%\Microsoft\Excel, sorted by date modified, for anything written around the time of the mistake.

Fix 5 — Recover Unsaved Workbooks

File → Info → Manage Workbook → Recover Unsaved Workbooks opens the UnsavedFiles folder directly. It is built for workbooks that were never saved at all, so it rarely helps after an overwrite. It still costs one click, and on some installs Excel parks a draft there when it closes abnormally. The Delete entry next to it is permanent and asks for no confirmation on some builds.

When it is not worth fixing

If the overwrite happened on a local drive with no restore points, no File History and no cloud copy, the previous bytes were overwritten on disk. On a solid-state drive this gets worse quickly: TRIM marks the replaced blocks as free and the controller erases them within seconds, so undelete tools that still work on spinning disks return little but unreadable fragments.

A partial result still counts. A version from last week plus your current file often lets you rebuild the difference in ten minutes. What cannot be reconstructed is a number that only ever existed in the copy you replaced. If the workbook also opens to a repair prompt or shows an empty sheet, that is a different failure with a different order of operations, covered in Excel file won’t open — read that before running any repair tool, because repair writes to the file.

If you would rather have someone examine the file than keep experimenting on it, the assessment described on the services page starts from a copy, never the original.

FAQ

Can I undo a save after the file is closed? No. Undo history is held by the running process and discarded on close. After that, recovery depends on version history, shadow copies, or a .xlk backup.

Does OneDrive keep the version I overwrote? Usually, when the file sat in OneDrive or SharePoint and sync was running. Personal accounts retain a shorter history than work accounts, so check the same day rather than next month.

Is the ~$ file my backup? No. It is a lock file with an owner name and a few bytes of metadata. It will not open as a workbook no matter how you rename it.

Will a data recovery service get it back? On a mechanical drive that has not been written to since the mistake, possibly. On an SSD with TRIM active, realistically no, because the blocks are already erased. Ask what happens if nothing is found before agreeing.