How to Restore a Previous Version of a Word, Excel or OneDrive Document

Quick answer

If the file is saved in OneDrive, OneDrive for Business, or SharePoint, you have version history. The fastest path: open the document in Word, Excel, or PowerPoint, click File → Info → Version History, choose the version you want, and either restore it or save it as a copy. From the OneDrive web app, right-click the file and choose Version history. Either path takes about ten seconds.

If the file is stored only on your local PC and was never on OneDrive, the answer is uncomfortable: Version History doesn’t apply, and the File Explorer “Previous Versions” tab almost never works on default Windows 11 because File History isn’t on by default. The honest options for a local-only file are limited — see “When to stop” below.

Last tested: Word and Excel for Microsoft 365 (Version 2402+), OneDrive web app, Windows 11 24H2.

Before you start

The single most important thing to establish before you click anything is where the file lives. Recovery options depend entirely on that.

  • Cloud-saved files (OneDrive Personal, OneDrive for Business, SharePoint): Version History works reliably. Multiple recovery paths. Don’t worry.
  • Local-only files (saved to C:, Documents, Desktop, an external drive, or a network share that isn’t SharePoint): Recovery depends on whether File History or Volume Shadow Copy was enabled before the loss. On a default Windows 11 install, neither is on. If you didn’t configure it, the previous version doesn’t exist anywhere on the machine.

Check this first by right-clicking the file. If you see “Show more options → Restore previous versions” and that dialog has actual versions listed, you have local backups. If it’s empty, you don’t — and no amount of clicking will produce versions Windows wasn’t recording.

The other thing worth knowing: Office’s own Version History inside Word, Excel, and PowerPoint only lists versions for files saved to OneDrive or SharePoint. For local files it’s empty. This is a frequent source of confusion.

What “previous version” means in different places

Three independent systems can produce a previous version of a file. They overlap in confusing ways.

1. OneDrive / SharePoint Version History. Every save to a OneDrive-stored file (manual or AutoSave) creates a version. OneDrive Personal keeps versions for at least 30 days, often much longer in practice. OneDrive for Business and SharePoint keep up to 500 versions by default and rarely run out — large files and high churn can age old versions out faster.

2. Office app Version History. This is the same data as #1, exposed inside the Office app via File → Info → Version History. Same versions, friendlier UI, with the ability to compare versions side-by-side before restoring. Only works for files saved to OneDrive or SharePoint.

3. Windows File History / Volume Shadow Copy. A separate Windows-side mechanism that creates local snapshots of files in protected locations on a schedule. Requires explicit setup. File History needs an external drive or network location to be enabled. Shadow Copies are usually only created during major system events (Windows Update, System Restore points), and rarely cover regular user files. Surfaces in the Previous Versions tab on the file’s Properties dialog.

If your file is on OneDrive, you have (1) and (2). If your file is local-only and you set up File History or Shadow Copies before the loss, you have (3). If your file is local-only and you didn’t, you have nothing — and that’s the situation most people are in.

Where this typically happens

Most “I need an earlier version” requests come from one of these patterns:

A spreadsheet where someone overwrote a working formula and saved. A Word document edited by a collaborator who deleted a section the owner needed back. A “Save As” that overwrote the original instead of creating a copy. A PowerPoint where slides were deleted and the file saved before anyone noticed. An accidental Find-and-Replace that wrecked the document. A file that was edited correctly, saved, and then “improved” by another collaborator’s worse version.

In every case, what you need is the version before the bad save. The path to that version depends on where the file lives.

Common scenarios

  • Word, Excel, or PowerPoint file in OneDrive or SharePoint, saved over with bad edits. Office app Version History (path 1 below). Thirty seconds.
  • Word document on local Desktop, never synced. File Explorer Previous Versions, only if File History was on before the change. Usually empty.
  • File originally on OneDrive but copied to Desktop and edited there. Version History on the OneDrive copy works for the period before the copy. Anything after that is in local-file territory.
  • File on a corporate network share. Depends on whether the file server runs Volume Shadow Copy (most do, with daily or weekly snapshots). Ask your admin.

Fixes to try first

These are the standard recovery paths in order. If your file is in OneDrive or SharePoint, step 1 or step 2 will solve this in a minute.

1. Use Version History inside the Office app.

Open the file in Word, Excel, or PowerPoint. Click File → Info, then click Version History. A pane opens on the right showing every saved version with a timestamp and the user who made it. Click any version to open it as a read-only preview in a separate window. From that preview you have two options at the top of the window: Restore (which overwrites the current file with this version) or Compare (which opens a side-by-side merge view).

If you’re not sure whether the older version is the one you want, always use Compare first. Restore is one-click and doesn’t ask for confirmation.

2. Use Version History on the OneDrive web app.

Open OneDrive in your browser, navigate to the file, and right-click. Choose Version history. The same list of versions appears in a panel. Each entry has a three-dot menu — choose Restore or Open file to preview before deciding.

This path is useful when the Office app is misbehaving, when you want to download a previous version as a separate file, or when you don’t want to open the document at all.

3. For SharePoint document libraries, use Version History from the document library.

In a SharePoint site library, click the document’s three-dot menu and choose Version history. Same data, same restore action. Note that SharePoint libraries can have versioning configured per library — if your admin disabled it, no versions will exist regardless of which path you use.

Advanced fixes

These cover local-only files and the cases where the standard paths don’t apply.

Try the File Explorer Previous Versions tab.

