You open a document library in SharePoint and see no version history entries for any file. This happens even though you know colleagues have edited the files multiple times. The cause is often a site collection feature that disables versioning or a library setting that limits history retention. This article explains why version history can vanish and provides the exact steps to restore it.
Key Takeaways: Fix Missing Version History in SharePoint
- Site collection feature “Document and Task Version Settings”: When deactivated, version history is not recorded for any library in the site.
- Library settings > Versioning settings: Controls whether major, minor, or no versioning is enabled for that specific library.
- SharePoint admin center > Site collections > Storage limits: Exceeding the site storage quota can cause version history to be deleted automatically.
Why Version History Disappears in a Document Library
SharePoint version history is controlled at three levels: the site collection feature, the library versioning settings, and the site storage quota. When version history is missing, one or more of these layers is misconfigured.
Site Collection Feature Deactivated
Every site collection has a hidden feature called “Document and Task Version Settings.” This feature must be active for version history to work. If a site collection administrator deactivates it, no new versions are saved for any document in any library. Existing versions remain visible, but new edits do not create entries.
Library Versioning Disabled
Each document library has its own versioning settings. If versioning is set to “No versioning,” SharePoint saves only the current version of each file. No history is retained. This setting is often changed accidentally when copying library templates or restoring from backup.
Storage Quota Exceeded
SharePoint sites have a storage limit set in the SharePoint admin center. When a site exceeds its quota, SharePoint automatically deletes old version history to free space. The deletion is silent and permanent. Users see only the current version and no prior entries.
Steps to Restore Missing Version History
- Check the site collection feature
Go to the site collection where the library lives. Click the gear icon and select Site settings. Under Site Collection Administration, click Site collection features. Find “Document and Task Version Settings.” If it shows Deactivate, the feature is already active. If it shows Activate, click Activate. - Enable versioning on the library
Navigate to the document library. Click the gear icon and choose Library settings. Under General Settings, click Versioning settings. Select Create major versions or Create major and minor (draft) versions. Set the number of versions to keep to a value like 100 or 500. Click OK. - Verify site storage quota
In the SharePoint admin center, expand Sites and select Active sites. Find the site containing your library. Check the Storage Used column. If it is at or near the Storage Limit, you need to increase the quota or free up space. To increase quota, select the site, click Policies, then Edit, and raise the storage limit. - Clear the browser cache
After changing settings, clear your browser cache or open a private browsing window. This ensures you see the latest version history entries. - Test with a new file
Upload a new file to the library. Edit it twice, saving changes each time. Open the version history for that file. If you see two versions, the fix is working. If you still see none, repeat steps 1 through 3.
If Version History Is Still Missing After the Main Fix
Version history was deleted by a retention policy
SharePoint retention policies can automatically delete older versions after a set number of days. Check if a retention policy applies to the library or site. Go to the SharePoint admin center > Information protection > Retention. Look for policies that target the site or content type. If a policy deletes versions after 30 days, you will not see history older than that.
Site collection was restored from backup
Restoring a site collection from backup often resets versioning settings to “No versioning.” After the restore, follow the steps above to re-enable versioning. Versions created before the backup are lost, but future edits will be tracked.
Third-party migration tool changed settings
Some migration tools disable versioning to speed up the transfer. After migration, manually enable versioning on each library. Check the migration tool’s logs for any setting changes.
Document Library Versioning Settings: Before vs After Fix
| Item | Before Fix | After Fix |
|---|---|---|
| Site collection feature | Deactivated | Activated |
| Library versioning | No versioning | Major versions or major/minor |
| Storage quota usage | At or above limit | Below limit |
| Version history visible | Only current version | All saved versions |
You can now check the site collection feature, library versioning settings, and storage quota to restore missing version history. Next, set a retention policy that matches your business needs so old versions are kept but not deleted prematurely. An advanced tip: use the Set-PnPListVersioning PowerShell cmdlet in PnP PowerShell to enable versioning on hundreds of libraries at once.