Your SharePoint site storage report says 80 GB used. What it does not say is which files have accumulated hundreds of versions, or where a targeted trim would reclaim the most quota. That answer comes from a version count export.
This guide covers how to export per-file version counts from SharePoint Online to Excel using Report Master, how to read the results, and how to act on them without trimming anything you still need.
What does a version count report show?
A version count report lists every file in the scope you define with the number of stored versions next to it. The key data points are the current version count, the version history storage that count represents, the file type, and the library it lives in.
This is different from a library-level storage report, which shows you total storage and average version counts per library. The version count export goes to the file level: you can see that a specific shared template has 487 versions while the rest of the library averages twelve, and you can target that file directly rather than trimming the whole library with a broad policy.
Why per-file counts matter more than library averages
Version distribution inside a SharePoint library is rarely uniform. The pattern that shows up most often in practice: a small number of heavily-used files (shared templates, frequently updated plans, master reference documents) accumulate version counts far above the library average, while the majority of files sit in single digits. A library average of 35 versions might mask one file at 490 and three hundred files at twelve.
Applying a library-wide trim policy based on an average misses this skew. Setting a keep-last-50 policy against a library where most files have under twenty versions leaves the real outlier untouched while deleting history from files that needed it. The file-level report reveals the distribution before you commit to a policy.
For libraries storing PDFs, images, or other non-Office formats, version count matters even more. SharePoint stores a full copy of these file types per version rather than a binary diff. A 2 MB PDF with 200 versions occupies approximately 400 MB in version history. High version counts on large binary files are often the single largest source of reclaimable storage on a tenant.
How to export version counts from SharePoint using Report Master
Step 1: Connect with a SharePoint Administrator account
Open ShareMaster and sign in using an account that holds the SharePoint Administrator role in your Microsoft 365 tenant. This role allows Report Master to enumerate files and version data across site collections, including sites you are not personally a member of. A Global Administrator account also works but is more privilege than the task requires.
Step 2: Open Report Master and select the version count report
Navigate to Report Master and select the version count report type. Set the target scope: a single library gives you a fast, focused view of one area; a full-tenant scan surfaces outliers across every site and is the recommended starting point if you have never run this report before.
For tenants with hundreds of site collections, a full scan may take several minutes. Report Master queries the SharePoint API to collect per-file version data, and the time to complete scales roughly with the total number of files in scope.
Step 3: Run the report and export to Excel
Run the version count report. When it finishes, export to Excel. The export includes one row per file with columns for the site, library, file name, file type, current version count, and version history storage consumed by those versions. Auto-filters are applied on export so you can sort and filter immediately without reformatting the sheet.
Sort the version count column from highest to lowest to see the extreme outliers at the top, then by version history storage to find files where high counts translate to high quota consumption.
See what else Report Master exports
Reading the version count export
| Column | What it tells you | What to look for |
|---|---|---|
| Version count | Number of versions currently stored for this file | Files at or above 450 are close to the 500-version ceiling and may be losing their oldest history automatically |
| Version history size | Storage consumed by all stored versions of this file (not including the current version) | Sort by this column to find the highest-cost files regardless of their version count |
| File type | Extension of the file (docx, pdf, jpg, xlsx, etc.) | PDFs, images, and video files at high version counts are higher-cost than Office files because they store full copies |
| Last modified | Date of the most recent version | Files last modified two or more years ago with high version counts are strong cleanup candidates: the versions are unlikely to be needed |
| Library / site | Where in the tenant this file lives | Cluster your cleanup by library: it is more efficient to run the Version Trimmer against a whole library than file by file |
A practical approach: create two filtered views in Excel. The first filters for version count above 100 and file type not in (docx, xlsx, pptx, one). These are non-Office files with high counts and full-copy version storage. The second filters for version history size above 1 GB regardless of count. These are the two groups where trimming delivers the highest return per action.
What to do after exporting: prioritising version cleanup
Once you have identified which files and libraries carry the highest version load, there are two levers to pull.
Trim existing versions. For libraries where current version counts are high, use Space Master's Version Trimmer to apply a keep policy: retain the last N versions per file and delete anything older. A keep-last-30 policy applied to a library where the average file has 250 versions will reclaim roughly 88% of the version history storage from that library. For the specific outliers you identified in the export, you can target those files individually rather than adjusting the whole library's policy.
Set a lower version limit going forward. After trimming, set the library's version limit to a value that prevents the same accumulation from recurring. For most document libraries, keeping 30 to 50 major versions is sufficient. Use the guide to setting the SharePoint library version limit for the steps and recommended values by library type.
For a broader view of how version history fits into your overall storage picture, the guide to getting a SharePoint storage report by library covers the library-level storage breakdown that complements the per-file version count data.
Once you have trimmed the worst offenders, the guide to trimming SharePoint version history covers how to run Space Master's Version Trimmer across a site or tenant for systematic cleanup.
Frequently Asked Questions
What is the default version limit for SharePoint Online files?
SharePoint Online stores up to 500 versions per file by default. Once a file reaches that ceiling, each new version drops the oldest one. Files on high-traffic shared documents can reach 500 versions within months if no lower library limit has been set. Checking version counts regularly, and adjusting library limits after reviewing the data, prevents silent quota consumption from growing unnoticed.
Does a high version count always mean high storage consumption?
Not always. Office documents (Word, Excel, PowerPoint) use binary diff storage, so many small edits add up to less storage than their version count suggests. Non-Office file types, including PDF, image, video, and archive files, store a full copy per version. A 5 MB PDF at 200 versions consumes roughly 1 GB in version history regardless of how small the changes between versions were. Cross-referencing version count with file type in the export reveals which high-count files are actually high-cost.
How do I reduce version counts after identifying high-version files?
Use Space Master's Version Trimmer against the libraries identified in the export. Set a keep policy (for example, keep the last 30 versions and delete anything older) and run it against the target library or libraries. The trimmer removes excess versions from SharePoint storage and reclaims the quota. Current files and recent version history are not affected.