Last Updated: November 10, 2026
Quick Summary
SharePoint version control settings live at the library and list level, not in one central admin panel. Open the library or list, select the gear icon, choose Library settings or List settings, then Versioning settings under General Settings. Site-level limits act as a ceiling, and the more restrictive value wins.
- Every minor version is a stored copy, so draft-heavy libraries grow fast.
- Lowering a site-level limit can permanently delete versions with no undo once expiration runs.
- Policies, contracts and signed agreements need a limit of 50 or higher.
- Automatic expiration deletes old versions permanently, with no recycle bin for individual versions.
- Restoring a previous version creates a new version rather than erasing the current one.
Table of Contents
- Where SharePoint Version Control Settings Actually Live
- SharePoint Major and Minor Versions: What Each One Costs You
- Picking a SharePoint Version History Limit That Holds Up
- SharePoint Intelligent Versioning and Automatic Expiration
- How to Restore Previous Version SharePoint Document Copies
- Version Limits, Storage Consumption, and Retention Policies
- Troubleshooting Missing or Unexpected Versions
- Book a Version Control Configuration Review
- Frequently Asked Questions
Where SharePoint Version Control Settings Actually Live
Most SharePoint version control problems start in the wrong settings screen. Teams hunt for a global switch, find nothing, and assume the platform is broken. It isn't. SharePoint document version control settings live at the library and list level, not in one central admin panel, and that single fact explains most of the confusion we see at MTRC Enterprises.
Two layers matter. Library settings govern document libraries. List settings govern lists. Both reach the same versioning screen, but they apply to different content.
Library Settings vs. List Settings
Library settings control document libraries, where files live. List settings control lists, where items like tasks and contacts live. Both open the same versioning options, but the scope differs.
Here is how to reach them:
- Open the library or list.
- Select the gear icon, then Library settings or List settings.
- Under General Settings, choose Versioning settings.
If your team is new to this screen, hands-on training on document management and permissions saves weeks of guesswork. Our SharePoint Fundamentals training walks end users through these exact panels.
SharePoint Major and Minor Versions: What Each One Costs You
SharePoint major and minor versions are not just labels. They decide who sees what, and they multiply your storage.
A major version is a published, numbered copy, like 3.0. A minor version is a draft, like 3.1, visible only to people with the right permissions. Turn on minor versions and coauthors can save drafts without publishing half-finished work to the whole team.
Every minor version is a stored copy, so draft-heavy libraries grow fast. Enable minor versions only where drafting actually happens.
Picking a SharePoint Version History Limit That Holds Up
The right SharePoint version history limit depends on how often a document changes, how far back you need to recover, and how much storage the library can afford. There is no universal number, but there is a predictable mechanism, and understanding it is what separates a limit that holds up from one that quietly deletes the history an auditor later asks for.
How site-level and library-level limits interact
SharePoint enforces version history limits at two layers, and they do not simply add together. The site-level limit acts as a ceiling: it is the maximum number of versions any library on that site can retain, regardless of what the library itself requests. The library-level limit is the local setting an owner chooses inside Library settings > Versioning settings. When both exist, the more restrictive value wins for that library.
Watch out: lowering a site-level limit can permanently delete versions in libraries that were relying on a higher local limit, and there is no undo once expiration runs.
A decision guide grounded in change frequency
Use the document's change pattern, not its department, to choose a limit:
| Document type | Suggested limit | Reasoning |
|---|---|---|
| Policies, contracts, signed agreements | 50 or higher | Auditors and legal teams routinely ask for the full edit trail; the cost of storage is trivial next to the cost of a missing version |
| Project plans and schedules | 25-50 | Frequent edits over a short lifecycle; history older than the project start rarely matters |
| Reference material and published standards | 10-20 | Changes are infrequent and usually deliberate |
| Working drafts and scratch files | 10 | Storage control matters more than deep history |
| Libraries under a retention label or records policy | Do not lower below the retention requirement | Compliance overrides storage savings |
Three questions resolve most disagreements:
- How often does the document change? A file edited daily needs more versions than one edited quarterly.
- How far back would a restore realistically go? If the answer is "last week," a limit of 10-20 is usually enough; if it is "last audit cycle," go higher.
- Is the library under a retention label, record designation, or legal hold? If yes, set the limit to satisfy the policy first and treat storage as a secondary concern.
A common mistake is leaving the default in place everywhere. The default is designed to be safe for the widest range of libraries, not optimal for any single one. Match the limit to the document lifecycle instead, and revisit it when a library's purpose changes.
SharePoint Intelligent Versioning and Automatic Expiration
SharePoint intelligent versioning reduces storage pressure by thinning old versions automatically instead of keeping every copy forever. The mechanism is worth understanding because it behaves differently from a simple version cap, and it interacts with retention in ways that surprise teams.
What intelligent versioning actually does
When intelligent versioning is active, SharePoint keeps more versions of a document while it is being actively edited and progressively fewer as the document ages. A file edited heavily this week may retain dozens of versions; the same file six months from now may retain only a handful of the oldest ones. The result is a version history that stays useful during active work without accumulating years of near-duplicate copies.
This is different from a hard version limit. A limit of 50 means the 51st version pushes out the oldest one immediately. Because time-weighted retention makes version history part of a broader records strategy, Crispin Associates connects these settings to the way organisations manage documents throughout their lifecycle.
Automatic versus manual expiration
Expiration is the process that actually removes old versions. Two modes exist:
- Automatic expiration runs on a schedule you set at the library or site level. It removes versions that fall outside the configured limit or thinning policy without anyone needing to remember.
- Manual expiration means an owner or administrator deletes versions by hand through version history or a script. It is slower and depends on someone remembering to do it.
For most libraries, automatic expiration is the safer operational choice because it runs consistently. Manual expiration is appropriate only when deletions need human review, for example, a library where a mistaken deletion would be costly and the volume is low enough to inspect.
Watch out: expiration deletes old versions permanently. There is no recycle bin for individual versions once expiration has run, so a retention policy that requires that history must be configured before expiration, not after.
How expiration differs from retention labels and records management
This is the distinction most teams miss. Version history limits and expiration control how many copies of a document SharePoint keeps. Retention labels and records management control how long a document and its required history must be preserved for compliance. They are separate systems, and they can conflict.
If a library is covered by a retention label that requires preserving versions, tightening the version limit or enabling aggressive expiration can put the organization out of compliance, even though the storage dashboard looks healthier. Before you enable expiration on any library, confirm whether a retention label, record designation, or legal hold applies. When the two conflict, compliance wins, and the version limit should be set to satisfy the retention requirement first.
Verifying what expiration removed
After expiration runs, owners should confirm the outcome rather than assume it. Open a representative file's version history and compare the version count and dates against the configured limit. If versions you expected to keep are gone, check the site-level limit first, a lower site ceiling overrides a higher library setting, then check whether a retention label is present, then check whether the library's own limit was changed. Documenting the configured limit and the date it was last reviewed gives you a defensible record if an auditor or legal team later asks why a version is missing.
How to Restore Previous Version SharePoint Document Copies
To restore a previous version in SharePoint, open the file's version history, pick the version you want, and restore it. The restore creates a new version rather than erasing the current one, so nothing is lost.
Follow these steps:
- Right-click the file and choose Version history.
- Review the list of versions and dates.
- Select the three dots beside the version you want.
- Choose Restore.
The restored copy becomes the current version. The old current version stays in history. For a deeper look at keeping files organized, read our guide on how to organize documents in SharePoint Online.
Version Limits, Storage Consumption, and Retention Policies
Version limits and retention policies pull in opposite directions. Version limits save storage space. Retention policies preserve records for compliance. When the two conflict, compliance wins.
Check these before you tighten limits:
- Does a retention policy cover this library?
- Do legal or audit rules require full history?
- Is storage consumption actually a problem?
If leadership is nervous about compliance after a scare, our governance and adoption consulting covers SharePoint policies and security compliance.
Troubleshooting Missing or Unexpected Versions
Missing versions usually trace to one of four causes. Check them in order:
- Versioning is off. Confirm it is enabled in library settings.
- The limit is too low. Old versions expire once the cap is hit.
- Expiration ran. Automatic expiration may have removed them.
- Permissions hide history. Users need edit or full control access.
Unexpected versions often come from coauthoring and sync. When several people edit in Office apps at once, SharePoint saves drafts you did not create on purpose. That is normal behavior, not corruption.
Book a Version Control Configuration Review
The hard part is knowing which libraries need which limits, and where retention rules override storage savings.
If your team inherited a sprawling SharePoint environment, a structured review beats guessing. At MTRC Enterprises, we work hands-on alongside your team, transfer knowledge, and work on fixed-price engagements with defined deliverables. You can explore our SharePoint consulting services or schedule a free consultation to talk through your environment. Get started with MTRC Enterprises and give your team settings they can own and maintain.
Version control is not a set-and-forget task. It is a decision about how your organization keeps records, and it deserves a deliberate answer. If you are unsure which libraries carry compliance obligations, start there before you change a single limit.
Frequently Asked Questions
How do you limit version history in SharePoint?
Open the document library or list, go to Settings, then Versioning settings. Under Version History Limits you can keep a set number of major versions, or switch to automatic expiration and set how many major and minor versions to retain within a time window. Apply the limit at the library level for busy sites and leave site-level defaults for everything else. Test on one library before rolling the change out across the tenant.
What is the difference between major and minor versions in SharePoint?
Major versions are numbered 1.0, 2.0, 3.0 and are the copies people see by default. Minor versions are numbered 1.1, 1.2 and are drafts that only show to people with edit or approve permissions when draft item security is turned on. If you never enable minor versions, every save creates a new major version, which burns through storage and version limits faster than a library that uses minor versions for work in progress.
Can you restore an earlier version of a SharePoint document?
Yes. Open the document, select Version history from the context menu, find the version you want, and choose Restore. That version becomes the current one and the version you replaced stays in history so you can roll back again. For a file that was deleted entirely, use the recycle bin first, then the second-stage recycle bin, before assuming the version history is gone.
How do SharePoint version history settings affect storage?
Every retained version is a full copy of the file, so version history can consume significant storage. Version limits and automatic expiration are the two controls that cap that growth. Review your largest libraries first, set a major-version limit that matches how far back your team actually needs to look, and pair it with a retention policy so compliance requirements and storage costs do not pull in opposite directions.
