Version History Is Missing for a Document Library: Fix

When you open a document library in SharePoint and find that the Version History option is grayed out or shows no entries, you cannot restore a previous version of a file. This problem usually occurs because the versioning settings for the library have been disabled or the library is configured to keep only the current version. This article explains how to check and enable versioning in SharePoint, restore the version history feature, and address related issues like missing major or minor versions.

Why Version History Is Missing in a Document Library

SharePoint document libraries use versioning to save a copy of a file each time it is edited. When versioning is turned off, SharePoint overwrites the file without keeping the previous version. The Version History option in the file context menu then shows no entries or is grayed out.

Versioning can be disabled by a site administrator or by a policy applied to the site collection. The library may also be set to keep only a limited number of versions, and if the limit is reached, SharePoint automatically deletes the oldest version when a new one is saved. In some cases, the library uses a content type that overrides the versioning settings.

The fix requires checking the library versioning settings and ensuring that major version creation is enabled. You must also set a reasonable limit for the number of versions to keep. If the library inherits settings from a content type or site policy, those must be adjusted at the higher level.

Steps to Enable Version History in a Document Library

To restore version history for a document library, you need to access the library settings from the SharePoint site. The steps below assume you have at least Edit or Design permissions on the site. If you cannot see the settings, contact your site collection administrator.

1. Open the document library
   Navigate to the SharePoint site that contains the document library. Click the library name in the Quick Launch menu or from Site Contents to open it.
2. Go to Library Settings
   Click the gear icon in the top-right corner of the page and select Library settings. If you are on a modern team site, you may need to click Library on the command bar, then Library settings.
3. Open Versioning Settings
   Under the General Settings section, click Versioning settings. This opens the page where you configure how versions are created and stored.
4. Enable major version creation
   In the Content Approval section, leave the default setting unless you require approval. In the Document Version History section, select Create major versions. Do not select No versioning.
5. Set the number of versions to keep
   In the Keep the following number of major versions field, enter a number such as 100 or 500. If you enter 0, SharePoint will not keep any versions. For libraries with many files, set a limit that balances storage and recovery needs.
6. Optionally enable draft version security
   If you plan to use content approval or minor versions, select Create major and minor (draft) versions instead. Then set Keep drafts for the following number of major versions to a value like 10.
7. Save the settings
   Click OK at the bottom of the page. SharePoint applies the new versioning settings immediately. Existing files will not get version history retroactively, but any future edits will create version entries.

If Version History Still Does Not Appear After Enabling

Enabling versioning does not restore version history for files that were edited before the change. If the Version History option is still missing or grayed out, check the following scenarios.

Library Uses a Content Type That Disables Versioning

Some libraries use content types that override the library-level versioning settings. To check this, go back to Library settings and look under Content Types. If a content type is listed, click its name. On the content type settings page, find the Advanced Settings section. Ensure that Allow management of content types is enabled and that the versioning settings for the content type match what you set at the library level. If the content type has No versioning selected, change it to Create major versions.

Site Collection Versioning Policy Overrides Library Settings

A site collection administrator may have applied a policy that limits or disables versioning. This policy is set in the SharePoint admin center. Go to SharePoint admin center > Policies > Versioning. If a policy is applied to your site, you will see a message in the library versioning settings page that reads This setting is managed by a site policy. In that case, the library setting cannot be changed. Contact the site collection administrator to adjust the policy or request an exception for your library.

Version History Was Deleted by a Retention or Storage Limit

If versioning was previously enabled but the history is now missing, the library may have reached its version limit. Check the Keep the following number of major versions value. If it is set to a low number like 1, SharePoint keeps only the most recent version and deletes all older versions. Increase this number to preserve more versions. Also check the site collection storage quota. If the site is over quota, SharePoint may automatically delete version history to free up space. In that case, free up storage by deleting old files or requesting more storage from the administrator.

Team Site vs Communication Site: Versioning Defaults and Differences

Item	Team Site	Communication Site
Default versioning for new library	Major versions enabled, keep 500 versions	Major versions enabled, keep 500 versions
Minor versions supported	Yes, can be enabled	Yes, can be enabled
Content approval default	Disabled	Disabled
Draft item security default	Only users who can edit items	Only users who can edit items
Policy override possibility	Yes, via SharePoint admin center	Yes, via SharePoint admin center

Both site types use the same versioning engine. The default settings are identical. The main difference is that team sites often have Microsoft 365 Groups attached, which can apply additional retention policies through Microsoft Purview. If a retention policy deletes version history, you need to adjust the policy in the Microsoft Purview compliance portal.

You can now enable version history in any document library using the Library Settings page. If the option is blocked by a site policy or content type, escalate the request to the site collection administrator. To prevent future version loss, set the version limit to at least 100 and monitor the site storage quota monthly.