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. Two read-only ShareMaster reports, both free on every plan, give you that picture:
- Folder inventory: one row per folder on the sites, libraries or folders you pick, with its total size, version history included, and its file count, so the heavy libraries stand out.
- Version trimming report: run it on those libraries with the keep rule you are considering, and it downloads an Excel of exactly what would be trimmed from each file and how much storage that would reclaim. Nothing is removed.
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 ShareMaster's Version trimming
Once you have your target libraries and keep count, open Version trimming in ShareMaster. The SharePoint version trimming tool page sets out every rule it offers and how it compares with SharePoint's own options.
- Sign in to the target tenant.
- Select what to process: sites, libraries or folders you pick, a CSV list, or the whole tenant.
- Enter your keep count. Version trimming keeps the current version plus the newest n earlier versions and removes the rest. Optional rules keep at most a number of versions a day, keep versions a minimum number of hours apart, only remove versions before a date, skip recently modified files, or narrow the run by file name or extension. A version is removed only when every rule you switched on agrees.
- Check what goes. A run across several libraries shows a preview of what each file would lose and asks before removing anything. A single library is trimmed as it is scanned once you confirm, so if you want the list first, run the Version trimming report with the same rules.
- Run it. By default the removed versions go to the recycle bin, so they stay recoverable for the retention window; a permanent delete that frees the space at once is an option, behind its own warning. Large libraries may take from several minutes to several hours depending on file count.
Version trimming 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 the Folder inventory again on the same sites. Compare the 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.
Every run is kept in ShareMaster's Report history with an Excel report of what it did, so you can open it again later without re-running anything. If you sent the versions to the recycle bin, they keep counting against storage until the bin is emptied or the retention window passes.
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 Easy Settings: search for the version limit and set it on a library, or set the limit a site gives libraries created from now on, without clicking through the settings pages. Lowering a library's limit permanently deletes the versions above it, so trim first if you want them in the recycle bin instead.
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.
Related guides
Last updated