SharePoint's default versioning settings create a new version every time a file is saved and keep up to 500 of them per file. On an active document library, that means a 10 MB file can quietly consume 500 MB or more in version history over a few years. This guide walks through how to find, measure, and trim that history without deleting any live content.
Why version history grows so fast
SharePoint Online enables versioning by default on document libraries. Each time a user saves a file, opens it in the browser editor, or syncs a change through OneDrive, SharePoint stores the previous copy as a version. Under the default 500-version cap, a file edited a few times a week can still have every edit from the last few years sitting in version storage.
The problem is that the storage figures in the SharePoint admin center show total usage per site without breaking out how much is version history. Microsoft does offer a version storage usage report, but it is queued per site or library through PowerShell. Without a breakdown, it is easy to underestimate how much version history has accumulated and hard to target it selectively.
Step 1: Audit current version storage
Before trimming anything, get a clear picture of where the version storage is concentrated. Run the Report Master storage report (Site Storage Metric for one site, Tenant Storage Metric for several) across the sites you want to clean up. The Excel export shows:
- Per library: total size, the size of the current files, and the amount a trim would save.
- The largest files, with their version size alongside their file size.
- A per-file breakdown of version numbers and sizes, so outliers stand out.
With this data, you can target the libraries that will give you the most storage back from a single trim operation rather than running blanket trims across every site.
Step 2: Decide on a version keep policy
A version keep policy defines how many versions to retain per file. Versions older than the keep count will be deleted. Choosing a keep count involves balancing storage savings against the practical and compliance needs of the business.
Common keep counts by organisation type
- General business libraries (HR, internal comms, general documents): 10 to 15 major versions is a comfortable default. Most users never look back more than a few revisions.
- Finance and legal (non-regulated): 20 to 30 major versions provides a longer audit trail without keeping everything.
- Regulated industries (healthcare, legal document control, financial services): check with your compliance team first. Some document control frameworks require specific version retention as part of the record.
Step 3: Run Space Master Version Trimmer
Once you have your target libraries and keep count, open Space Master and navigate to the Version Trimmer.
- Connect ShareMaster to the target tenant.
- Select what to process. The Version Trimmer works on the libraries or folders you pick in one site; the Bulk Version Trimmer works on every document library in the site collections you pick.
- Enter your keep count under Retain some versions?. The trimmer keeps the current version plus the most recent n earlier versions and removes the rest. Optional rules cap versions per day, keep a minimum number of hours between retained versions, limit the run by file name, or only delete versions older than a date.
- Run the Version Trimming Report from the Reports menu first. It applies the same rules without deleting anything and lists what would go.
- Click Execute Trimmer. The trimmer processes files in batches and logs progress as it goes. Large libraries may take several minutes to several hours depending on file count. Deleted versions do not go to the recycle bin.
The Version Trimmer does not touch the current (latest) version of any file. If a file has 120 versions and your keep count is 10, it keeps the current version and the 10 before it, and removes the 109 older ones.
Step 4: Verify the results
After the trim completes, run Report Master again on the same sites. Compare the version storage figures before and after to confirm the expected reduction. Spot-check a few files in the trimmed libraries to verify that:
- The current version of each file is intact and opens correctly.
- Version history in SharePoint shows the expected number of remaining versions.
- No files were skipped or partially processed.
Space Master writes a CSV with a row per file: the versions removed, the space saved and the file size. Be aware that a file checked out at the time is checked in by the trimmer as a major version before it is trimmed, so warn people with work in progress before you run it.
Step 5: Set a version limit going forward
A trim fixes the historical accumulation, but without a lower version limit in place, the library will rebuild the same problem over the next few years. SharePoint lets you set a version limit at the library level, and from PowerShell for a whole site.
Two ways to apply limits:
-
Through SharePoint: open the library, go to Library settings, then Versioning settings. Set a maximum number of major versions (the page accepts 100 or more), or
Set-SPOSite -MajorVersionLimitwith-ApplyToExistingDocumentLibrariesfor every library in a site. - Through ShareMaster's Settings Updater: it writes the same count limit into all the document libraries across a chosen set of sites, which is useful if you want a consistent policy across many sites without clicking through each library. It needs a SharePoint Administrator account.
How much storage can you expect to reclaim?
It depends on how many versions your files hold, which is why the report run matters: the Version Trimming Report lists the space each file would give back before anything is deleted. For a sense of scale, Microsoft's own examples for its automatic version limits show version storage falling by around 94 to 96 percent against a plain 500-version count limit.
How much of that turns into tenant headroom depends on how much of your quota is version history rather than current files, and on how fast content keeps growing.
For context on how tenant storage quotas work, see the SharePoint Online storage limits reference.