Folder inventory

Folder tree, sizes and file counts

The folder tree of a library, as a spreadsheet, with a size and a count on every branch. Use it when a library is too big and you need to know which part of it is the problem before you start moving anything.

What it tells you

• How big each folder is, including everything beneath it at any depth.
• How many files and how many subfolders each branch holds.
• Where the tree is deep or wide enough to cause trouble later, from each folder's full path in the Library Path column.
• Which folders are empty, since those are listed too rather than skipped.

How it runs

1. Sign in and pick a scope. Clicking the tile asks which account to use and how to connect, signs you in if you are not already, and drops you straight on the site list. No feature page asks you to connect a second time. You can stop at a site, a library, or a single folder inside one.
2. It walks the tree. Every folder under your scope, at every depth, with progress reported per folder rather than a spinner.
3. It rolls the numbers up. Each row carries its whole branch, not just what sits directly in that folder, which is what makes the sheet sortable by size.
4. Save the workbook. Summary first, then the Details sheet with a row per folder.

How it works

Only document libraries are read. A whole site expands into its libraries, and into its subsites when you ask for them; a library or folder you tick is read as it is. Libraries are read one at a time, and inside each the folder tree is walked from the top, level by level, one folder at a time, so the whole tree is known before any totals are worked out.

For each folder it reads SharePoint's own storage figure, which includes version history, and how many items the folder holds. ShareMaster works out what sits directly in each folder by taking its subfolders' figures off its own, then adds the tree back up from the bottom, so every row equals what sits in that folder plus every row beneath it. A figure that could not be worked out is left blank rather than shown as zero.

Sometimes SharePoint's folder figures are missing or plainly too low: a library that reports nothing at its root, or a folder whose figure counts fewer files than it is known to hold. For those folders, and the folders above them, ShareMaster reads the files instead and adds up their sizes. That figure covers current versions only, and the library is marked as measured from items so the difference is visible. If that read is itself incomplete, its numbers are not used and a note says so.

The library's Forms folder, which holds its views and templates, is not listed and its size is not counted. A folder whose subfolders cannot be listed keeps its own row, and the branch that could not be read is named in a note. A library whose top folder cannot be read is skipped and listed. The workbook goes into History as soon as the run ends.

What you get

An Excel workbook, named like contoso-folder-inventory-20260901-142207.xlsx, kept in Report History whether or not you save it. Every number on the Details sheet is recursive: that folder and everything below it.

Summary sheet

The run, the totals, and which libraries were measured without version history.

Details sheet

One row per folder, plus a run total at the top.

What you need

• Read access to the libraries in scope.

What it will not do

• Sizes are recursive and normally include version history, so a folder total will usually exceed what you see in the browser. Where a library's folder sizes cannot be read and its files are added up instead, those figures cover current versions only, and the Summary sheet says which libraries that applies to.
• A wide tree is a long read. Scoping to one library rather than a whole site collection is the difference between minutes and hours.
• Anything that had to be cut short or measured differently is listed on its own, not left for you to notice.

See every feature