SharePoint Cleanup: How to Find and Delete Junk Data

Why SharePoint Gets Cluttered

SharePoint environments accumulate junk data faster than most administrators expect. Files get duplicated across sites, documents go untouched for years, team sites outlive the teams that created them, and version history quietly balloons storage consumption. Left unchecked, this clutter drives up storage costs, slows search results, and makes it harder for people to find what they actually need.

The good news: a structured cleanup process can reclaim significant storage and restore order. The challenge is knowing where to look and what to delete safely.

This article provides general guidance for SharePoint cleanup. Specific steps may vary depending on your Microsoft 365 plan, SharePoint version, and organizational policies. Always test cleanup actions in a non-production environment and verify compliance requirements before deleting data.

The Four Types of SharePoint Junk Data

Before starting any cleanup effort, it helps to understand the main categories of waste that build up in SharePoint.

Duplicate Files

Duplicate files are one of the most common storage problems. They appear when users copy documents between sites instead of sharing links, when migration tools import the same content twice, or when teams maintain separate copies of templates and reference materials. Duplicates not only waste storage but also create confusion about which version is the source of truth.

Stale Documents

Stale documents are files that nobody has accessed or modified in a long time. These include abandoned drafts, outdated project deliverables, superseded policies, and old reports that have no ongoing business value. In many environments, stale content accounts for 40 to 60 percent of total storage consumption.

Orphaned Sites

Orphaned sites are team sites, communication sites, or project sites that no longer have active owners or members. They often linger after projects conclude, teams reorganize, or employees leave the organization. These sites consume storage and licensing overhead while serving no purpose.

Old Version History

SharePoint's versioning feature keeps a copy of every saved change to a document. While versioning is valuable for recovery and audit purposes, retaining hundreds of versions for every file adds up quickly. In document-heavy environments, version history alone can consume more storage than the current files themselves.

A Systematic Cleanup Process

Effective cleanup follows four phases: audit, prioritize, clean, and prevent. Skipping straight to deletion without understanding the data usually leads to mistakes or incomplete results.

Phase 1: Audit

Start by gathering data on what exists and how it is being used. The SharePoint admin center provides storage metrics at the site collection level, showing which sites consume the most space. Within individual sites, the Site Usage reports and Storage Metrics page reveal which libraries and files are the largest.

For a more detailed audit, consider these data points:

Storage by site collection — Identify the top 10 to 20 sites by storage consumption. These are the highest-impact targets for cleanup.
Last modified dates — Flag files and sites that have not been modified in 12 months or more.
Version counts — Identify documents with excessive version history, particularly those with more than 50 versions.
Site ownership — Check whether each site has active owners. Sites with no active owners are candidates for orphan review.

Phase 2: Prioritize

Not all junk data carries the same risk or reward. Rank cleanup targets by storage impact and deletion safety:

Low risk, high impact — Old version history, recycle bin contents, and clearly abandoned personal test sites. These are safe to clean up first.
Medium risk, medium impact — Stale documents in project sites that concluded more than a year ago. Notify former team members before deletion.
Higher risk, variable impact — Duplicate files in active libraries and content in sites with unclear ownership. These require more investigation before action.

Phase 3: Clean

With priorities set, work through each category methodically.

Trim version history. Reduce version limits on libraries that retain excessive versions. A reasonable default for most organizations is 50 major versions. Use the Storage Metrics page to identify libraries where version history is the dominant storage consumer, and trim old versions accordingly.

Empty recycle bins. Site recycle bins and the second-stage recycle bin both count against storage quotas. After confirming that no recently deleted items need recovery, clear both stages.

Archive or delete stale content. For documents that have not been accessed in over a year, decide whether to archive them to cheaper storage or delete them outright. If regulatory or compliance requirements apply, archive rather than delete.

Remove orphaned sites. Contact former site owners or their managers before deleting orphaned sites. If no owner can be identified after 30 days of outreach, proceed with archival or deletion per organizational policy.

Deduplicate files. Removing duplicates requires care. Identify the authoritative copy, redirect any links or references to it, and then delete the extras. This is the most labor-intensive cleanup task but yields meaningful storage and clarity improvements.

Phase 4: Prevent

Cleanup without prevention is a recurring chore. Put guardrails in place to slow re-accumulation.

Built-In Tools for SharePoint Cleanup

SharePoint and Microsoft 365 include several tools that support cleanup without requiring third-party software:

SharePoint Admin Center Storage Metrics — Provides a top-level view of storage consumption across all site collections.
Site Collection Storage Metrics — Available within each site under Site Settings, this breaks down storage by library, folder, and file, including version history.
Microsoft 365 Usage Reports — Show activity trends across sites, helping identify inactive sites and users.
Retention Policies (Microsoft Purview) — Automate deletion of content after a defined retention period, ensuring stale data does not accumulate indefinitely.
Site Lifecycle Policies — Prompt site owners to confirm that their sites are still active. Unconfirmed sites can be flagged for review or automatic closure.

For environments with more than a few hundred sites, third-party tools that specialize in SharePoint analytics and cleanup can automate duplicate detection, stale content identification, and bulk version trimming. These tools are especially useful for large-scale or recurring cleanup efforts.

Preventing Re-Accumulation

A cleanup project only stays effective if the underlying habits and policies change. Four strategies help maintain a clean environment over time:

Set version limits proactively. Configure version limits at the library or site template level before content is created. Fifty major versions is a practical default for most document libraries.

Implement retention policies. Use Microsoft Purview retention policies to automatically delete content that exceeds its useful life. Apply different retention periods to different content types based on business and compliance requirements.

Enforce site lifecycle policies. Require site owners to certify their sites periodically. Sites that go uncertified should be flagged for review and eventual decommissioning.

Train users on linking versus copying. Many duplicate files exist because users do not know how to share links instead of copying files between sites. Short training sessions or reference guides on sharing best practices reduce duplication at the source.

Quarterly Cleanup Checklist

Use this checklist every quarter to keep SharePoint storage under control:

[ ] Review the top 20 site collections by storage consumption
[ ] Identify and investigate sites with no active owners
[ ] Trim version history on libraries exceeding storage thresholds
[ ] Empty site recycle bins and second-stage recycle bins
[ ] Run a stale content report for files unmodified in 12+ months
[ ] Check for and resolve duplicate files in high-traffic libraries
[ ] Verify that retention policies are applied and functioning correctly
[ ] Confirm site lifecycle policy attestations are up to date
[ ] Document cleanup actions taken and storage reclaimed
[ ] Update stakeholders on storage trends and upcoming cleanup targets

Consistent quarterly attention prevents small messes from becoming major cleanup projects. The first cycle takes the most effort. After that, each subsequent review gets faster as policies and user habits improve.