SharePoint Preservation Hold Library: Why Storage Stays High After Deletion
| What you find | What it means | Safe next step |
|---|---|---|
| Large live-file version histories | Library versions may be consuming storage | Review retention, report versions, and evaluate a trim job |
| Large Preservation Hold Library | Content is being preserved for compliance | Ask compliance owners to identify applicable policies and holds |
| Storage unchanged after deletion | Preserved copies or recycle bins may remain | Compare Storage Metrics and retention status before repeating deletion |
| No clear policy owner | You cannot yet authorize disposal | Establish ownership and document requirements before changes |
If a site's document library shrank but its storage did not, don't immediately run a bigger deletion job. The missing space may belong to preserved content rather than visible files. Microsoft's retention documentation for SharePoint and OneDrive (Microsoft Learn: retention for SharePoint and OneDrive) explains when content is copied into the Preservation Hold Library and why manually editing, moving, or deleting those copies is unsupported.
What is the Preservation Hold Library?
It is a hidden system location SharePoint creates when it needs to preserve content. Retention policies, retention labels, and eDiscovery holds are related compliance mechanisms, but they are not interchangeable. The applicable setting and the document's record status affect what happens when someone edits or deletes it. Ask the compliance owner which mechanism applies instead of treating every retained file as having one identical deletion rule.
A user may be allowed to delete the working copy of a document while a retained copy remains. Some record settings prevent deletion instead. Neither behavior means retention has failed. It means ordinary library actions do not decide when the organization's compliance copy can be disposed of.
Why lowering version limits may not release space
Version limits control ordinary document version histories; they do not cancel a retention requirement. Microsoft explains that versions of retained documents can be preserved together in a single file in the Preservation Hold Library. Do not count visible versions and assume their removal will free the same amount of storage. Separate your live-file version report from preserved-content storage.
Changing a policy for future versions is also not the same as queuing a trim job for existing versions. Read the version-trimming guide and Microsoft's trimming workflow before any approved cleanup. Trim jobs permanently delete eligible versions, bypassing the normal recycle bin; run the available report and what-if analysis first.
A safe investigation workflow
- Record the affected site URL, current storage, and the dates of recent deletions or policy changes. Inspect site Storage Metrics with an authorized administrator to distinguish live libraries, versions, and preserved content.
- Ask a compliance administrator to inspect retention policy scope, item retention labels, record settings, and eDiscovery cases that include the site. A site owner's view alone is not a complete inventory of holds.
- Record the policy or case owner, the business obligation, and the next review date. Keep mandatory retained content out of any projected savings calculation.
- Measure eligible live-file versions separately. Test any approved changes on a limited scope, preserve required evidence, and compare storage again after the service has processed them.
Which PowerShell command should I use?
Use Security & Compliance PowerShell—not a guessed PnP retention cmdlet. Get-RetentionCompliancePolicy lists retention policies; its DistributionDetail option provides distribution details. Get-CaseHoldPolicy inspects eDiscovery hold policies when you have the required case access. These read-only commands are starting points, not proof that no item labels or other holds apply.
# After connecting to Security & Compliance PowerShell
Get-RetentionCompliancePolicy -DistributionDetail
# For a specific case you are authorized to review:
Get-CaseHoldPolicy -Case "Case name"What can you safely change?
If compliance owners determine that a policy's scope is wrong, they can review it through the supported retention policy process. Do not remove tenant-wide coverage merely to reduce a bill. Other policies or holds may still retain the content, and cleanup is asynchronous rather than an immediate quota reset. Never manually purge the Preservation Hold Library or promise a specific amount of savings before measuring eligible content.
Smart Storage Analyzer provides read-only storage reports and per-file version-history size. It does not release holds or delete content; this guide does not claim it provides a dedicated Preservation Hold Library audit. Use the storage cost calculator only after distinguishing retained storage from content approved for cleanup. For the wider process, see the storage reduction playbook.
Get your first result in about 10 minutes
Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.
- Download the .sppkg package from the latest release.
- Upload it to your tenant App Catalog.
- Add the web part to a SharePoint page.
Email me when a new release ships
No marketing spam. One short email when a new release ships. You can unsubscribe anytime.
Was this page helpful?
One click. No form, no email address.
Missing something in SharePoint Smart Permissions? Feature requests and bug reports go straight to the developer on GitHub — no account needed to read, free account to post.
Request a featureRelated tool
SharePoint Smart Permissions
Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.
Keep reading
Microsoft 365 Archive vs trimming version history: which fixes SharePoint storage?
Archive, buy more storage, or trim versions? Each fixes a different problem. Here's how to choose, using Microsoft's current pricing rules.
How to Reduce SharePoint Storage: A Step-by-Step Playbook
Most tenants running out of SharePoint storage can recover a lot before buying more. This playbook puts the steps in order, from measuring to version trimming to archiving.
Trim SharePoint Version History: Automatic Limits That Reclaimed 30–40% Storage
A two-step change that can cut SharePoint storage substantially: turn on Automatic version limits for new sites, then run one PowerShell command per existing site. Exact retention schedule and script included.
Running out of storage?
Let our team build your storage cleanup plan
We find what is driving your storage use, set version-history and retention policies that fit your organization, and help you avoid buying extra storage.
About the author
Sean Regan
SharePoint & Microsoft 365 consultant with 20+ years of hands-on experience building SPFx web parts, migration tooling and tenant-grade automation. Maintainer of the open-source SharePoint Smart Solutions suite.
