SharePoint storage limit exceeded? 6 Proven ways to reclaim space

Answer in brief

When your SharePoint storage limit is exceeded, begin by identifying where the largest recoverable storage opportunities are before deleting anything or buying extra capacity. Review inactive sites first, then large files, version-heavy files, inactive files and unnecessary ROT content. Confirm ownership, retention requirements and business value before archiving, trimming or deleting content.

Use this cleanup order:

1. Review inactive sites
2. Find large files
3. Investigate version-heavy files.
4. Review inactive files.
5. Remove unnecessary redundant, obsolete and trivial content.

This sequence helps you start with broader, high-impact opportunities and progressively narrow the review. For the complete planning process, use the SharePoint cleanup checklist for IT admins. If you still have a genuine capacity shortfall after cleanup, use SharePoint storage calculator to assess the remaining requirement.

Six ways to reclaim SharePoint storage

The workflow above determines what you should investigate first. The six methods below explain the individual recovery options in more detail, including version trimming, ROT cleanup, large-file review, inactive-site cleanup, recycle-bin clearing and retention-based disposal. Not every method will apply equally, so use your reports and approval process to prioritise the safest opportunities.

1. Clean up inactive teams and sites 💤

Inactive sites are the first review step because a single site-level decision may address an entire inactive workspace without requiring file-by-file investigation. Check site activity, storage use, ownership and business purpose together. Archive content that still has a legitimate retention or reference need, and delete only after the appropriate review and approval.

For a detailed site-level decision process, see Archive vs Delete: How to Clean Up Inactive SharePoint Sites (and Save Storage Fast).

Implementation actions

Manual option

Find sites which have been inactive for at least 1 year (or longer if sensible). After confirming ownership, business value and retention requirements, decide whether the site should remain active, be archived or be approved for deletion. Archiving may provide a safer route when future access could still be required.

Storage costs for archived content are 75% lower than that of live SharePoint content.

Automated option

Automatically notify site owners when an inactivity threshold is reached by using Site Lifecycle Management in SAM.

Considerations

• Analysis: Generate comprehensive site usage reports including last login dates, file access patterns, and owner status. Analyse storage consumption relative to content value.
• Verification: Contact site owners to confirm abandonment status before taking action.
• Documentation: Record cleanup decisions for future reference.
• Caution: As a rule, archive rather than delete unless there is absolute certainty that the site does not contain any important content. Also, verify compliance requirements.
• Prevention: Implement lifecycle management policies for future site monitoring.

2. Improve large file management 🐘

Large files are the second cleanup step because they can expose concentrated storage use quickly and may also carry substantial version history. Size alone does not make a file unnecessary. Review its owner, purpose, activity, latest-version size and total-version footprint before deciding whether to retain, relocate, archive or delete it.

Start with Find and clean up large files to increase SharePoint storage, then use the report to distinguish large current files from large files whose historical versions create the greater storage opportunity.

Large files in SharePoint often take the form of media and technical files.

Media files

• Uncompressed video content
• High-resolution images and graphics
• Audio recordings and presentations
• Marketing materials with embedded media, like PowerPoint decks

Technical files

• CAD drawings and engineering files
• ISO images
• Database backups and exports
• System documentation with screenshots
• Software installation packages

Implementation actions

Use reporting on files larger than 50MB to review results to determine whether to keep them in SharePoint, or move them to a simpler, more cost-effective storage location.

Considerations

Storing or moving files classified as personal to OneDrive needs to be approached with caution to prevent business-relevant files from ending up in a location where they are not correctly permissioned and retained if a user leaves the organization.

3. Investigate version-heavy files📜

Version history is the third review step, after you have identified inactive sites and large files. The best candidates are not simply files with many versions. Prioritise files where historical versions consume substantially more storage than the current file, then confirm recovery, retention and owner requirements before permanently trimming anything.

Use SharePoint version history cleanup: what to remove, what to keep to decide which versions still provide recovery or business value. When the scope has been approved, follow How to trim versions to increase available SharePoint storage for the implementation options.

Storage impact examples

