Every version of every file in SharePoint Online counts against your tenant storage quota. A 500-user tenant left to run unchecked for two years can accumulate hundreds of thousands of redundant file versions - often five to ten times the actual working data size. The good news: most of that storage is recoverable within a few hours, without touching live files.
This guide walks through five concrete steps, ordered by typical impact, to reduce SharePoint Online storage quickly and safely.
What Counts Against Your SharePoint Storage Quota?
Before deleting anything, it helps to understand what Microsoft counts against your pooled tenant storage. The answer is broader than most admins expect.
- Current file versions - the live copy of every document, image, video, and page.
- Previous versions - every historical version retained in a document library. With a 500-version default limit, a single frequently-edited document can accumulate dozens of gigabytes in version history alone.
- First-stage recycle bin - files deleted by users but not yet permanently removed. Retained for up to 93 days.
- Second-stage recycle bin - items cleared from the user-level bin that move to the site collection recycle bin for the remainder of the 93-day window.
- Metadata and list attachments - typically a small fraction of total storage, but worth noting for large lists.
Version history and the recycle bin are the two biggest surprise contributors. A document revised 200 times may have 200 stored versions, each counted separately against your quota.
Step 1: Identify the Biggest Storage Consumers
Reducing storage without data is guesswork. Start by generating a storage report across your tenant to see which site collections, libraries, and individual files are responsible for the most space.
What to look for first
- Site collections over 50 GB - prime candidates for version cleanup
- Document libraries with high version counts (check average versions per file, not just total size)
- Individual files over 100 MB - images, videos, and PST files are common culprits
- Sites with no activity in the past 12 months - these may be safe to archive or delete
ShareMaster's Report Master exports a full storage utilisation breakdown to Excel in one click, including version counts per library. That gives you a prioritised target list before you change anything.
The Microsoft 365 admin centre alternative
The Microsoft 365 admin centre shows per-site-collection storage under SharePoint > Active sites. It provides a useful high-level view but does not break down storage by version history or show file-level detail. It tells you which sites are large; it does not tell you why.
Step 2: Trim Version History in Bulk
Version trimming is almost always the single largest storage saving. Most documents only need the last 5 to 10 versions for any practical purpose, yet SharePoint's default 500-version limit means a busy library can accumulate thousands of versions per file over time.
Using PnP PowerShell, version trimming is possible - but slow. You iterate over every site, library, and file. For a tenant with tens of thousands of files, that script can run for days and is prone to throttling errors from the Microsoft 365 API.
ShareMaster's Version Trimmer does the same work graphically. Choose which sites and libraries to target, set a retention rule such as "keep last 10 major versions", preview exactly how much storage will be freed, then run. It handles Microsoft 365 throttling automatically and processes files in parallel.
- Open ShareMaster and navigate to Space Master.
- Select Version Trimmer.
- Choose the site collections to target, or select all.
- Set your version retention policy (for example, "keep 10 major versions").
- Review the projected storage saving in the preview pane before committing.
- Click Trim Now and monitor progress in the activity log.
For large tenants, a version trim run typically recovers 30% to 70% of total tenant storage. See the dedicated version trimming guide for a deeper walkthrough including library-level targeting and scheduling.
Step 3: Compress Oversized Images
Images uploaded directly to SharePoint - product photos, site banners, scanned documents, presentation exports - are often uncompressed or only lightly compressed. A single high-resolution scanned PDF can run to 20 MB. A folder of 500 such files represents 10 GB that can often be halved with no visible quality loss.
ShareMaster's Image Reducer scans selected libraries for images above a size threshold you set, then recompresses them in place. It replaces the original file with the smaller version, leaving the filename, metadata, and version history intact. Users rarely notice any quality difference for document-quality images.
This step is unique: it shrinks existing files without deleting any data. That makes it safe to run even in libraries under a compliance hold - nothing goes into the recycle bin.
Step 4: Remove Empty Folders
Empty folders are a minor storage item on their own, but they add visible clutter, trigger sync client warnings, and slow down admin scripts that iterate library contents. Over years of migration activity and department reorganisations, empty folder trees accumulate quickly and silently.
ShareMaster's Empty Folder Remover finds and deletes empty folders across one or more site collections in a single pass. You get a preview list before anything is removed, so you can exclude folders that are intentionally kept empty as structural placeholders.
Step 5: Clear the Recycle Bin
Items in the SharePoint recycle bin still count against your storage quota. In a large, active tenant the combined recycle bin can hold many gigabytes of data that nobody will ever restore. The bin operates in two stages:
- First-stage (user recycle bin): Visible to users within each site. Items sit here for up to 93 days from the deletion date.
- Second-stage (site collection recycle bin): Items cleared from the first-stage bin move here for the remainder of the 93-day window. Only site collection admins and above can see this stage.
Site collection admins can clear the second-stage bin from the SharePoint admin centre one site at a time. Doing that across hundreds of site collections requires either a PowerShell loop or a tool that targets multiple collections at once.
ShareMaster's Recycle Master lets you search, filter, and bulk-clear the recycle bin across all site collections from a single view. You can filter by deleted date, file type, or deleted-by user before deciding what to clear - reducing the risk of removing something a user still needs.
Putting It All Together
| Step | Typical Storage Impact | Risk | ShareMaster Tool |
|---|---|---|---|
| Trim version history | 30-70% of total storage | Low (check holds first) | Space Master - Version Trimmer |
| Compress images | 5-20% (image-heavy tenants) | Very low (non-destructive) | Space Master - Image Reducer |
| Remove empty folders | Negligible storage, reduces clutter | Very low | Space Master - Empty Folder Remover |
| Clear recycle bin | 5-15% (varies by tenant activity) | Low (review before clearing) | Recycle Master |
| Bulk delete unwanted files | Varies | Medium (irreversible for live files) | Space Master - Bulk Delete |
Frequently Asked Questions
Does clearing the SharePoint recycle bin free storage immediately?
Yes. Once items are permanently deleted from the second-stage recycle bin, the storage they occupied is freed from your tenant quota immediately. There is no delay or background processing step.
How many versions does SharePoint Online keep by default?
By default, SharePoint Online document libraries retain up to 500 major versions per file. With Microsoft 365 Automatic Versioning enabled, minor versions may also accumulate. Each version counts separately against your tenant storage quota. See the SharePoint versioning defaults reference for library-type-specific settings.
Can I reduce SharePoint storage without permanently deleting files?
Image compression is the main non-destructive option. ShareMaster's Image Reducer replaces large image files with smaller compressed versions in place, with no impact on the filename, metadata, or version history. Version trimming does remove old versions, but those are typically safe to delete unless a legal or compliance hold is in place. Check with your compliance team before trimming any library under retention policy.
What is the SharePoint Online tenant storage quota formula?
Your tenant receives 1 TB of base storage plus 10 GB per licensed Microsoft 365 user. A 200-user organisation gets 3 TB total (1 TB + 2 TB) pooled across all site collections. Individual site collections can be capped below the pooled total by a SharePoint admin.
Try ShareMaster free for 14 days