A user deletes a file. Someone empties the bin. The ticket arrives: "Can we get that back?" Whether the answer is yes depends on exactly which stage was emptied, how long ago the deletion happened, and what backup infrastructure was in place. This page maps every realistic recovery path so you know where to look first.
What "emptied" actually means in SharePoint
SharePoint uses two recycle bin stages per site collection. Emptying the bin is not the same thing depending on who does it.
User empties the first-stage bin
When a site member or owner clicks "Empty recycle bin" from their bin view, SharePoint moves those items to the second-stage bin - it does not permanently delete them. The items are still recoverable by a site collection administrator. This is the most common scenario behind "the bin is empty but can we still get the file?"
Admin empties the second-stage bin
When a site collection administrator explicitly empties the second-stage bin (or the entire bin from the admin interface), items are permanently removed from SharePoint's active storage. This is a destructive operation. The only remaining recovery options at this point are external: Microsoft 365 Backup, a third-party backup solution, or a downloaded copy of the file.
The 93-day expiry
SharePoint automatically purges items from the recycle bin 93 days after the original deletion date. Both stages share this single clock. An item deleted on day 1 and moved to the second stage on day 80 expires on day 93, not day 13 from the stage transfer. Once the 93-day window closes, native recovery is not possible regardless of whether anyone manually emptied anything.
Recovery options side by side
| Recovery path | Works after user emptied first-stage? | Works after admin emptied second-stage? | Works after 93-day expiry? | Admin permission required |
|---|---|---|---|---|
| SharePoint second-stage recycle bin | Yes | No | No | Site collection admin |
| Recycle Master (ShareMaster) | Yes - indexed search across all sites | No | No | Site collection admin or Global admin |
| SharePoint version history | No (item must still exist as a file) | No | No | Contributor or above |
| Microsoft 365 Backup | Yes (if Backup covers the site) | Yes (if Backup covers the site) | Yes (within configured retention) | Global admin or Backup admin |
| Third-party backup solution | Yes (if solution covered the file) | Yes (if solution covered the file) | Yes (within solution's retention) | Varies by solution |
| Microsoft Support request | Rarely possible; not guaranteed | Rarely possible; not guaranteed | Not available after expiry | Global admin to raise ticket |
| Downloaded / emailed copy | Possible if someone has a local copy | Possible if someone has a local copy | Possible if someone has a local copy | None |
Step 1: check the second-stage bin before anything else
Before concluding that a file is gone, verify the second-stage bin. Most "emptied bin" recovery tickets are solved here because users can only empty the first-stage bin - they cannot reach the second stage themselves.
To access the second-stage bin, navigate directly to https://yourtenant.sharepoint.com/sites/your-site/_layouts/15/AdminRecycleBin.aspx using a site collection administrator account. The full steps and permission requirements are covered in the SharePoint second-stage recycle bin access guide.
If the tenant has many sites and you need to search across all of them simultaneously, Recycle Master indexes every site collection's bin and lets you filter by filename, deleted-by user, date range, and file type across the whole tenant from a single view. This is significantly faster than checking each site's admin bin page manually when you do not know which site collection the file belonged to.
When the second-stage bin is also empty
If an administrator has already cleared the second-stage bin, or if 93 days have elapsed since deletion, SharePoint has no native copy. At this point the question shifts entirely to your external protection layer.
Microsoft 365 Backup
Microsoft 365 Backup (a paid add-on) takes snapshot copies of SharePoint sites and stores them separately from the tenant's active storage. If it was enabled and configured to cover the affected site, an admin can initiate a site-level restore from the Microsoft 365 admin centre. The restore rolls the entire site to a snapshot state, overwriting any changes made since. It is not a file-level restore.
This makes Microsoft 365 Backup useful for large-scale recovery events but awkward for recovering a single document without disturbing everything else on the site.
Third-party backup solutions
Purpose-built Microsoft 365 backup tools typically offer more granular recovery than Microsoft 365 Backup - item-level restore, library-level restore, and the ability to recover to a different location rather than overwriting the live site. If your organisation uses one of these solutions, the recovery path depends on its retention configuration and whether the affected site was included in the backup scope.
Downloaded or emailed copies
In many organisations, the fastest recovery path is a copy on someone's local machine: a downloaded version, a file attached to an email, a Teams message with the document. Ask the requester before committing to a complex restore operation.
"Before opening a backup restore ticket, always ask whether anyone downloaded the file or received it as an email attachment. A five-second check can save an hour of admin work."
Decision matrix: where to start
| Your situation | Start here |
|---|---|
| User says "I emptied my bin" - deletion within 93 days | Check the second-stage admin bin at /_layouts/15/AdminRecycleBin.aspx |
| Cannot find the file across multiple sites | Use Recycle Master to search all site bins by filename or date range |
| Admin cleared the second-stage bin, deletion within 93 days | Microsoft 365 Backup (if subscribed) or third-party backup |
| Deletion was more than 93 days ago | Microsoft 365 Backup or third-party backup only; ask about local copies |
| No backup solution in place, bin expired | Ask the requester for a local or email copy; consider a Microsoft support ticket as a long shot |
| Hundreds of files deleted by a user or script within 93 days | Recycle Master bulk restore filtered by deleted-by and date range |
Frequently Asked Questions
Can I recover a SharePoint file after the recycle bin has been emptied?
It depends on which stage was emptied. If a user emptied the first-stage bin, items move to the second-stage bin where a site collection administrator can still recover them within the 93-day window. If the second-stage bin was also cleared by an administrator, or the 93-day window has passed, recovery requires Microsoft 365 Backup, a third-party backup solution, or a locally saved copy.
How long do files stay in the SharePoint second-stage recycle bin?
The second stage does not add extra time. SharePoint measures 93 days from the original deletion date, so an item moved to the second stage partway through that window expires at day 93, not 93 days from when it was moved.
Who can access the SharePoint second-stage recycle bin?
Only site collection administrators can see and restore items from the second-stage bin. Regular site members and owners cannot access it. SharePoint administrators and Global administrators automatically hold site collection admin rights and can reach any site's second-stage bin.