Excel AutoSave saves changes to a supported workbook on OneDrive or SharePoint while you work. It is not a folder full of backup copies. If a recent edit vanished, check which account and file you opened. Then inspect Version History before replacing anything. If the entire workbook disappeared from a local Windows drive, protect the drive and look for the file itself. This distinction saves you from searching temporary folders when the answer is in the cloud. It also prevents a pointless cloud search for a local-only original.
What AutoSave saves, and what it does not
In current Microsoft 365 versions of Excel, the AutoSave switch applies to a workbook saved in OneDrive or SharePoint. When the switch is on, Excel writes changes to that cloud file frequently as you edit. You are working on the same file, not creating a separately named copy after every keystroke. The file name and cloud account therefore matter as much as the switch itself. Two workbooks with identical names in different accounts can look like one lost file until you inspect their locations.
Version History is the way to examine earlier states of a cloud file. Its entries are not a recording of every individual keystroke, so a particular moment may not have its own recoverable version. Still, an earlier version can be more useful than guessing which local temporary file contains the missing rows. Before restoring it, open the candidate and compare the relevant sheets, formulas, and timestamps. Save a separate copy of the current workbook first, especially if coworkers have edited it since the mistake.
AutoRecover serves another purpose. It may preserve work after Excel closes unexpectedly, including work from a local session. It does not make a local-only file eligible for cloud AutoSave. For the recovery snapshot location rather than the cloud-save feature, follow the separate Excel AutoRecover file-location steps.
Confirm the workbook and account before changing a setting
Read the location shown by Excel
Open the workbook in desktop Excel and select its name near the top of the window. Check the location associated with that file. An expected OneDrive or SharePoint location supports the cloud-save path. A local drive letter suggests you may be editing a different copy. If your organization has both personal and work accounts, read the account name carefully. A Recent Files list can show entries from several places. A familiar filename alone proves very little.
Make a harmless test edit only after you have identified the correct workbook. Add a temporary value in a spare cell, wait for the save indication, and inspect the same file through OneDrive or SharePoint in a browser. Remove the test value afterward. If the browser shows a different workbook, stop and resolve the account or path mismatch before changing more data. Do not run a test in a shared production sheet where even a temporary edit could trigger formulas, alerts, or a colleague’s workflow.
Keep a copy before experimenting
Use File > Save a Copy when you need an independent starting point for a new project. If you instead change the original and plan to use Save As at the end, AutoSave may already have written those changes to the original. Name the copy clearly and check its location before editing. This is particularly important for templates, financial models, and workbooks shared with a team. It also gives you something safe to compare against an older version later.
Turn AutoSave on without confusing it with AutoRecover
For a Microsoft 365 workbook, choose File > Save As from within Excel. Select the intended OneDrive or SharePoint location, give the file an identifiable name, and save it. Open that cloud file and check the AutoSave switch at the upper left. Microsoft documents the cloud-location requirement in its AutoSave setup instructions. If you use a work account, your organization may control available locations or app versions. Ask its administrator before moving confidential data into a personal account merely to make the switch appear.
Do not simply drag a local workbook into a synced folder and assume Excel now treats it as the active cloud copy. Open or save the intended file from Excel, then confirm its displayed location. A sign-in problem or sync delay can leave you looking at an older local version. Check the account and location instead of trusting the toggle’s color alone.
If the switch stays off, ask three concrete questions. Is the workbook saved to a supported cloud location? Are you signed in to the account that owns or can edit it? Is the file in a format and application state that supports AutoSave? For example, a CSV is not an Excel workbook with all of its features, and Microsoft says CSV files do not support AutoSave. Preserve the CSV as data, then save a separate supported workbook if that workflow is appropriate. Do not rename an extension to make the toggle appear.
Recover an earlier edit from the right history
Compare versions before you restore one
If an edit was overwritten in a cloud workbook, open that file and select its name or the Version History command. Review the dated entries and open a promising earlier version. Look beyond the first visible worksheet. Inspect the exact tab, cells, formulas, and linked tables that matter. Another teammate may have changed the file after the version you want. Restoring immediately could discard their useful work. Save the current file as a separate copy. Then decide whether to restore the older version or copy only the needed cells.
A version may be absent for the minute you remember. AutoSave writes frequently, but Version History does not necessarily create a separate version for every save. Search the nearby entries instead of assuming the feature failed. If the workbook sits in a different Microsoft account or a SharePoint library, inspect that service’s history for the actual file. A local file with the same name has no automatic claim to those cloud versions.
Decide whether Undo is still the simpler answer
For a recent change in an open editing session, Ctrl+Z may be enough. Once you close and reopen the workbook, Undo history is not a substitute for file versions. For the distinction among Undo, cloud history, and a missing local file, see how to undo in Excel. Choose the least disruptive method that fits the event. Do not replace a whole workbook for one cell if you can safely copy that cell from an older version.
A grey or absent AutoSave switch is a clue, not proof that Excel has lost your work. Start with the file’s displayed storage location and the signed-in account. If the file remains on a local drive, save a copy to an approved OneDrive or SharePoint location if your organization permits it. If it already points to cloud storage, check whether you can open that exact file in a browser. A browser copy that is newer than the desktop copy suggests a sync, sign-in, or duplicate-file problem, not necessarily missing spreadsheet data.
Check the extension and whether Excel opened the document as read-only or in a protected state. Preserve the original before converting formats or changing permissions. If a colleague owns the file, ask whether you have edit access. Keep manual saves while you investigate; an unavailable AutoSave switch does not stop you from using Ctrl+S. It also does not mean the AutoRecover feature is unavailable after a crash.
A shared workbook can have simultaneous edits from several people. Before replacing its contents, tell collaborators which copy and time you are examining. Compare the cloud version’s last-modified information with your saved copy. If a coworker’s changes are present in one version but not another, extract the missing data into a separate workbook for review. That is safer than repeatedly restoring versions until the visible cells look right.
When the workbook itself is missing from a Windows drive
For a workbook stored only online, check the correct OneDrive or SharePoint account, its recycle bin, and its version history. A scan of your PC cannot search Microsoft’s servers. If the workbook was stored locally and then deleted, inspect the Windows Recycle Bin and any backup you already have. Stop saving new files to the affected drive while you search. If the drive disconnects, makes unusual noises, or develops severe read errors, stop repeated software scans and ask a specialist about imaging or recovery.
On a stable Windows drive, PandaOffice Drecov can search the original storage device for a lost workbook. Its read-only recovery workflow, Quick Scan, Deep Scan, filters, and preview help you examine candidates. It does not reverse edits in the active cloud workbook or repair physically damaged hardware, and recovery depends on the file data still being present. The Excel recovery topic page explains other file-loss cases.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Step 1: Choose the original local location
Prepare a separate healthy drive for recovered files, and do not install recovery software on the partition that held the lost workbook. Open Drecov, then select the readable Windows drive or original folder where that workbook last existed. If the missing file lived only in OneDrive online, return to the cloud account instead of scanning your PC.
Step 2: Scan and identify the workbook
Run Quick Scan first. Search by the old filename, folder, or document type, then compare candidate dates and sizes. If the file is absent and the source remains stable, run Deep Scan and review additional candidates. Preview representative spreadsheets when the format supports it, but remember that a preview may not expose every worksheet or formula. A familiar first tab is not enough evidence that the entire workbook survived.
Step 3: Save elsewhere and verify
Recover the promising copies to the separate healthy drive, never back to the original source. If the output is not where expected, check the Drecov folder or Recovery folder. Open each recovered workbook in Excel and inspect the needed sheets, formulas, and recent rows. Keep the best verified copy separate from the current cloud workbook until you have decided what to merge. Only then consider repair, cleanup, formatting, or other changes to the original drive.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Make the next save easier to trust
Choose one named source of truth for important spreadsheets. Use a specific cloud account and folder, or a managed local location with a separate backup. Record who can edit a shared workbook and how to find its version history. When starting a new calculation from an old model, create a copy first. Verify that the copy’s name and location changed before altering formulas. These checks prevent many apparent AutoSave failures that are really edits to the wrong file.
For local-only workbooks, continue to save normally and keep a backup schedule. AutoRecover can help after a crash. It is temporary protection, not a history of every decision you made. An unstable drive needs more urgent attention than an Excel toggle. Copy readable data to safe storage while you can, and stop if the device deteriorates. Once you know which copy is current, open an older version and inspect it. That tells you more than a switch that merely appears to be on.
Conclusion
Excel AutoSave works for the right cloud workbook and account; Version History helps you inspect earlier states, while AutoRecover addresses a different crash scenario. Identify the actual file before changing settings or restoring an older copy. If a local workbook was deleted, protect its drive and use Drecov only while that device is stable and readable. Recover to another drive, open the result, and verify the sheets you need before replacing anything.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
