How to reduce SharePoint storage without deleting files
Six levers, ranked by the space each one typically returns, with the measurement step that tells you which applies to your tenant. Every step is reversible or non-destructive to current file content.
Last updated · By Sean Regan
Quick answer
What is the fastest way to reduce SharePoint storage without deleting files?
Lower version limits on read-mostly libraries, move cold files and folders to Microsoft 365 Archive, empty both recycle bins, consolidate duplicate large files, and retire sites that only hold copies. In a typical 1 TB tenant these five levers return 200–400 GB, and none of them deletes a file anyone is using.
The procedure, with numbers
Worked against a 1 TB tenant that is 92% full. Percentages are of billed storage and reflect what we have measured across tenants; substitute your own once you have a per-file report.
- Measure per file, not per site (0 GB, 30 minutes). Get size, modified date, age in days and version count for every file in your five largest sites. Without this you will optimize the wrong library.
- Lower version limits on read-mostly libraries (100–300 GB). Set the major-version limit to 50 on finance archives, image libraries and policy repositories. A 20 MB deck with 300 versions bills ~6 GB; cutting to 50 versions returns ~5 GB from that one file.
- Move cold content to Microsoft 365 Archive (100–250 GB). Anything untouched for two years. Archive bills at roughly a quarter of the active rate, so 200 GB archived saves about $360 a year at list add-on pricing.
- Empty both recycle bins (10–50 GB). Deleted content bills for up to 93 days; the second-stage bin is the one people forget.
- Consolidate duplicate large files (30–100 GB). Sort by size, group by file name, pick one owning location, link from the rest.
- Re-measure two days later. Tenant figures lag by up to 24 hours. Two dated reports showing the same site materially lighter is what funds the next round.
Steps 2 to 5 are changes you make in SharePoint itself. Step 1 and step 6 need a per-file report, which the admin center cannot produce — see the tooling note below.
Step 0 — measure, or you will guess wrong
The SharePoint admin center gives you one storage number per site and no explanation. Teams routinely spend a week deleting files in the wrong library because the actual weight was version history in a different one. A per-file report with size, modified date, age in days and archival tier turns the whole exercise into arithmetic — and Smart Storage Analyzer produces it read-only from a SharePoint page, free and with no PowerShell.
The six levers, ranked
Lower version limits on read-mostly libraries
SharePoint bills every version at its full size for most file types. A library keeping 500 major versions of large decks can be several times the size of its current content. Drop the limit on finance archives, image libraries and policy repositories first.
- Typical reclaim:
- 10-30% of billed storage
- Effort:
- Low
Move cold files, folders and sites to Microsoft 365 Archive
Archive storage bills at a fraction of the active rate, and it can be applied to individual files and folders as well as whole sites. Rank candidates by the size of their Very Stale content rather than by site name.
- Typical reclaim:
- 10-25% of billed storage
- Effort:
- Low
Empty the first- and second-stage recycle bins
Deleted content keeps consuming quota for up to 93 days. If you have just finished a cleanup, the reclaim does not land until the second-stage bin is emptied or expires.
- Typical reclaim:
- 1-5% of billed storage
- Effort:
- Very low
Consolidate duplicate large files
The same 400 MB video living in five team sites bills five times. Sort a scan report by size, group by file name, and pick one owning location — then link to it from the others.
- Typical reclaim:
- 3-10% of billed storage
- Effort:
- Medium
Retire sites that only hold copies
Migration staging sites, department sites replaced two reorganizations ago, and 'temp' sites nobody owns. Confirm the content exists elsewhere, then archive rather than delete so the reversal path stays open.
- Typical reclaim:
- 2-15% of billed storage
- Effort:
- Medium
Prove the reclaim and keep it
Re-run the scan and compare it against the earlier one. Two dated reports showing the same site materially lighter is what converts a one-off cleanup into a recurring, funded governance task.
- Typical reclaim:
- —
- Effort:
- Low
What not to bother with
Asking users to "clean up their files" returns almost nothing and costs goodwill. Blanket deletion policies stall in review. Buying add-on storage before measuring locks in a recurring cost for content that was 30% versions. Do the measurement, then the two big levers, and only then consider quota.
Frequently asked questions
How do I reduce SharePoint storage without deleting files?
Work the levers in order of GB returned per hour of effort: lower version limits on read-mostly libraries, empty both recycle bins, move cold files and folders to Microsoft 365 Archive, consolidate duplicate large files to a single owner, and remove abandoned sites that only hold copies. None of these remove a current file that someone is using.
Which lever frees the most space first?
In almost every tenant we have measured, version history is the largest single line item, followed by cold content that belongs in Microsoft 365 Archive. Both are reversible in the sense that no live file content is lost, which is why they clear governance review faster than a deletion project.
How do I find out what is actually using the storage?
The SharePoint admin center reports one number per site and no breakdown. Run a free scan with SharePoint Smart Storage Analyzer to get a per-file report with size, created and modified dates, age in days and an archival tier, plus a treemap of the biggest folders. Tree View and List View always show per-file version-history size; Storage Report has a separate option enabled by default.
How long does reclaimed SharePoint storage take to show up?
Not immediately. Removed versions and deleted items pass through the first-stage and second-stage recycle bins, and tenant storage figures in the admin center refresh on a delay of up to about 24 hours. Plan to measure the before and after a couple of days apart.
Is lowering the version limit risky?
Lower it deliberately and it is the safest lever available. Excess versions are trimmed on the next SharePoint maintenance pass and the current version is never touched. Keep higher limits on libraries with a genuine legal or audit need for full revision history, and check retention or eDiscovery holds before changing anything.
Do I need PowerShell or an admin role to measure this?
No. SharePoint Smart Storage Analyzer is an SPFx web part that runs read-only in the browser using the signed-in user's permissions — no modules, no service account, no data leaving the tenant. You do need admin rights to change versioning settings or to archive content.
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.
Estimate version-history overhead and the savings from a lower version limit.
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.