The average Microsoft 365 tenant stores hundreds of gigabytes in files no one has opened in over a year. Most of it hides in corners: deep document libraries, forgotten project sites, and five years of version history on a single 200 MB CAD file. This guide covers five methods for locating large files across SharePoint Online, from the admin center down to scripted queries, so you can find the waste before it becomes a quota crisis.
What counts as a "large file" in SharePoint Online?
A large file is any item whose size, multiplied by its version count, meaningfully dents a site's quota. A single 2 GB video with no versioning is easy to spot. Harder to catch: a 15 MB PowerPoint presentation with 400 versions consuming 6 GB for a single document. The methods below surface both patterns: individual oversized items and libraries where version bloat has quietly overtaken the current file sizes.
SharePoint Online's base tenant storage is 1 TB plus 10 GB per licensed user. Unmanaged versioning and forgotten large files are the two fastest ways to exhaust that allocation without realising it.
Method 1: Find large files with the SharePoint admin center
The SharePoint admin center gives you a per-site-collection view of storage consumption. It is the fastest starting point when you do not know which sites are the problem.
- Sign in to the Microsoft 365 admin center and open SharePoint admin center.
- Go to Sites > Active sites.
- Click the Storage used column header to sort descending. The heaviest site collections rise to the top.
- Export the full list to CSV using the download icon if you need to analyse it in Excel or share it with the team.
This gives you the ranking of sites by total storage. It does not tell you which specific files or libraries inside those sites are responsible. That requires the next two methods.
Method 2: Site storage metrics page
Once you know which site is the heaviest, drill into its per-library breakdown:
- Open the SharePoint site in question.
- Go to Site settings > Storage metrics (listed under Site Collection Administration in the settings menu).
- The page shows a folder tree with storage totals at each level. Navigate into the document libraries consuming the most quota.
- Click a library to see per-folder detail, then navigate to individual files.
When versioning is enabled, each file shows a separate row for its current size and its version history size. A file where the version row is larger than the current-content row is a version-bloat flag worth investigating.
Method 3: Excel file report with Report Master
ShareMaster's Report Master exports a flat file list to Excel, including file name, library path, current size, version count, total version storage, author, and last modified date for every item in a library or across a full site.
What the report includes
- File name, library, and full path within the site
- Current file size and total version storage as separate columns
- Version count (how many copies SharePoint is holding)
- Created by, last modified by, and last modified date
- Content type
Once the report is open in Excel, a single sort on "Total size including versions" brings your top offenders to the top of the sheet. If you run the export across several sites, combine the CSV outputs and sort across the whole tenant view. This is the fastest path from "I know the site is heavy" to "I know exactly which files to address."
For libraries running automatic versioning under Microsoft's newer version management policy, the version count column is especially useful: files with hundreds of versions on a 50 MB document are exactly the kind of item that silently fills a quota over months.
Try Report Master free for 14 days
Method 4: Version history audit with the Version Trimmer
Version bloat is a distinct problem from single large files. A library full of Word documents averaging 3 MB each sounds modest until unmanaged versioning has run for five years and each document carries 300 versions.
Using Space Master's Version Trimmer
ShareMaster's Version Trimmer scans a document library or a full site and reports total version storage, average versions per file, and the oldest version dates across the library. You set a keep policy (for example, keep the 10 most recent versions, or keep all versions newer than 90 days) and the tool calculates exactly how much storage trimming to that policy would reclaim before you commit to the operation.
This pairs well with the Report Master file export: use Report Master to rank the heaviest libraries across a site, then use the Version Trimmer to calculate and reclaim version storage within those libraries without deleting the live files themselves. The two tools together give you a full picture of where the storage actually lives.
See also: How to trim SharePoint Online version history for a step-by-step walkthrough of the trimming process.
Method 5: PnP PowerShell (scripted approach)
When a GUI tool is not available, PnP PowerShell can pull file sizes from a single library. It works, but it requires scripting knowledge, a PnP app registration in Entra ID, and care around the list view threshold.
- Connect:
Connect-PnPOnline -Url https://<tenant>.sharepoint.com/sites/<site> -Interactive - Pull items:
Get-PnPListItem -List "Documents" -Fields "FileLeafRef","File_x0020_Size","Modified" - Export to CSV, open in Excel, and sort by
File_x0020_Size.
Limitations to be aware of: the File_x0020_Size field returns the current file size only. Version storage is not exposed through that field; you need a separate Get-PnPFileVersion loop per file to total it, which becomes slow and throttle-prone across a large library. Across a tenant with many sites, this script can run for hours and will hit Microsoft 365 throttling limits without a retry mechanism.
For occasional one-library checks, PowerShell is adequate. For tenant-wide or repeated audits, Report Master is faster and avoids the scripting overhead entirely.
Frequently Asked Questions
What is the maximum file size in SharePoint Online?
250 GB per file. In practice the bigger concern is volume: thousands of medium-sized files accumulating years of version history contribute far more to quota overruns than any single large upload.
Do file versions count against SharePoint storage quota?
Yes. Every stored version counts against the site quota. Binary files (PDFs, images, videos) store a full copy per version. Office documents use delta compression, so each version is smaller than a full copy, but the storage still compounds across hundreds of versions on active documents.
Does the SharePoint admin center show file-level storage?
No. The admin center shows storage only at the site collection level. File-level detail requires the per-site Storage Metrics page, a Report Master export, or a PnP PowerShell query against individual libraries.
How can I find large files across multiple SharePoint sites at once?
The native admin center stops at the site level. For cross-site file analysis, use Report Master to export file reports from multiple sites and combine them in Excel, or run Space Master's Version Trimmer across a list of sites to aggregate version storage data in a single session.