To restore deleted SharePoint file content without overwriting newer edits, first preserve any newer copies. Use a single-item restore where possible, rather than rolling back an entire document library and reversing unrelated work.
The recovered file contains the content and retained versions available when it was deleted, not changes subsequently saved elsewhere. Start by separating the missing document from any newer copies before choosing a recovery method.
Key Takeaways
- Preserve newer or unsynchronised copies before restoring a deleted SharePoint file, then compare them with the recovered document and merge any required edits.
- Restore a selected item from the first-stage Recycle Bin where possible. The second-stage Recycle Bin requires site collection administrator access, and both stages share the same 93-day recovery period from the original deletion.
- Use Version history when a file still exists but was overwritten. Reserve Restore this library for wider damage because it can reverse legitimate activity from the previous 30 days.
- For bulk recovery, use PnP PowerShell with a defined scope, recorded item IDs and batches below 5,000 items. Check the inventory and filters before rerunning a command that restores nothing.
- If an item has been permanently removed from the second-stage bin, raise a Microsoft Support request promptly or check whether a separate backup can restore it to an alternate location.
Protect newer edits before starting recovery
Preserve the current working copies
Identify the original SharePoint site, document library, folder and filename. Then establish whether somebody has recreated the document, saved a replacement or continued editing a locally synchronised copy.
Ask affected users to stop editing temporarily. Save newer content separately, using a different filename or recovery folder, before attempting restoration. If a device contains unsynchronised changes, preserve those locally before reconnecting it.
A downloaded copy protects the document’s content, but does not preserve its complete SharePoint version history, permissions or metadata. Record those separately where they matter.
Keep the recovery scope narrow
Recover the deleted item rather than restoring the whole library when only that item is missing. A wider rollback can reverse legitimate changes made after the selected recovery point.
If the original path already contains a same-name file, preserve that newer document before resolving the conflict. Do not delete it simply to make the restore succeed.
After recovery, compare the recovered file with the preserved working copy and merge the required changes. For Word documents, Review > Compare can help identify differences. Record which copy becomes authoritative before colleagues resume editing.
Restore the file from the first-stage Recycle Bin
The SharePoint recycle bin is the normal starting point. Restoring a selected item returns it to its original location, subject to any conflict or error that needs attention.
Follow These Steps:
- Open the SharePoint site containing the deleted document.
- Select Recycle Bin in the left-hand navigation. If it’s absent, open the Settings gear icon, select Site Contents and find Recycle Bin.
- Identify the correct item using its name, original location, deletion date and deleted-by details.
- Select the item, then choose Restore.
- Open the recovered document and review its content and version history before releasing it for normal use.
Navigation labels vary between SharePoint experiences. Microsoft’s SharePoint and Teams recovery instructions describe the supported route.
If the file is absent, ask a site administrator to investigate. An empty personal view doesn’t establish that everybody’s deleted items have disappeared.
Escalate to the second-stage Recycle Bin
The second-stage Recycle Bin, also called the site collection Recycle Bin, holds items removed from the first stage for the remaining recovery period. Restoring items from this stage requires site collection administrator permissions.
Open the site’s Recycle Bin and follow the second-stage Recycle Bin link at the bottom of the page. An authorised administrator can identify the item, select it and choose Restore.
Microsoft’s site collection recovery guidance confirms that restored items return to their original locations.
Moving an item into this stage does not create another recovery window. An item deleted from its original folder 90 days ago normally has only 3 days remaining, even if it entered the second-stage bin today.
If an item is missing from your view, ask the Microsoft 365 administrator to investigate. You may still be able to recover deleted files at this later stage, depending on how much of the original recovery window remains.
Understand the 93-day SharePoint recovery window
These recovery options have different limits.
| Recovery option | Available window | Effect on newer work |
|---|---|---|
| First-stage Recycle Bin | Within the shared 93-day period | Restores selected deleted items |
| Second-stage Recycle Bin | Remainder of the same 93 days | Restores selected items with administrator access |
| Restore this library | Previous 30 days | Reverses library activity after the chosen point |
| Separate backup | Configured backup retention | Depends on restore scope and destination |
The narrowest suitable option normally creates the least disruption.
The clock starts at the original deletion
SharePoint Online normally retains deleted items for 93 days after deletion from their original location. Microsoft’s SharePoint retention documentation confirms that the 93-day retention period spans both Recycle Bin stages.
Do not apply general 14-day or 30-day recycle-bin advice to SharePoint Online. Nor is its standard 93-day period simply an administrator-selectable shorter setting. SharePoint Server has different configuration rules.
Some items disappear before 93 days
An administrator can permanently remove items from the second-stage bin. SharePoint also purges its oldest items if that bin exceeds its allocation.
First-stage storage counts towards the site quota. The second-stage allocation is 200% of the site collection quota, rather than a universal 25GB allowance. Neither bin is independent backup storage.
Distinguish version history from library rollback
Use version history for an existing document
If the file still exists but its contents were overwritten, start with Version history rather than the Recycle Bin. Review the saved versions and identify the required content.
Restoring an older version makes it current; it does not automatically merge that content with newer edits. Preserve the current content first, then compare or combine the versions.
Version history is part of sound SharePoint document management, but its usefulness depends on the versions still being available. It cannot recover an unsaved edit that never reached SharePoint.
Reserve library rollback for widespread damage
A site administrator can use Settings > Restore this library to undo file and folder activity within the previous 30 days. It is useful when deletion, corruption or unwanted changes affect many documents.
Microsoft’s shared-library restoration guidance describes this broader rollback.
The selected point affects legitimate activity too. Preserve subsequent work and review the activity list before proceeding. This feature cannot recover files already purged from the site collection Recycle Bin, or restore an entire deleted library.
Restore deleted SharePoint files in bulk with PnP PowerShell
PnP PowerShell provides administrator commands for inventorying and restoring recycle-bin items. It requires appropriate authentication and permissions, and should be used against a defined recovery scope.
Use This Controlled Sequence:
- Connect to the affected site and inventory the relevant stage using
Get-PnPRecycleBinItem, with-FirstStageor-SecondStage. - Record item IDs, original paths, deletion times and deleting users. Filter candidates using
DeletedDateandDeletedByEmail, with an explicit time range. - Preserve replacement files, then restore a small approved group of recorded candidates with
Restore-PnPRecycleBinItem -Force. Keep the batch size below 5,000 items. - Log each outcome and compare successful restores with the approved IDs before continuing in batches below 5,000 items.
The documented Get-PnPRecycleBinItem parameters include -RowLimit. This limits returned items; it is not a pagination mechanism or a guarantee against threshold errors.
Filtering after retrieving only the first 4,000 entries can miss older matches. Repeating that query may retrieve the same unrelated items rather than advance through the bin.
The error “operation prohibited because it exceeds the list view threshold” needs more than a smaller restore batch. Separate inventory retrieval from restoration and use recorded IDs where possible.
If a command completes but restores nothing, inspect the candidate count, site connection, selected stage and filters before rerunning it. -Force suppresses confirmation; it doesn’t correct selection errors.
Escalate beyond the recycle bins without overwriting good data
Raise a Microsoft Support request promptly
A site collection administrator cannot restore an item permanently deleted from the second-stage bin. That closes the recycle-bin route, but doesn’t establish that every recovery route is unavailable.
Microsoft’s SharePoint data-deletion guidance describes a separate service-backup window of 14 days. Raise a support request promptly with the site URL, affected paths and deletion timeline.
Support recovery can involve a site collection rather than an individual document. It isn’t a guaranteed additional 14 days of self-service file recovery. Preserve current content and establish the proposed restore scope before authorising a wider recovery.
Recover backup content separately where possible
Backup software may restore the required file to an alternate location, where supported, so you can compare it with the live document before replacing anything.
A backup restores captured content, not edits made after its recovery point. Review its coverage of file versions, permissions and metadata alongside the actual document.
Our guidance on Microsoft 365 backup protection explains why native recovery windows and separate backup serve different purposes. A backup job marked successful still needs restore testing.
Frequently asked questions
How do you access the Recycle Bin from Microsoft Teams?
For channel files, open the channel’s Files or Shared tab and select Open in SharePoint, sometimes under More. Open that site’s Recycle Bin.
Private and shared channels use separate SharePoint sites, so start from the affected channel. Files shared in a Teams chat usually reside in the sender’s OneDrive and require that recovery route instead.
Does restoring a deleted file recover every edit?
No. It recovers the deleted item and its retained history, not newer content saved in a replacement file, another location or an unsynchronised device.
After restoring, compare the recovered document with those separate copies. Restoring the original does not combine them automatically.
Keep the recovery narrower than the damage
A targeted restore protects unrelated work, but newer replacement files still need separate preservation and comparison. Treat a whole-library or site rollback as a wider change requiring its own recovery plan.
Speak to our team about Microsoft 365 support and recovery planning. We can help review recovery procedures and cloud backup recovery weaknesses before a deletion becomes a wider business interruption.