• On an average 10TB tenant, there are more than 2 million documents.
• In highly collaborative organizations where users constantly edit documents, version history typically accounts for 40-60% of total storage consumption for active files. In many instances, this can easily add up to 30% of the total storage on the tenant.
• The most storage is usually consumed by outlier documents with media embedded in them. A PowerPoint file with two 800MB high-resolution videos embedded in it has a single-version size of 1.6GB, but after being edited over a period of 2 years with small changes to text, it can grow to more than 500GB.

Implementation actions

Eliminating version bloat requires a three-step approach:

1. Trim unnecessary older versions.
2. Set future version limits to either a capped manual number, or automatic limits.
3. Monitor growth and usage and adjust your approach accordingly.

Considerations

• Version limits must align with regulatory retention requirements. Collaborate with legal and compliance teams to determine appropriate version counts for different content types.
• Version trimming in SProbot frees up storage immediately by permanently deleting trimmed versions instead of sending them to the recycle bin

4. Review inactive files 💤

Inactive files are the fourth cleanup step. A file that has not changed recently may still be operationally important, subject to retention or useful as a historical reference, so inactivity should be treated as a review signal rather than an automatic deletion rule. Prioritise inactive files that also consume meaningful storage.

Review each candidate against:

• Its owner and current business purpose.
• Its most recent meaningful activity.
• Its current and total version size.
• Applicable retention, hold or disposal requirements.
• Whether it should remain active, be archived or be deleted.
• Whether the responsible owner has approved the action.

Use Free up SharePoint storage by finding and removing inactive files to generate and review the candidate set. Before deleting stale content, use When to delete SharePoint files instead of archiving them to confirm whether deletion, archiving or keeping the file active is the safer decision.

5. Identify and remove ROT content 📼

Redundant, obsolete and trivial content is the fifth cleanup step because it requires judgement about whether material still has business value. Confirm the authoritative copy, owner, retention position and approved disposal route before removing anything. Where value remains but active access is unnecessary, archiving may be safer than deletion.

• Redundant content includes unnecessary copies where another verified authoritative version exists.
• Obsolete content includes superseded material that no longer supports an active business process.
• Trivial content includes test, temporary or non-business files that have been confirmed as unnecessary.

For uncertain cases, use When to delete SharePoint files instead of archiving them. If content must be retained but does not need to remain active, review How to archive SharePoint sites with Microsoft 365 Archive: Setup, Steps, Costs & Gotchas.

Examples of Redundant content

• Multiple copies of identical presentations
• The same documents uploaded by different users
• Backup copies stored in active locations

Examples of Obsolete content

• Completed project documentation with no archival value
• Marketing materials for discontinued products
• Meeting recordings older than retention requirements
• Superseded policy documents and procedures

Examples of Trivial content

• Test sites like "Joe Sandbox 2024"
• Personal files mistakenly uploaded to team sites
• Screenshot collections and temporary files
• Draft content that was never finalized

Considerations

Searching for duplicate files across an entire tenant requires extensive resources and may not be practical in many cases.

6. Supporting recovery and prevention mechanisms

Recycle bin and second-stage cleanup 🗑️

SharePoint's two-stage recycle bin retains deleted content for extended periods, continuing to consume storage space against site quotas even when users have deleted unwanted content. This creates temporary hidden storage burden that administrators often overlook.

Recycle bin system overview

First-stage recycle bin

• Visible to site users after content deletion
• Retains content for 93 days by default
• Continues consuming storage against site quotas
• Accessible by site owners through site settings interface

Second-stage recycle bin

• Accessible only to site collection administrators
• Retains content if it is deleted from the first-stage bin
• Requires administrative access for cleanup

Implementation actions

Unfortunately clearing of recycle bins is not possible through the SharePoint admin center, so you need to do this via the site UI or PowerShell.

1 - Cautious option: Empty only the second-stage recycle bin to ensure that you’re not deleting content which users might still want to restore.

# Connect to the site
Connect-PnPOnline -Url "https://yourtenant.sharepoint.com/sites/yoursite" -Interactive
# Clear only second-stage recycle bin
Clear-PnPRecycleBinItem -SecondStage -Force

