How to Set Version Limits in a SharePoint Library
Version limits let SharePoint automatically manage version history at scale. Set them once and version cleanup becomes invisible.
What it is
Version limits are a library-level setting that tells SharePoint: ‘keep the last N major versions and the last M minor versions’. Once a file goes beyond those limits, the oldest versions are automatically removed. This is the right way to manage version cleanup in most libraries — predictable, consistent, no manual intervention.
Default version limits are typically generous (often 500 major versions). For most libraries, this is fine — storage isn’t usually the bottleneck. But for very high-churn libraries, or libraries with legitimate compliance constraints, you might want to tighten the limits, or in some cases, loosen them.
The decision is about balancing storage, audit trail needs, and what level of history is actually useful. A meeting notes library might be fine with 20 versions per file. A controlled policy library might need 100 majors with no automatic deletion at all. Set them once, document the choice, and move on.
When to use this
- When you’re setting up a new library and want to lock in version behaviour.
- When a library’s version history is growing faster than expected.
- When you’re aligning a library with retention or compliance requirements.
- When you want predictable, automated version management instead of manual cleanup.
How to do it
- Open the library and go to Library settings.
- Open Versioning settings.
- Set how many major versions to keep (e.g. 50, 100).
- If using minor versions, set how many to keep per major version.
- Save the settings.
- Test on a non-critical library first if you’re tightening from generous defaults.
- Communicate the change to library owners and authors.
- Review storage and version behaviour after a few weeks.
Best practices
- Match limits to library purpose. Working drafts: tight limits. Controlled documents: generous limits.
- Document the limits in your governance. ‘This library keeps last 50 majors’ should be written down somewhere people can find.
- Don’t set limits below your retention requirement. If you’re required to keep 7 years of versions, the library has to support that.
- Combine limits with approvals for controlled libraries. Approval ensures only meaningful versions are major; limits keep the count manageable.
Common mistakes
- Setting too-tight limits on important content. You might lose history before you realise the limit was too low.
- Setting different limits in libraries that should match. Inconsistency confuses users and complicates governance.
- Forgetting to set limits at all. Defaults work for most cases but might not suit your specific workload.
The Governance Starter Kit gives you the plain-English governance system for real organisations. The 5 governance domains, the Roles & Responsibilities Matrix, the Library Standards Audit, the Monthly Governance Routine — and the 5-day Start This Week plan.
Get the Governance Starter Kit — $29 →FAQ
How do I set version limits on a SharePoint library?
Go to Library Settings -> Versioning settings. Set ‘Keep the following number of major versions’ (typical: 50) and ‘Keep drafts for the following number of major versions’ (typical: 10). Save. SharePoint enforces the limit automatically — old versions get removed as new ones are created.
What’s a good SharePoint version limit?
For most libraries: 50 major versions, 10 minor versions per major. For high-edit-frequency files (working documents): 25/5. For archive libraries where every version matters: 500/100 (or unlimited). The right number balances rollback safety against storage cost.
Does changing SharePoint version limits delete existing versions?
No — reducing the limit doesn’t immediately delete versions over the new limit. SharePoint enforces the new limit on future versions only. To clean up existing excess versions, run a manual cleanup or a Power Automate flow. The setting prevents future bloat; it doesn’t fix existing bloat.
Should I disable SharePoint versioning to save storage?
Almost never. Versioning is one of SharePoint’s most valuable features — it makes accidental overwrites impossible and gives you a complete audit trail. Set strict limits instead. Saving 20% storage by disabling versioning is rarely worth losing the safety net.