SharePoint storage limit exceeded? 6 Proven ways to reclaim space

If when you open the SharePoint admin center, you see the “Your storage is full” message, this is for you.

This guide outlines six proven methods to reclaim 30-70% of SharePoint storage without data loss. These methods have been tested by the SProbot team across various organizational environments and consistently deliver significant storage reduction.

Method 1: Eliminate document version history bloat

Version history represents the largest opportunity for storage optimization in most SharePoint environments. SharePoint Online stores up to 500 major versions of each document by default (this can be set up to 50 000), resulting in substantial storage consumption over time.

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 existing 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.

How-to guidance

• How to trim file versions to increase available SharePoint storage
• How to save SharePoint storage with automated file versioning

Expected results

20-30% storage reduction after working through all sites.

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

Method 2: Identify and remove ROT content

ROT content is Redundant, Outdated, and Trivial files that consume storage without providing business value. This content accumulates through normal business operations but requires systematic identification and removal.

Examples of Redundant content

• Duplicate files across multiple site locations
• Multiple copies of identical presentations
• Same documents uploaded by different users
• Backup copies stored in active locations

Examples of Outdated 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 files and sample documents
• Personal files mistakenly uploaded to team sites
• Screenshot collections and temporary files
• Draft content that was never finalized

Implementation actions

To identify and clean up ROT, you need to first find sites and files which meet the criteria above, then choose to either archive or delete them.

1. ‍Redundant content – At site level, find sites and teams which have the same name but different URLs, evaluate which is the original (or most relevant) by consulting with site owners, then archive or delete unwanted copies. Within a library or site, find files which have the same filename, determine which copies are the authoritative ones, and remove the unwanted duplicates.
2. Obsolete content – At site level, find sites which have been inactive for at least 6 months (or even longer if sensible). At file level, find files which haven’t been updated for at least 1year.

How-to guidance

• Clean up duplicate sites and teams
• Clean up inactive sites
• Clean up test sites and teams
• Find duplicate files using PowerShel

Expected results

10-20% storage reduction plus improved search performance and content discoverability.

Considerations

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

Method 3: Improve large file management

Large files disproportionately impact SharePoint storage while often providing minimal business value relative to their storage consumption. Single video files can consume equivalent space to thousands of business documents.

Common large file types

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
• Database backups and exports
• System documentation with screenshots
• Software installation packages

Implementation actions

Generate reports showing files larger than 50MB (or a threshold you see fit) sorted by last modified, file type, and version size. Focus on files not updated recently as primary optimization candidates.

1. Identify files exceeding 50MB using search, PowerShell, or SProbot.
2. Determine whether these files are business critical.
3. Determine inactive files are still required.
4. Trim versions if relevant.
5. Migrate to alternative storage locations if applicable\

How-to guidance

• Find and clean up large files
• Trim file versions

Expected results

15-30% storage reduction plus improved sync performance for document libraries.

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.

Method 4: Clean up inactive teams and sites

Abandoned SharePoint sites consume storage indefinitely without providing business value. These sites result from completed projects, organizational changes, and employee departures.

Implementation actions

Manual option

Run a report on last activity in descending order, confirm with site owners (if the sites aren’t orphaned) whether their sites are still needed, and then either archive or delete them.

Automated option

Automatically notify site owners when an inactivity threshold is reached by using SProbot’s inactive site cleanup or Site Lifecycle Management in SAM.

Expected results 

10-20% storage reduction plus reduced administrative overhead and improved site discoverability.

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.

Method 5: 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

Expected results

Immediate storage reduction impact following cleanup completion.

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.

Method 6: 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.

How to implement these methods

Phase 1: Quick wins (Week 1-2) 

Begin with version history optimization to achieve immediate, dramatic storage reduction with minimal risk. Configure appropriate version limits and implement cleanup actions with scripts or a tool like SProbot.

Phase 2: ROT content (Week 2-6) 

Focus on ROT content identification starting with unused files over 50MB and sites and files not accessed in 12+ months. These categories provide significant savings with clear business justification.

Phase 3: Lifecycle management (Week 6-12)

Implement abandoned site cleanup processes and establish ongoing governance policies through controlled site/team provisioning to prevent future accumulation of storage waste.

Phase 4: Continuous optimization(Ongoing) 

Establish quarterly reviews with monthly monitoring using SProbot’s Health Check. Build stakeholder engagement throughout the process for long-term success.

FAQs

How quickly will optimization methods show results? Version history cleanup provides immediate results within hours of implementation. ROT content removal requires 2-4 weeks for analysis and approval processes. Abandoned site cleanup typically takes 4-6 weeks depending on the number of sites requiring review.

What safeguards prevent accidental deletion of important content? Implement staged approaches with stakeholder approval processes to minimize accidental deletion risks. SharePoint's recycle bin provides 93-day recovery windows for recently deleted content. Consider archiving high-value content to Microsoft 365 Archive (at+-25% of the cost of SharePoint storage) instead of deleting it.

What ongoing maintenance is required for these optimizations? Establish quarterly comprehensive storage reviews with monthly monitoring of version history and large files. Automated cleanup of inactive sites (and retention policies for some categories of content) can reduce the manual effort involved substantially.

How do archiving and deletion approaches differ? Archiving moves content to cold storage within Microsoft 365 archive, which is inaccessible to end-users but still accessible to SharePoint admins and eDiscovery. Deletion permanently removes content after recycle bin retention periods expire. Selection depends on business value assessment and regulatory requirements.

In conclusion

Storage optimization requires systematic implementation and ongoing governance rather than one-time cleanup activities. The methods outlined here provide immediate storage reclamation while establishing processes that prevent unnecessarily increasing storage use in future.