Keep the newest N
Set how many earlier versions to keep per file. Everything older is removed, and the current version is never touched.
Every saved version of every file is charged against your storage. Version Trimmer removes the history you no longer need, on rules you set once, across the libraries you pick, a CSV of URLs or every SharePoint site in the tenant. Removed versions go to the recycle bin unless you say otherwise.
The Version trimming report is free on every plan. Live trimming comes with Recycle Master, from USD 300 a year. Pricing
It deletes the older versions of files and leaves the current version alone. SharePoint can do this itself, but only file by file in the Version history panel, gradually through a lower library limit, or permanently through a PowerShell trim job. ShareMaster runs the same clean-up from a window, with finer rules, a free report of the saving, and the recycle bin as a safety net.
| Version history panel | Lower the library limit | Microsoft trim job | ShareMaster Version Trimmer | |
|---|---|---|---|---|
| Removes history that already exists | One version of one file at a time | Gradually: up to 20 surplus versions each time a file is saved | Yes, as a queued background job | Yes, in one run |
| Who runs it, and how | In the browser, file by file | Library settings, set by the site owner | PowerShell, queued by an administrator. Tenant-wide jobs are in preview and need an extra licence | The desktop app, signed in with access to the content you trim |
| Scope | One file | One library | Site, library or OneDrive | Sites, libraries or folders you tick, a CSV of URLs, or every SharePoint site in the tenant |
| Rules | You choose each version | Version count, or automatic limits | Age (30 days minimum), major version count, or automatic | Newest N, older than a date, most per day, hours apart, skip recently modified files, extension, file name wildcard |
| See it before it happens | You can see the version | No | What-if analysis against a version report CSV | Excel report per file, same rules, free on every plan |
| Can you get versions back? | Yes, from the site recycle bin | No, deleted permanently | No, deleted permanently | Yes by default, from the recycle bin. Permanent delete is opt-in |
The trim job is the right tool when you need Microsoft's automatic algorithm applied to existing files, or a OneDrive account trimmed. Version Trimmer is for when you want a per-file record of what will go, rules finer than a count or an age, or the chance to undo a rule that turned out too aggressive.
Set how many earlier versions to keep per file. Everything older is removed, and the current version is never touched.
Skip files modified after a date, only remove versions older than a date, and target file types or names with a wildcard.
Cap how many versions survive per day, which tames AutoSave bursts, or keep versions at least a set number of hours apart.
Removed versions go to the recycle bin by default. Permanent delete gives the storage back the same day, behind its own red warning.
Start with the Version trimming report. Point it at a site, choose the same rules you would trim with, and it downloads an Excel file listing each file, the versions those rules would remove and the space that would come back. It writes nothing to SharePoint, and it is free on every plan, including the free Community licence, so you can size the saving across the whole estate before deciding anything.
If you would rather start from version counts, exporting SharePoint version counts to Excel shows which files carry the most history.
A tenant's SharePoint storage is one shared pool: 1 TB plus 10 GB for each licensed user. Every version of every file is counted in it, not just the file you see. New document libraries keep up to 500 major versions of each file, so a spreadsheet saved a few times a day can hold hundreds of copies of itself. Once the pool is used up, Microsoft charges for extra storage (current extra storage pricing), and that charge recurs every month. How version history fills SharePoint storage works through the arithmetic, and co-authored files are the worst offenders: why co-authoring multiplies versions.
The obvious fix is to lower the limit in the library's versioning settings. That works slowly. SharePoint applies the new limit to a file when it is next saved, removing at most 20 surplus versions per save, and those removals are permanent. Files that nobody edits keep their whole history, and those are often the biggest. Setting the SharePoint version limit walks through the settings themselves, and what intelligent versioning changes covers Microsoft's automatic mode.
Every version you keep is a version a migration has to copy, so trimming first shortens the move and keeps the destination lean: see trimming SharePoint versions before a migration. Trimming is also safer to plan once you stop counting on version history as a backup, which it was never designed to be: why version history is not a backup. For a step-by-step walkthrough of a first trim, read how to trim SharePoint version history.
Recorded in 2023 on an earlier version of ShareMaster. The screens and steps have changed since.
Try ShareMaster free for 14 days, no credit card. The Version trimming report is not limited on the trial, so you can measure the saving across every library before you decide.
Last updated