Version history alone can account for more than half the storage consumption in an active SharePoint Online site collection, yet most admins focus only on the files they can see in document libraries. The recycle bin, old document versions, and Preservation Hold Library contents all count toward the same quota as your live content. This reference lists every source that contributes to a site collection's storage figure and ranks each by typical impact.
All Storage Sources That Count Toward SharePoint Quota
| Storage Source | Counts toward quota? | Typical impact | How to reduce |
|---|---|---|---|
| Current file versions (live binaries in document libraries) | Yes | Medium | Delete files no longer needed; use bulk delete for entire folder trees |
| Version history (previous versions of files) | Yes | High (often the largest source) | Trim version history; reduce the major/minor version limits on document libraries |
| First-stage recycle bin contents | Yes | Medium | Empty the site recycle bin; expires automatically after 93 days |
| Second-stage recycle bin contents | Yes | Medium (same items, different stage) | Empty the site collection recycle bin as a SharePoint admin; expires automatically |
| Preservation Hold Library (Purview retention holds) | Yes | High (on sites under long-duration policies) | Cannot be manually emptied while hold is active; reduce hold scope if possible |
| Page library content (Site Pages web part content) | Yes | Low to Medium (depends on embedded images) | Remove unused pages; manage image sizes embedded in page content |
| Embedded images in SharePoint pages (stored in Site Assets) | Yes | Medium (on content-heavy intranet sites) | Compress or resize images before upload; remove unused images from Site Assets |
| List attachments | Yes | Low (rarely a significant source) | Remove attachments from list items; move large attachments to document libraries |
| Microsoft Teams channel files (stored in SharePoint document libraries) | Yes | Medium to High (active Teams channels) | Remove old files from Teams channel tabs; version trimming applies to Teams-backed libraries |
| List item metadata and column values | Yes (negligible) | Negligible | Not worth optimising for storage purposes |
What Does Not Count Toward SharePoint Site Collection Storage
Not every piece of data associated with SharePoint Online draws from the site collection quota. These sources are billed differently or have no storage cost to the site:
| Item | Why it does not count |
|---|---|
| Microsoft 365 audit log data | Stored and managed by Microsoft at the tenant level; not part of SharePoint site storage |
| Search index and crawl data | Maintained by Microsoft as part of the SharePoint Online service; zero cost to tenant quota |
| Entra ID user profiles and social data | Stored in user profile service storage allocated separately from site collections |
| Microsoft Forms responses | Stored in Microsoft Forms service storage, not in a SharePoint site collection |
| Microsoft 365 Groups mailbox content | Stored in Exchange Online; does not consume SharePoint quota even for Teams-connected groups |
| OneDrive for Business (personal sites) | Each user's OneDrive draws from that user's individual OneDrive quota, not the SharePoint site collection pool |
Admin Actions and Whether They Reclaim Storage
| Action taken by admin | Reclaims storage? | Notes |
|---|---|---|
| Delete a file from a document library | No (moves to recycle bin) | File moves to first-stage recycle bin; quota is unchanged until the bin is emptied or expires |
| Empty the first-stage recycle bin (site level) | Partially (moves items to second stage) | Items move from first to second stage; still consuming quota |
| Empty the second-stage recycle bin (site collection admin) | Yes | Items are permanently deleted; quota is immediately reclaimed |
| Trim version history (delete old versions) | Yes (immediately) | Each deleted version's binary is removed from storage; quota is reclaimed per version removed |
| Reduce document library version limit (e.g., from 500 to 10) | Partial / delayed | Prevents new version accumulation; does not retroactively delete existing versions already stored above the new limit |
| Delete a site collection | Yes (after recycle bin expiry) | Site moves to the site collection recycle bin; full quota is reclaimed after 93 days or manual permanent deletion |
| Enable Microsoft Intelligent Versioning (automatic version cleanup) | Yes (gradually) | Microsoft automatically thins old versions over time based on age; storage reduction is gradual, not immediate |
Version trimming combined with recycle bin cleanup is the fastest path to meaningful storage reduction on active SharePoint sites. ShareMaster's Space Master includes a Version Trimmer and tools to clear the recycle bin across site collections in a single session, and shows you a storage breakdown by source before any action is taken. For a step-by-step walkthrough, see the guide to reducing SharePoint storage fast.
Frequently Asked Questions
Does the SharePoint recycle bin count toward storage quota?
Yes. Items in both the first-stage and second-stage recycle bin count toward the site collection's storage quota until they are permanently deleted. Deleting files from a library without then emptying the recycle bin reclaims no usable storage. The 93-day retention window represents a maximum; an admin can empty the bin at any time to immediately recover that quota.
Does SharePoint version history count toward storage?
Yes. Each stored version of a file consumes storage equal to the size of that version's binary. A 10 MB document with 50 stored versions can consume up to 500 MB of site collection quota for that single file. Version history is consistently the largest unexpected storage drain in document libraries with frequent editing activity.
What is the fastest way to reclaim SharePoint storage?
Two actions produce the fastest results: empty the site collection recycle bin (immediately frees all recycle bin storage), and trim version history on libraries with large files and high version counts (permanently removes old version binaries). On most active SharePoint sites, version trimming returns significantly more storage than recycle bin cleanup. Both operations are available in ShareMaster Space Master with a site-by-site storage breakdown to prioritise where to act first.
Does SharePoint list item metadata count toward storage quota?
Metadata column values consume a negligible amount of storage and are not a meaningful contributor to quota in practice. The dominant sources are file binaries (current and versioned), recycle bin contents, and Preservation Hold Library contents on retained sites. Optimising metadata fields for storage purposes is not worth the effort.
Try ShareMaster free for 14 days