How to Delete Old Versions in SharePoint
Sometimes you need to clean up version history — but most of the time, you shouldn’t. Deletion is permanent and removes audit trail.
What it is
Version history can grow large for actively-edited files. A document edited daily for two years might have hundreds of versions. Each version uses storage (though often small), and the long history can be hard to navigate. Some teams want to clean this up — and SharePoint allows it, but it’s worth pausing before you do.
The trade-off is straightforward: deleting old versions reduces clutter and storage, but removes audit trail. For everyday working files, that’s probably fine. For controlled documents (policies, procedures, regulated records), it’s almost certainly not — and may be a compliance violation depending on your industry.
A better approach in most cases is to set version limits at the library level, so SharePoint automatically keeps the most recent N versions and removes older ones. This is consistent, predictable, and doesn’t require manual intervention. Manual deletion of specific versions should be rare and deliberate — and never done on regulated content without checking retention policies first.
When to use this
- When a library has unnecessarily large version history slowing things down.
- When you need to free up storage on a heavy-use library.
- When you’re cleaning up a library after a major restructure.
- Almost never, for regulated or controlled content — check retention policies first.
How to do it
- First, confirm the library has versioning enabled and review your retention requirements.
- Open the file’s Version history.
- If you have permission, you’ll see a delete option next to older versions.
- Confirm exactly which versions you’re deleting.
- Keep at least one approved/published version even when cleaning up.
- For systematic cleanup, prefer setting version limits at library level over manual deletion.
- Document any deletions if your governance requires it.
Best practices
- Use version limits, not manual deletion. Set the library to keep e.g. 50 major versions and SharePoint handles cleanup automatically.
- Never delete versions of regulated content without checking retention. Some industries require keeping every version for years.
- Keep approved/published versions. Even in a cleanup, the official versions should remain.
- Restrict who can delete versions. Most users shouldn’t have this permission.
Common mistakes
- Deleting versions to ‘tidy up’ regulated content. Could create compliance violations. Check first.
- Deleting all versions including approved ones. Destroys audit trail entirely.
- Manual deletion when version limits would do the job. Inefficient and error-prone.
The File Sanity Kit gives you the Container Method™ — audit, restructure, and future-proof SharePoint without IT admin. The complete methodology, full workbook, and 8-tab Excel planner.
Get the File Sanity Kit — $27 →FAQ
How do I delete old versions of a SharePoint file?
Open Version History on the file. Find the version to remove, click the dropdown, choose Delete. The version moves to the Recycle Bin (recoverable for 93 days). To delete many old versions across a library, ask a SharePoint admin to run a PowerShell or Power Automate cleanup.
Why does my SharePoint library use so much storage?
Version history is usually the answer — each version of each file counts against your storage quota. A 5MB file with 500 versions consumes 2.5GB. Reduce by setting version limits in Library Settings -> Versioning settings. Common settings: 50 major versions, 10 minor versions per major.
Should I automate SharePoint version cleanup?
Yes for large libraries with thousands of files. Build a Power Automate flow that deletes versions older than X months, keeping the most recent N. Combine with version limits at the library level for layered protection. Manual cleanup of one file at a time is fine for small libraries; it doesn’t scale.
Will deleting SharePoint versions affect the current version?
No — deleting historical versions has no effect on the current version. The current version stays exactly as it was. Only the ability to roll back to deleted versions is lost. Keep the most recent 10-20 versions as a safety net; older versions are usually safe to remove.