You need to restore a previous version of a SharePoint page after an unintended edit or content error. SharePoint automatically saves versions each time you publish a page. This article explains how to review version history, restore a specific version, and set governance rules to control version retention. You will learn the exact steps to recover content and the settings that prevent version bloat.
Key Takeaways: Restoring SharePoint Page Versions and Governance
- Page details pane > Version history: Opens the list of all saved versions with timestamps and authors.
- Restore button in version history: Replaces the current published version with the selected older version.
- SharePoint admin center > Site collection > Version settings: Limits the number of major versions retained per page.
How SharePoint Page Versioning Works
SharePoint stores a separate copy of a page each time you publish it. Minor versions (drafts) are saved when you save without publishing. Major versions are created when you click Publish. The version history includes the date, time, and the person who made the change. By default, SharePoint retains all major versions indefinitely unless you set a limit. This can cause storage growth if pages are edited frequently.
The version history feature is available on all modern SharePoint pages, including wiki pages, web part pages, and news posts. You must have Edit or Full Control permissions to restore a version. Viewers can see the version history list but cannot restore.
Steps to Restore a Previous Version of a SharePoint Page
- Open the page in edit mode
Navigate to the site that contains the page. Select the page from the site pages library or open it directly. Click the Edit button in the top command bar. The page opens in edit mode. - Open the page details pane
Click the Page details button in the top right corner of the page. The details pane opens on the right side of the screen. - Select Version history
In the page details pane, scroll down and click Version history. A list of all saved versions appears, showing the version number, date, time, and the person who saved it. - Choose the version to restore
Click the version you want to restore. The page preview shows the content of that version. Confirm it is the correct version. - Click Restore
Click the Restore button directly on the version row. A confirmation dialog asks if you want to restore this version. Click Restore again. The page is replaced with the selected version. The restored version becomes the current published version. - Check the page after restore
Close the version history pane. Review the page to confirm the content is correct. Republish the page if needed by clicking Publish in the top command bar.
Restoring a Version Without Opening the Page
- Go to the site pages library
From the SharePoint site, select Pages from the left navigation or click Site contents and open the Pages library. - Select the page
Hover over the page name and click the check box that appears. - Click Version history on the command bar
With the page selected, click Version history in the top command bar. The version history panel opens. - Restore the version
Follow the same steps as above to select and restore a version.
Setting Version Limits for Governance
To prevent unlimited version storage, set a maximum number of major versions per page. This is done at the site collection level in the SharePoint admin center.
- Open SharePoint admin center
Go to the Microsoft 365 admin center and select SharePoint. Or directly navigate to admin.microsoft.com and choose SharePoint. - Select Active sites
In the left navigation, click Active sites. A list of all site collections appears. - Choose the site collection
Click the name of the site collection where you want to set version limits. Do not click the check box. - Open Settings
In the site details panel that opens, select the Settings tab. Scroll to the Site collection settings section and click Site collection features. - Find Version settings
Scroll down the list of features and locate Version settings next to the document library. Click the Activate button if the feature is not already active. - Set the version limit
After activation, click Version settings. Enter the maximum number of major versions to keep. For example, enter 100. SharePoint will keep the most recent 100 major versions and delete older ones automatically. - Save the changes
Click OK to apply the version limit. The setting applies to all pages in that site collection.
Common Issues When Restoring Page Versions
Restore button is grayed out
You do not have Edit or Full Control permissions on the site. Contact the site owner or administrator to grant the appropriate permission level. Site members with Contribute permission cannot restore versions.
Version history is empty
No major versions have been published. Draft versions are not shown in the version history list unless you have permission to view drafts. Publish the page at least once to create a major version.
Restored page looks different from the preview
The version preview may not load all web parts correctly. After restoring, edit the page and check each web part. Refresh the browser to see the full page.
Version limit deleted old versions
If you set a version limit, older versions are permanently deleted. You cannot restore a version that was removed. Set the limit high enough to retain the history you need.
Manual Restore vs Version Limit: Key Differences
| Item | Manual Restore | Version Limit |
|---|---|---|
| Purpose | Recover a specific previous version of a page | Control storage by limiting the number of versions kept |
| Action | User clicks Restore on a version row | Admin sets a number in site settings |
| Effect | Replaces current published version with selected version | Deletes oldest versions when new versions are published |
| Permission needed | Edit or Full Control | Site Collection Administrator |
Restoring a previous version is a direct content recovery action. Setting a version limit is a governance action that prevents uncontrolled version growth. Use both together for complete version management. After restoring, always check the page for broken web parts or missing content. If you frequently restore versions, consider setting a higher version limit to keep more history.