How to Restore a Previous Version of a SharePoint File

Use SharePoint version history when a file still exists but contains unwanted changes, corruption, or an older-than-expected state. Preserve today's file first, because restoring a historical version affects everyone using the same library item.

Fast route: In the SharePoint library, open the file's menu, select Version history, inspect the candidate, and choose Restore only after saving the current version separately.

1. Confirm the authoritative library item

1. Open the file through its SharePoint site.
2. Verify the tenant, site, library, folder, and filename.
3. Copy the web URL.
4. Record the unwanted change and approximate time.
5. Ask collaborators to pause edits during recovery.

A downloaded file or a same-name OneDrive copy has its own history. Work from the library URL that collaborators actually use.

2. Preserve the current version

Download the current file or use Save a Copy in its Office application. Label the copy with the date and “before SharePoint restore.” For a list item or page, capture current fields, approval state, and screenshots if export is not practical.

This safety copy preserves changes made after the target version. It also gives you material for a selective merge instead of a full rollback.

3. Open version history from the library

1. Select the ellipsis beside the file or item.
2. Choose Version history.
3. If the command is hidden, open More.
4. Review version numbers, timestamps, editors, and status.
5. Open or view promising versions.

For an Office file, File > Info > Version History can expose the same cloud history in supported applications. A historical Office version normally opens read-only, letting you compare or save a copy.

4. Account for library version settings

SharePoint libraries can retain major versions, minor drafts, or approval states. Visibility may depend on permission:

• readers may see only published major versions;
• editors may see drafts they are allowed to access;
• approvers may manage pending or rejected versions;
• checked-out documents can contain work not yet committed as a normal version.

If the expected revision is absent, ask the library owner about version limits, content approval, checkout, and draft visibility. Do not assume the user interface lost data.

5. Compare the actual file contents

Select a candidate only after application-level checks:

• Word headings, comments, tracked revisions, and tables;
• Excel formulas, tabs, named ranges, macros, and links;
• PowerPoint slides, speaker notes, media, fonts, and charts;
• PDF page count, annotations, and rendering;
• SharePoint page web parts, layout, properties, and links.

Modern SharePoint pages can visually highlight added, deleted, moved, and edited web parts between versions. Use that comparison instead of relying solely on dates.

6. Restore the selected version

1. Reconfirm the current safety copy.
2. Open the menu for the verified historical version.
3. Select Restore.
4. Confirm the prompt.
5. Wait for the library to update.
6. Reopen version history.

Microsoft explains that restoring creates a new current version based on the historical content. The intervening versions remain in history unless retention or manual deletion removes them.

7. Validate approval and collaboration state

After restoration:

1. Open the current file from the web.
2. Confirm its new version number.
3. Check approval or publishing status.
4. Review metadata columns and content type.
5. Test sharing, links, and automation.
6. Notify collaborators before editing resumes.

An older draft restored as current may still need approval or publication. Workflows and alerts can also trigger when a new version is created.

Diagnose common failures

Use a library rollback only for broad incidents

For widespread deletion, overwrite, corruption, or malware, an authorized owner can use Restore this library to undo actions from the last 30 days. That operation affects many files and folders. Protect valid newer work and review the activity timeline first.

For one file, version history is narrower and safer.

Improve version quality before the next edit

Keep versioning enabled with limits appropriate to the library, document approval requirements, and avoid unnecessary mandatory checkout for real-time coauthoring. Before major imports or approvals, save a named or independent checkpoint. Retention and backup remain necessary because version history is not permanent archival storage.

Sources

• Enable and configure versioning
• How versioning works in lists and libraries
• Compare page versions in SharePoint
• Restore a shared library