Right-click the file in File Explorer, choose Show more options → Restore previous versions (Windows 11) or Properties → Previous Versions tab (older Windows). If anything is listed, you can restore it. Most users see nothing, because:

  • File History isn’t enabled on default Windows 11 installs (it requires an external drive or network location to be configured).
  • System Restore creates Volume Shadow Copies that mostly capture system files, not user documents.
  • The Previous Versions feature in Windows 11 only surfaces these two sources.

If the dialog is empty, no previous version exists in the local backup systems. Don’t keep clicking — there’s nothing more to find.

Check OneDrive Files Restore (M365 subscribers).

If the file used to be in OneDrive but is now in a state you don’t want, Files Restore can roll the entire OneDrive back to a date in the last 30 days. This is overkill for one file but works when Version History doesn’t have the version you want — for example, if the file was deleted and re-created with the same name, breaking the version history chain. Open OneDrive on the web, click the gear icon, and choose Restore your OneDrive. See recovering a deleted OneDrive file for the full walkthrough.

For shared network drives — ask about Shadow Copies.

Most Windows file servers run Volume Shadow Copy and take periodic snapshots (typically daily or hourly during business hours). If your file lives on a \\server\share path, right-click and choose Properties → Previous Versions. If snapshots are running, you’ll see a list. If not, your admin can usually still recover from the server’s snapshot history even if the Previous Versions tab is empty client-side — they just need the file path and the timeframe.

On Mac — Time Machine for local files.

If you’re on macOS and you set up Time Machine before the change, it has hourly snapshots for the past 24 hours, daily for the past month, and weekly older. Use the Time Machine UI to find and restore the right version. Same constraint as Windows File History: it has to have been on before the loss.

For files saved to OneDrive but with no version you want.

If Version History has versions but none is the one you need, two reasons are common: AutoSave saved over your work mid-edit before you realized (the bad version became the basis for all subsequent saves), or a different user with edit access made the change. In either case, Files Restore on the whole OneDrive (above) is the broader-reach option. For unsaved-edit recovery on Word specifically, see recovering an unsaved Word document.

If you are on a work or school device

Tenant-level recovery options often exist in business environments that don’t exist in personal ones.

Tenant retention policies. If your organization has Microsoft Purview retention applied to OneDrive or SharePoint, deleted or modified files may be silently held in a Preservation Hold Library beyond the standard version history window. Only an admin can access this. If your file is past the version history retention or has lost the right version, it’s worth asking.

Tenant backup products. Many organizations run third-party backup over Microsoft 365. If standard recovery paths fail, ask your IT admin whether tenant backup exists. Recovery from these typically goes back months or years rather than days.

Library versioning settings. SharePoint document libraries can have versioning configured by admins — major versions only, major and minor, or no versioning at all. If a library has versioning disabled, no versions exist regardless of your account. Check with your admin if Version History is unexpectedly empty.

What you shouldn’t do on a managed device: install document recovery software to scan for previous versions. These tools recover deleted files from disk, not previous versions of existing files, and won’t help here.

When to stop

If your file lived only on a local drive, was never on OneDrive or SharePoint, and File History wasn’t enabled before the loss, the previous version doesn’t exist on the machine in any form recovery software can find. Tools that scan for “deleted file fragments” are looking for something different — they recover deleted files, not earlier versions of files you still have. You can’t recover what was never recorded.

The honest move at that point is twofold. First, accept the loss for this file. Second, fix the underlying setting so this doesn’t happen again. The fix is one of these, ranked by how reliable they are:

  • Save the file in OneDrive or SharePoint going forward. Version History is automatic and free with any Microsoft 365 plan.
  • If you can’t use the cloud, enable File History on Windows (Settings → System → Storage → Backup → File History) and point it at an external drive. Versions will accumulate from that point on.
  • For shared business files, push your IT team to enable Shadow Copies on the file server if they haven’t.

Pick one. None of them recover the file you’ve already lost — but they all prevent the next loss, which is the only useful thing you can do at this stage.

  • Recover an unsaved Word document — for files where AutoRecover is the path, not Version History
  • Recover a deleted OneDrive file — when the file was deleted entirely, not just edited badly

Official references

FAQ

How far back does Version History go?

OneDrive Personal keeps versions for at least 30 days, often considerably longer in practice. OneDrive for Business and SharePoint keep up to 500 versions per file by default. Both engines age old versions out as new ones come in — high-churn files reach the cap faster than low-churn files. There’s no fixed time limit; there’s a version count.

Why does the Office app show no Version History?

Two common reasons. First: the file is saved to a local drive, not OneDrive or SharePoint. Office’s Version History only works for cloud-saved files. Second: the file is on OneDrive but was opened via a local sync path before being saved — confirm by checking the title bar of the document, which should show the cloud location.

Will Restore overwrite the current version?

Yes — restoring an older version makes it the current version. The previous “current” version becomes a new entry in the version history, so nothing is lost permanently. To grab a copy of the older version without changing the current state, use Open file or Download instead.

Why is the Previous Versions tab empty in File Explorer?

Almost always because File History wasn’t enabled before the change. The Previous Versions tab pulls from File History snapshots and Volume Shadow Copies — neither runs by default on Windows 11. If you never set them up, there are no snapshots to surface.

Can I see who made each change in Version History?

Yes, on OneDrive and SharePoint. Each version entry shows the user who saved it and the timestamp. This is particularly useful in shared SharePoint libraries where multiple people edit the same file. The Office app’s Version History shows the same metadata.

My file was on OneDrive, then I copied it to Desktop and edited locally. What can I recover?

You have the OneDrive copy’s version history up to the point you copied it. Edits made locally after the copy aren’t in OneDrive’s version history — that file became a separate object. Recovering local edits requires File History or another local backup to have been running on the Desktop side at the time.

↑ Back to top