SharePoint version history storage calculator
Last updated · By Sean Regan
Estimate your version overhead
Adjust the six inputs to match your library or site. Everything is calculated in your browser — nothing is sent anywhere.
Files in the library or site you are sizing.
Office documents average 1-3 MB; design and media libraries run far higher.
Files uploaded once and never changed carry no version overhead. In most libraries this is 20-40%.
An average across edited files, not the library limit. Most tenants land between 8 and 20; only a few hot documents approach 100+.
Older versions are usually smaller than today's file, and shredded storage plus co-authoring trims what each version writes. 50-70% is typical.
What you would lower the library limit to. 50-100 suits most document libraries, though the realized average will be lower.
Current files
97.7 GB
Version history
246.1 GB
72% of total storage
Reclaimable
87.9 GB
at a 10-version limit
Annual value
$211
$18/mo at $0.20/GB
The dollar figures value the reclaimed space at the Microsoft list rate of $0.20/GB/month for extra SharePoint storage. If your tenant is inside its pooled allowance you will not see an invoice change — the value is in deferring a storage purchase. Moving the same content to Microsoft 365 Archive at $0.05/GB/month instead of deleting it would be worth about $158 a year.
See the tenant-wide picture
Check your total included quota (1 TB + 10 GB per licensed user), overage cost, and months until full with the storage cost calculator.
How the estimate works
Each retained major version is counted against your quota as a separate logical copy of the file, so overhead scales with the number of versions kept.[1] The trap in naive estimates is applying the library's version limit — 500 by default — to every file. Real libraries follow a long-tail distribution: a large share of files have zero or one version, a moderate share have a handful, and a small number of hot documents carry hundreds. Averaged across edited files, most tenants land somewhere between 8 and 20 versions, which is why the defaults here are modest.
Three inputs dominate the result: the share of files that are actually edited, the average number of versions retained, and the average size of a retained version relative to today's file. A library of scanned PDFs uploaded once has almost no version overhead regardless of the limit. A shared planning workbook edited daily for three years may be 95% version history.
Shredded storage: what it changes and what it does not
Shredded storage splits a document into BLOB chunks in the content database, so saving an edit writes only the changed chunks rather than re-uploading the whole file. It was introduced to cut write amplification, database churn, and upload traffic — and it is why saving a small change to a 50 MB deck is fast.
What it does not do is change how the version is counted. SharePoint Online meters and reports each retained version as a full logical copy of the file at that point in time, and that is the number that shows up in site storage metrics and against your tenant quota. Shredding is a physical storage optimization; quota accounting stays logical. So do not expect version history to be "free" because of shredded storage.
Where it does help the estimate: the average retained version usually measures smaller than the current file, because documents grow over their lifetime and because co-authoring auto-save produces many small intermediate versions rather than full-size snapshots. That is the reason the calculator exposes an average version size factor instead of assuming every version equals today's file size — set it to 100% if you want the conservative worst case.
Get the real number, not an estimate
Use this page to size the opportunity before you touch a library setting, then measure it. SharePoint Smart Storage Analyzer always shows version-history size in Tree View and List View. Storage Report has a separate Include Version History Size option, enabled by default: every measured file reports its retained-version bytes next to current size, and the report totals them in a separate tile. Folder rows remain current-file-only because SharePoint offers no recursive version-history rollup.
Once you know which libraries carry the overhead, follow the steps in lower version limits to reclaim storage and remember that trimmed versions sit in the second-stage recycle bin for the remainder of the 93-day window before the bytes come back.
Want SharePoint to trim for you? Our walkthrough on trimming version history with Automatic limits covers the retention schedule and the one PowerShell command for existing sites that reclaimed roughly 30–40% of our storage.
FAQ
- How much storage does SharePoint version history use?
- A realistic estimate is (files that actually get edited) × (average versions retained − 1) × the average size of a retained version. Most libraries have a long tail of files with zero or one version and only a handful with hundreds, so a realistic average is closer to 10-20 versions, not the 500-version library limit.
- What is shredded storage and does it reduce version size?
- Shredded storage splits a file into BLOB chunks so an edit only writes the changed chunks. It reduces write amplification and network traffic, but SharePoint Online still reports and bills each retained version as a full logical copy of the file. Office co-authoring and delta sync mean the average retained version usually measures somewhat smaller than the current file, which is why the calculator applies a version-size factor.
- Does lowering the version limit free storage immediately?
- Trimming versions moves the removed versions into the recycle bin first. The bytes are reclaimed once the second-stage recycle bin is emptied or the 93-day retention window elapses.
- How do I see the real version-history size instead of an estimate?
- Run Smart Storage Analyzer. Tree View and List View always report retained-version bytes per file alongside current-file size. For a whole-site total, leave Include Version History Size enabled in Storage Report. Most libraries return version data in bulk; only unsupported lists need per-file fallback measurements.
- What is a sensible version limit?
- Most document libraries are well served by 50-100 major versions, or by Version History Limits Automatic, which keeps all versions from the last 30 days and thins older ones by age.
References
- [1] Document library version history limits — Microsoft Learn
- [2] Manage site collection storage limits — Microsoft Learn
Related
Looking for the other calculators? They all live on the tools & calculators page.
The SharePoint storage guides
Seven pages, three jobs: understand how storage is counted, measure what you actually have, then act on it.
Understand
Measure
Free SPFx web part: treemap, per-folder totals and per-file version-history size.
Seven steps to measure per-file version-history size, trim it safely, and prove the reclaim.
Admin center, Storage Metrics, PowerShell and Smart Storage Analyzer compared.
Get your first result in about 10 minutes
Download SharePoint Smart Storage Analyzer, follow the step-by-step install guide, and run it against a real site the same afternoon. Nothing to license, nothing to renew.
- Download the .sppkg package from the latest release.
- Upload it to your tenant App Catalog.
- Add the web part to a SharePoint page.
Email me when a new release ships
No marketing spam. One short email when a new release ships. You can unsubscribe anytime.
