How to Trim SharePoint Version History

SharePoint's default versioning settings create a new version every time a file is saved, with no upper limit on how many versions accumulate. 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. With no version cap set, every edit from the last five years may still be sitting in version storage.

The problem is that the standard SharePoint admin center storage report shows total usage per site but does not break out how much is version history versus live content versus recycling bin. Without that breakdown, it is easy to underestimate how much version history has accumulated and impossible 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 Report Master across the sites you want to clean up. The Excel export shows:

Total storage per site, split into live content, version history, and recycling bin.
Average version count per library.
Libraries where version counts or version storage are disproportionately high.

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.

Focus on the outliers. In most environments, 10 to 20 percent of libraries hold 80 percent or more of the version storage. Find those libraries with Report Master before you start the trim.

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.

Get sign-off before trimming. Always confirm in writing with the business owner that older versions are not needed for compliance, audit, or regulatory reasons before running a version trim. Some industries treat version history as part of the document control 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 the sites and libraries you want to process. You can target a single library, all libraries in a site, or multiple sites at once.
Enter your keep count. The trimmer will retain the most recent n versions per file and remove all older ones.
Click Run. 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.

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 removes versions 11 through 120 from the oldest end and keeps the 10 most recent.

Run trims outside business hours. Version deletion calls the SharePoint API and counts against your tenant's throttle limits. For large trim operations spanning many thousands of files, scheduling overnight reduces the risk of hitting Microsoft's concurrency limits during the business day.

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 logs a result for each file processed. If any files were skipped (for example, because they were checked out at the time), the log identifies them for a follow-up run.

Step 5: Set a version limit going forward

A trim fixes the historical accumulation, but without a 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.

Two ways to apply limits:

Through SharePoint: open the library, go to Library settings, then Versioning settings. Set a maximum number of major versions.
Through Explore Master: Explore Master lets you view and update version settings across multiple libraries in bulk, which is useful if you want to apply a consistent keep policy across 20 or 30 libraries at once rather than clicking through each library individually.

How much storage can you expect to reclaim?

In environments without a version cap, trimming to a keep count of 10 to 15 typically reduces version storage by 60 to 85 percent. Total site storage usually drops by 30 to 60 percent, depending on how much of the quota was occupied by versions rather than live content.

For a 500 GB tenant at 90% utilisation, a version trim can realistically recover enough headroom to avoid a storage purchase for six to twelve months, depending on content growth rate.

For context on how tenant storage quotas work, see the SharePoint Online storage limits reference.

Related guides

Try ShareMaster free for 14 days