Finding a specific deleted file in a large SharePoint Online recycle bin is harder than most admins expect. These are the three approaches available, compared across the dimensions that matter most in a real recovery scenario.
| Approach | Search by keyword | Filter by date range | Search across site collections | Scripting required | Bulk restore from results |
|---|---|---|---|---|---|
| Native SharePoint browser | Name only | No | No | No | No |
| PnP PowerShell | Yes (Where-Object) | Yes | Yes (loop required) | Yes | Via script |
| ShareMaster Recycle Master | Yes | Yes | No (one site collection) | No | Yes |
How Does SharePoint Recycle Bin Search Work?
The SharePoint Online recycle bin loads deleted items in a paginated list with a search box that matches on item name and nothing else. To locate a deleted file on any other basis, you either scroll and sort the native browser view, filter results using PnP PowerShell queries against the recycle bin API, or use a dedicated tool that loads the bin and filters it locally. Each approach offers a different balance between search depth and the technical knowledge required to use it.
The distinction matters most when you are recovering a specific file from a recycle bin that holds thousands of items, or when you know the date or the person but not the name. What none of the three approaches changes is scope: recycle bins are per site collection, so if you do not know which site held the file, every option means working through the candidate sites one at a time.
Three Ways to Search the SharePoint Recycle Bin
Option 1: The Native SharePoint Recycle Bin Browser
Every SharePoint Online site has a recycle bin accessible from the site settings menu. End users see items they deleted personally. Site owners and members with contribute access see a broader set. Site collection administrators have an additional view - the second-stage (site collection) recycle bin - accessible through Site Settings under Site Collection Administration.
The native browser lets you:
- Sort by Name, Original Location, Deleted By, Deleted Date, or Size
- Select individual or all visible items and restore them
- Navigate between first-stage and second-stage views separately
The native browser does not let you:
- Search on anything other than item name (the box matches names only)
- Filter by a date range (sorting by date is not the same as filtering)
- View items from multiple sites simultaneously (nothing does, the bins are per site collection)
- Select items based on a search result and bulk-restore them
In practice, the native browser works well when the recycle bin contains a few hundred items and you have a rough idea of the filename or deletion date. Once item counts grow into the thousands - common on busy document libraries or collaboration sites - scrolling becomes inefficient. Sorting by Deleted Date helps narrow the window, but you still need to manually identify the correct items.
Option 2: PnP PowerShell
PnP PowerShell's Get-PnPRecycleBinItem cmdlet retrieves recycle bin data directly from the SharePoint Online REST API for the connected site. Unlike the native browser, it returns all items in a single call without pagination. You can then pipe the results through Where-Object to apply any filter your recovery scenario requires.
# Connect to the target site first
Connect-PnPOnline -Url "https://yourtenant.sharepoint.com/sites/SiteName" -Interactive
# Find all deleted items with "budget" in the filename
Get-PnPRecycleBinItem | Where-Object { $_.LeafName -like "*budget*" }
# Find items deleted in the last 30 days
Get-PnPRecycleBinItem | Where-Object { $_.DeletedDate -gt (Get-Date).AddDays(-30) }
# Query the second-stage recycle bin only
Get-PnPRecycleBinItem -ItemState SecondStageDeletedItems
Key properties returned by Get-PnPRecycleBinItem include LeafName (filename), DirName (original folder path), DeletedDate, DeletedByName, Size (in bytes), and ItemState (first or second stage). You can export the full result set to CSV for audit records.
The limitation is scope. Get-PnPRecycleBinItem operates against one site at a time. To cover a whole tenant, you need to loop through site URLs, which means maintaining a site inventory list and scripting the iteration. If 50 sites are involved, that is 50 separate connection and query operations. This is a property of the recycle bin itself rather than of PowerShell, so every option on this page inherits it.
PowerShell is the right tool when you need the flexibility of arbitrary filtering on a known site, when you want to export results for documentation, or when you are comfortable scripting a multi-site loop. It is not suited to environments where the admin carrying out the recovery does not have scripting experience.
Option 3: ShareMaster Recycle Master
Recycle Master provides a desktop UI for searching and restoring items from the SharePoint Online recycle bin without PowerShell. You connect it to a site collection, pick the first or second stage, and it pages the whole bin down to your machine so the filtering happens locally instead of in the browser.
Recycle Master's search and filter capabilities:
- Keyword search against item names, on whichever stage you have selected
- Date-deleted range filter (set a start and end date to narrow results to a specific incident window)
- Deleted-by-user filter, so you can recover everything one departing employee deleted from a site
- Item type filter, plus original location and author
- Bulk-select items from filtered results and restore them in a single operation
The scope is one site collection at a time, the same as the other two options. Recycle Master removes the scripting and the sort-and-scroll, not the need to know roughly where the content lived. Across sites it does two things: it empties the bins on as many sites as you tick in a single operation, and it reports item counts and sizes per site so you can see where the deleted content is sitting.
The practical difference in a support scenario: a ticket arrives saying "I accidentally deleted our entire Q1 folder last Tuesday." In the native browser, the admin navigates to the relevant site, sorts by date, and scrolls to identify the items. In Recycle Master, they set the date filter to last Tuesday, type the folder name, and restore the matched items in one pass. The time difference on a large recycle bin is significant.
Where Recycle Master pulls ahead across a whole tenant is not search but cleanup and visibility: it empties bins on every site you select in one operation, and its recycling bin report gives item counts and sizes per site without a script. For MSPs managing multiple client tenants or administrators responsible for dozens of sites, that is the part which removes real work. Finding a named file in an unknown site collection is still a per-site job.
When a site has tens of thousands of deleted items spread across the first and second stage, scrolling the native SharePoint recycle bin browser to find a specific file is not a realistic recovery strategy. The native list was built for occasional, small-scale recovery - not bulk or keyword-targeted restores at scale.
Side-by-Side Capability Comparison
| Capability | Native Browser | PnP PowerShell | Recycle Master |
|---|---|---|---|
| Search by keyword / filename | Column sort only | Yes (Where-Object filter) | Yes (indexed search) |
| Filter by date deleted | Sort only | Yes | Yes (date range picker) |
| Filter by who deleted | Sort only | Yes | Yes |
| Filter by file type | No | Yes (extension match) | Yes |
| First-stage recycle bin | Yes | Yes | Yes |
| Second-stage recycle bin | Yes (separate nav) | Yes (-ItemState param) | Yes (stage selector) |
| Search across site collections | No | Yes (with loop script) | No (one site collection) |
| Empty bins on many sites in one operation | No | Yes (with loop script) | Yes |
| Bulk restore from filtered results | No | Via scripting | Yes |
| Export results to file | No | Yes (CSV) | No |
| Admin role required | No (own items) | Yes | Yes |
| Scripting knowledge needed | None | Moderate | None |
For organisations that need filtered search and bulk restore on a site without writing a script, Recycle Master is the only option in the table that does both. See more on the advanced recycling bin features it provides, including the multi-site bulk clear. If you are working out which stage holds your item in the first place, how to search the SharePoint recycle bin covers the native route.
See everything Recycle Master includes, including how filtered search, bulk restore and the second-stage view work in a single connected session.
Decision Matrix: Which Tool to Use
| Your situation | Best approach |
|---|---|
| Small recycle bin (under 500 items), single site, you know roughly when the file was deleted | Native SharePoint browser |
| Single site, large recycle bin, comfortable with PowerShell scripting | PnP PowerShell |
| Need to export a full recycle bin inventory to CSV for an audit report | PnP PowerShell |
| Multiple sites, no scripting available, need bins emptied or sized | ShareMaster Recycle Master |
| Recovering all items deleted by a departing employee across all their sites | ShareMaster Recycle Master, if you know which sites to check: it filters on "deleted by" but reads one site collection at a time, so you repeat it per site. PnP PowerShell if you need to sweep every site unattended. |
| Searching the second-stage (site collection) recycle bin across many sites | ShareMaster Recycle Master |
| Bulk restore of hundreds of items from a date-range-filtered result | ShareMaster Recycle Master |
Frequently Asked Questions
How do I search the SharePoint recycle bin by filename?
The native recycle bin has a search box, but it matches on item name only, within one stage of one site collection. To filter on anything else, pipe Get-PnPRecycleBinItem results through Where-Object in PnP PowerShell, or use ShareMaster Recycle Master, which loads the bin for a site collection and filters it locally on name, original location, type, author, deleted-by and a deleted date range.
Can I search the recycle bin for files deleted by a specific user?
Yes. PnP PowerShell lets you filter by the DeletedByName property using Where-Object. ShareMaster Recycle Master has a dedicated Deleted By filter field that works on either stage without scripting. Both run against one site collection at a time. The native browser shows a Deleted By column you can sort, but not filter by a specific value.
How do I access the SharePoint second-stage recycle bin?
Go to Site Settings, then click Site Collection Recycle Bin under Site Collection Administration. This link is only visible to site collection administrators. Alternatively, use Get-PnPRecycleBinItem -ItemState SecondStageDeletedItems in PnP PowerShell, or use Recycle Master, where the stage is a selector on the same screen rather than a separate page to navigate to.
Can I search the SharePoint recycle bin across all sites at once?
No, and no tool does this, ShareMaster included. Recycle bins are scoped per site collection: the native browser is scoped to the current site, PnP PowerShell needs a loop across a list of site URLs, and Recycle Master connects to one site collection at a time. What ShareMaster does do across many sites is empty their bins in one operation and report item counts and sizes per site. See the guide to searching the SharePoint recycle bin for how to work through candidate sites, and the bulk restore guide for large-scale recovery once you have found the items.