2 - Aggressive option: Empty both first and second-stage recycle bins.

# Connect to the site
Connect-PnPOnline -Url "https://yourtenant.sharepoint.com/sites/yoursite" -Interactive
# Clear all items from both recycle bins
Clear-PnPRecycleBinItem -All -Force

Considerations

This method only accelerates the storage gain process, if you don’t delete items this way, they will automatically free up space after their bin retention period ends anyway.

Implement disposal via retention policy ♻️

Retention policies are a powerful way to prevent storage from being indefinitely consumed, and because they are automated, reduce administrative overhead.

Due to how they are generally configured with a broad scope affecting large swathes of sites and can be complex to understand, they can potentially result in unwanted removals if care is not taken. For this reason, retention policies are best used for long-term disposal (measured in years rather than months) rather than short-term content cleanup.

Background: Learn about retention for SharePoint and OneDrive

Implementation actions

It is recommended that you review  Microsoft’s guidance around retention and disposal or consult with a Purview specialist before implementation labels and policies, but the broad steps for implementation are typically:

1. Business policy definition: In purely business terms, define retention schedules based on how long different departments are required by regulatory bodies to keep content. In some cases, this might be driven by practical rather than regulatory considerations.
2. Technical planning: Map out the various labels and policies to be created to retain and dispose of content both at site and individual file level. Use Microsoft’s retention Flowchart to check your logic.
3. Testing: Thorough testing with shortened periods and clearly defined scenarios is necessary to understand the impact of various labels and policies on each other and the end-results. Do not underestimate the possibility for misunderstanding and conflicting rules to affect the outcomes you might expect to be obvious (see the flowchart above).
4. User awareness: Conduct training and set up easy-to-understand guidance material which makes all users aware of the policy applicable to their area of the business.
5. Deployment: More so than many other systems and processes, only deploy once you are 100% satisfied that everyone understands the outcomes

Considerations

It is important to understand that retention policies by their very nature (and name, of course!) are designed to retain first and then dispose. This means that implementation might in some instances result in more storage consumption because content is retained, rather than being easily disposed of by users who aren’t aware of the policies.

Conclusion

When SharePoint storage is full, the safest response is not indiscriminate deletion. Review inactive sites first, then large files, version-heavy files, inactive files and unnecessary ROT content. This order helps you focus on significant opportunities while keeping ownership, retention, recovery and business value central to each decision.

The SharePoint cleanup checklist for IT admins provides the broader governance process, while the linked version, inactive-file and archive guides support each specialist decision. After completing the cleanup review, validate the capacity recovered and use the [internal link to: SharePoint storage calculator: Estimate your tenant's needs] before deciding whether additional storage is still necessary.

FAQs

What should I clean up first when SharePoint storage is full?

Start with inactive sites, then review large files, version-heavy files, inactive files and unnecessary ROT content. This order moves from broad site-level opportunities to more detailed file-level decisions. Confirm ownership, retention and business value before deleting or trimming anything.

Should I delete large SharePoint files to free space?

Not automatically. File size is a prioritisation signal, not proof that the file is unnecessary. Review the file’s purpose, owner, activity, version history and retention requirements before deciding whether it should stay in SharePoint, be archived or be deleted.

Does changing SharePoint version limits remove existing versions?

Changing a limit may help control future growth, but accumulated versions may still require a separate reporting and trimming process. Review the existing version footprint and confirm recovery and retention requirements before permanently removing historical versions.

Is an inactive SharePoint file safe to delete?

No. Inactivity alone does not establish that a file has no value. An inactive file may still support legal, operational, historical or reference requirements. Confirm ownership, retention and business value, then decide whether to keep, archive or delete it.

Is clearing the recycle bin a long-term storage strategy?

No. Clearing approved deleted content may accelerate the release of storage, but it does not address the causes of ongoing growth. A sustainable process also reviews inactive sites, large files, version history, inactive files and ROT content.

Should I buy more SharePoint storage before cleaning up?

First establish whether your current storage contains meaningful reclaimable capacity. If cleanup would not provide enough space, or if most content remains necessary and active, use a storage calculator to estimate the genuine additional requirement.