SharePoint Version History, How It Actually Works and How to Restore an Old File
What happens when someone overwrites a document, and how to get the old copy back
By Shehryar Hassan, Microsoft 365 & Azure Consultant
Someone on your team just told you they overwrote a file, or a formula got deleted, or a whole section of a document vanished after someone else edited it. The first question is always the same: is it gone for good?
Usually not. Every document library in SharePoint, and every OneDrive, keeps version history automatically, without anyone turning it on. Each time a file is saved, whether that's someone hitting save in Word or the auto-save that runs during co-authoring, SharePoint quietly stores a new version behind the current one.
Finding and restoring an old version
Open the file's details pane (the "i" icon in the top right of the library, or right click the file and choose Details). Under Version History you'll see a list of every saved version with a timestamp and who made it. Click a version to preview it, and if it's the one you want, use the three dot menu next to it and choose Restore. That swaps the current version for the old one and keeps a record of the change, it doesn't erase anything.
You can do the same thing from inside Word, Excel, or PowerPoint on the web: File, Info, Version History does the same lookup without leaving the app.
Where this trips people up
A few things catch admins and users off guard.
Version history isn't unlimited by default. Most libraries keep 500 major versions now, which is a lot, but a site owner can still turn that number down or up in library settings, so don't assume every version back to day one is sitting there.
Deleting a file doesn't wipe its versions right away. The whole file, versions included, goes to the site's Recycle Bin and stays recoverable for 93 days, then a second stage recycle bin holds it a bit longer before it's really gone.
Heavy co-authoring can generate a lot of versions fast. Several people editing the same document in one afternoon can produce dozens of minor versions, which is normal and nothing to worry about.
If a file is checked out to someone, which still happens on older libraries with check-in and check-out turned on, version history still works, but you're only seeing versions up to the last check-in.
None of this needs IT involvement most of the time. Point the person at Version History first. It solves the "I lost my work" panic far more often than people expect.
Get new posts by email
One note when there is something worth reading. No spam, unsubscribe anytime.
Related articles
What Viva Engage Actually Is and Whether Your Team Needs It
Viva Engage is Microsoft's rebrand of Yammer, built for open company-wide conversation rather than project work. Here's what it actually does and when it's worth switching on.
Windows 365 Cloud PC, What It Actually Is and When You'd Use One
Windows 365 gives each user a dedicated cloud desktop at a flat monthly price, no Azure portal required. Here's how it actually differs from Azure Virtual Desktop and when it's worth the seat cost.
Getting Started With Power BI for Excel Users
Power BI can feel like an unnecessary extra step if you already know Excel. Here's what it actually does differently, and when it's worth learning.