Content reviewed: 12 October 2026
Measure what consumes storage before changing version limits. Separate future settings from cleanup of existing history. Microsoft explains these operations in the version history limits overview.
File size is only part of storage use
A file’s current size does not show all storage associated with it. Previous versions and retention mechanisms can consume additional space. Measure actual site and version storage rather than multiplying current file size.
Break consumption down by sites and libraries. Identify growing business processes and their owners. A sales library of actively edited proposals may need different rules from published reference material.
Include automation that overwrites files or uploads under the same name. High consumption can reflect a workflow creating more versions than the business needs.
A full site or a full tenant pool
In SharePoint admin centre → Active sites, check total and available organisation capacity. With manually managed limits, a site can reach its own quota while the shared pool still has space. Raising that site limit does not purchase more capacity. Microsoft notes that usage figures exclude changes from the last 24–48 hours. Compare completed cleanup with a later measurement, not just the immediate number.
New defaults do not clear old history
Organisation defaults apply to newly created libraries. Changing them does not update existing libraries or delete their history. Existing-library rules require a separate targeted change.
Site-level settings also distinguish library policy updates from trimming. Report “policy updated” and “storage released” separately. Changes to a library’s expiration and count settings behave differently, as described below.
Otherwise an administrator may conclude that the setting failed, or promise storage savings before cleanup has actually happened.
What each setting changes
| Change | Effect | Check |
|---|---|---|
| Organisation default | New libraries inheriting the organisation default | Existing libraries can remain unchanged. |
| Expiration in an existing library | New historical versions receive the new age limit | Existing versions do not automatically receive new expiry dates. |
| Count in an existing library | Excess history is gradually trimmed as files are updated | This is not instant bulk cleanup. |
| Separate trim job | Asynchronous removal under the selected mode and scope | Impact report, completion and preservation exceptions. |
The FAQ describes roughly 20 deletions per file update after a count reduction. Reducing 500 to 300 therefore need not remove all 200 versions on one edit. This is not a timing guarantee. Where manual policy combines count and age, exceeding either can trigger deletion; “500 versions and 365 days” does not promise all versions for a full year.
Build the initial inventory
| Area | Measure | Decision |
|---|---|---|
| Sites | Consumption and growth | Priority |
| Libraries | Purpose and owner | Required history |
| Versions | Storage and age | Impact-report candidates |
| Retention and holds | Preservation requirements | Cleanup restrictions |
| Automation | Repeated overwrites/uploads | Process changes |
| Recovery | Required older states | Approved history |
Fill the inventory from current data. Silence from users is not evidence that old versions are unnecessary.
Automatic and manual modes
Automatic mode uses Microsoft’s version-storage algorithm. Manual settings specify major-version counts and optionally expiration. Choose a mode against the required recovery history.
A team that routinely restores week-old drafts needs a different test from a library of long-term approved documents.
A simple default can work, but exceptions need a documented purpose and owner. A storage reduction that removes necessary recovery options is not a successful change.
Run an impact report first
Identify which versions the proposed rules would affect before bulk cleanup. An impact report separates a policy change from permanent removal of history.
Show the owner the affected business content, version ages and recovery consequences. Approval should address that scope, not just “delete old versions”.
Check retention and records before estimating savings; preservation requirements may prevent versions from being deleted.
Policies, labels and records differ
| Content state | Documented behaviour |
|---|---|
| Retention policy or eDiscovery hold | Version limits yield to preservation; trimming can mark expiry and defer deletion. |
| Retention label without a policy or hold | Limits can still apply; a label does not automatically block every cleanup. |
| Content marked as a record | Version deletion is blocked. |
These distinctions follow the version-limit protection exceptions. Deferred deletion can take effect when a hold ends or retention expires. Do not promise immediate savings for all report candidates or remove preservation solely to gain storage.
Trimming bypasses the recycle bin
Trim jobs permanently delete versions, unlike ordinary user deletion into the recycle bin. Stopping a running job does not reverse completed deletions. Use a What-If report and verify required recovery first. Manual age-based trimming also has restrictions: it does not process the trailing 30 days, and the documentation states that versions created before 1 January 2023 are deleted. Check that behaviour in the report rather than assuming old versions will remain.
Tenant-wide trimming is labelled private preview in the current instructions, with a separate SharePoint Advanced Management or Copilot prerequisite. Do not present it as a generally available command for every tenant. For available site/library operations, track the asynchronous job; timing depends on version volume and service processing.

Example: video and Office documents
An illustrative marketing site stores videos and working documents. Videos are large and replaced several times, while editors frequently compare changes in text documents.
Prepare separate reports by business purpose and file type. Video owners confirm required history; document editors confirm review and recovery needs. Size alone does not decide what to delete.
File-type version limits support audio, video and outlookpst categories. An override replaces the library default for that category; it is not an additional limit layered on top. Other file types keep the normal policy. It is not a filter for arbitrary extensions.
Illustrative report: 80 GB of versions match the proposed criteria. If preservation prevents deletion of 20 GB of that amount, do not report all 80 GB as confirmed savings. Track estimated impact, actual deleted versions and the later measured storage change separately. These are our illustrative numbers, not observed customer results.
A verifiable change workflow
- Record current policy and consumption.
- Generate a report for the proposed limits.
- Confirm business history and preservation needs.
- Update future policies in the intended scope.
- Check asynchronous updates have completed.
- Run approved cleanup only in the chosen scope.
- Verify consumption and available recovery versions.
Policy updates and cleanup can be asynchronous. Track job status and the result; submitting a request does not mean the change has finished.
When additional storage makes sense
If required content and history account for the growth, buying capacity may be appropriate. The review does not have to produce a saving.
Compare capacity costs with administration and the risk of unsuitable cleanup. A small one-off reduction may not address continued growth; budget for the trend as well as today’s warning.
More capacity does not fix a workflow that creates unnecessary history. Correct that process too.
Explain recovery changes to users
Explain which versions remain available and whom to contact for recovery. Users need to understand changed recovery options rather than the term “trimming job”.
Prepare a short document-restore guide and test it with a representative user. The business owner confirms that the remaining history supports the work.
Frequently asked questions
Do new organisation defaults delete existing versions?
No. They apply to new libraries; existing policies and history require separate consideration.
Should every library use the lowest count?
Not without checking required history and recovery needs. Measure the consequences first.
Can trimmed versions be restored from the recycle bin?
No. Trimming jobs bypass the recycle bin. Recovery would require a previously established backup and a verified supported restore method.
Is the largest-file list enough?
No. Include version storage, libraries, retention and the process generating content.
Keep evidence of the result
Record future policies, completed cleanup and the growth trend. This makes storage decisions explainable without promising to fix SharePoint with one setting.








