Does the SharePoint Recycle Bin Take Up Storage Space?

The short answer is yes. Items in the SharePoint recycle bin count against the tenant storage quota for as long as they remain there. Deleting a file from a document library does not free up storage immediately -- it simply moves the file to a holding area where it continues consuming space. This catches many administrators off guard, especially after large cleanup efforts that appear to have no effect on the storage report. Understanding how the recycle bin works and when items actually stop counting against the quota is essential for managing SharePoint storage effectively.

How the Two-Stage Recycle Bin Works

SharePoint uses a two-stage recycle bin system. Each stage has its own retention window, and items count against the storage quota in both stages.

First-Stage Recycle Bin

When a user deletes a file, list item, or folder from a SharePoint site, it moves to the first-stage recycle bin (also called the end-user recycle bin). The item stays there for 93 days from the date of deletion. During this window, the user who deleted the item -- or a site collection administrator -- can restore it to its original location.

Items in the first-stage recycle bin are visible to the user who deleted them. Site owners and members can access the recycle bin from the site contents page. The 93-day clock starts the moment the item is deleted from the library, not from any other event.

Second-Stage Recycle Bin

When an item is manually deleted from the first-stage recycle bin, or when the 93-day first-stage retention expires, the item moves to the second-stage recycle bin (also called the site collection recycle bin). Only site collection administrators can access this stage.

Items in the second-stage recycle bin are retained for 93 days from the date they entered the second stage. After that, the item is permanently deleted and the storage is finally released. This means a deleted file could theoretically occupy storage for up to 186 days -- 93 days in each stage -- before the space is reclaimed.

The second-stage recycle bin has a size limit of 25 percent of the site collection storage quota. If this limit is reached, the oldest items are permanently deleted to make room for newer ones.

How OneDrive Handles the Recycle Bin Differently

OneDrive for Business uses the same two-stage recycle bin mechanism, but with one important distinction: OneDrive storage is allocated per user, not from the shared tenant pool. Each user typically receives 1 TB of OneDrive storage. Deleted items in a personal OneDrive recycle bin count against that individual user's 1 TB allocation, not the SharePoint tenant pool.

The retention timelines are identical -- 93 days in each stage. However, because OneDrive storage is separate, a bloated OneDrive recycle bin does not affect the SharePoint storage report. Administrators monitoring SharePoint storage sometimes overlook OneDrive entirely, which can be a problem when former employees' OneDrive accounts are retained and their recycle bins are full of deleted content.

When an employee leaves and their Microsoft 365 license is removed, their OneDrive enters a 30-day deletion window (extendable to a maximum of 3,650 days via the OneDrive admin center). During this window, the recycle bin contents still count toward tenant storage. Cleaning up departing users' OneDrive recycle bins before account deletion avoids carrying that dead weight.

The Real Storage Impact

The recycle bin's storage impact is larger than most administrators assume. Consider a common scenario: a team decides to reorganize a document library and deletes 50 GB of outdated files. The storage report shows no change. The administrator checks again a week later -- still no change. The files are sitting in the first-stage recycle bin, consuming the same 50 GB they always did.

In many environments, recycle bin contents account for 5 to 15 percent of total SharePoint storage consumption. For a tenant using 800 GB of its 1 TB pool, that could mean 40 to 120 GB locked up in recycle bins across various site collections. That is a meaningful amount of space, especially when the alternative is paying Microsoft $0.20 per GB per month for overage storage.

Version history compounds the problem. If a file had 30 saved versions before deletion, all 30 versions move to the recycle bin along with the current version. A 10 MB document with 30 versions is actually consuming over 300 MB in the recycle bin -- and the user who deleted it likely has no idea.

Reclaiming Storage: User Steps

Individual users can empty their own recycle bin items to push them to the second stage, or administrators can permanently remove items. Here is how both sides can take action.

For end users who want to clean up after themselves:

1. Navigate to the SharePoint site where files were deleted
2. Click Recycle bin in the left navigation panel (or access it from site contents)
3. Select the items to permanently delete, or click Empty recycle bin to remove everything
4. Confirm the deletion when prompted

This moves the selected items to the second-stage recycle bin. The storage is not freed immediately, but it starts the second-stage retention clock.

Reclaiming Storage: Administrator Steps

Site collection administrators and SharePoint administrators have more control over recycle bin management.

To empty the second-stage recycle bin for a specific site:

1. Navigate to the site collection
2. Go to Site Settings and select Site collection recycle bin under Site Collection Administration
3. Switch to the Second-stage recycle bin view
4. Select items and click Delete to permanently remove them, or use Delete All to clear the entire second-stage bin

For tenant-wide cleanup, administrators can use SharePoint Online Management Shell with PowerShell. The Clear-SPOSiteRecycleBin cmdlet removes all items from both stages of a site's recycle bin in a single operation. Running this across multiple sites can be scripted to reclaim storage in bulk.

The PowerShell approach is more efficient for organizations with many site collections:

1. Connect to SharePoint Online using Connect-SPOService
2. Use Get-SPOSite to list all sites and their storage usage
3. Run Clear-SPOSiteRecycleBin -Identity <SiteURL> -Confirm:$false for each site that needs cleanup

After emptying recycle bins, allow 24 to 48 hours for the storage report in the SharePoint admin center to reflect the freed space. The report is not updated in real time.

Preventing Recycle Bin Bloat

Rather than periodically clearing recycle bins as a reactive measure, a few practices help keep recycle bin storage under control:

• Empty recycle bins after major cleanups. Whenever a large batch of files is deleted as part of a reorganization or archival effort, follow up by emptying the affected site's recycle bin.
• Include recycle bins in storage audits. When reviewing tenant storage usage, check recycle bin sizes alongside active content. The SharePoint admin center storage report includes recycle bin data if examined at the site level.
• Educate users about the distinction between deleting and permanently removing. Most users assume that deleting a file frees up space. A brief explanation during onboarding or in internal documentation prevents confusion later.
• Monitor departing employees' OneDrive accounts. Before removing a license, check whether the user's OneDrive and its recycle bin contain large amounts of data that will linger in the tenant.

The recycle bin exists for a good reason -- accidental deletions happen, and the ability to restore files within 93 days has saved countless hours of lost work. The goal is not to disable or circumvent it, but to factor its storage cost into planning and clean it up intentionally rather than letting it accumulate unnoticed.