Disk analysis
How a Disk Space Analyzer Reads a Drive
A disk space analyzer answers a plain question: which folders hold the bytes? A disk usage analyzer on Windows usually starts at a drive letter, walks the folders it can open, and adds file sizes into parent totals.
Updated October 21, 2026. Windows menus can differ by version and by settings on the PC.
The scan is an inventory, not a verdict. A large total means a large amount of recorded data under that folder. It does not, by itself, mean the folder is safe to remove. Windows, games, video projects, and backups are supposed to be large.
What the scan does
-
Choose a root
The root is the drive or folder you asked to inspect. Everything outside that root is absent from the result.
-
List each level
The scan records files and steps into folders. If Windows denies access, that branch is missing or partial.
-
Roll the sizes upward
A folder total is the sum of what was found inside it. The parent should not add those same bytes a second time.
-
Present the totals
A table sorts them. A treemap draws them. Either view is only as complete as the walk that produced it.
How file size is calculated
A file has a logical size: the byte length stored for that file. On disk, NTFS allocates space in clusters. A 1 KB file can occupy a 4 KB cluster, which is a common allocation unit, though the size depends on how the volume was formatted. Explorer shows both ideas in Properties as Size and Size on disk.
A disk usage analyzer has to pick one of those numbers. A tool that adds logical sizes can report less than the used-space figure for the volume, because clusters, restore points, and reserved areas are not ordinary file lengths. A tool that adds every file it sees, and ignores hard links, can report more than the volume holds. The component store under Windows uses hard links, so a naive sum of C:\Windows can count the same bytes more than once.
How folder hierarchy is evaluated
Hierarchy is membership. Documents inside a project folder belong to that folder, and that folder belongs to your user profile. A good result lets you move down one level at a time without losing the total you came from.
Display depth is a separate choice. A picture that draws every file on a full drive becomes unreadable, so visual tools often stop drawing tiny items until you zoom. The bytes are still in the parent total. They are just not labeled yet.
What the numbers mean
| Sample category | Size | Share | How to read it |
|---|---|---|---|
| Applications | 48 GB | 21.1% | Installed software in the sample, including a design suite with subfolders. |
| Documents | 12 GB | 5.3% | Office files, PDFs, and project notes. |
| Pictures | 22 GB | 9.6% | Camera photos, screenshots, and edited images. |
| Videos | 64 GB | 28.1% | The largest sample category: project footage, exports, and short clips. |
| Downloads | 18 GB | 7.9% | Installers, archives, and other downloaded files. |
| Backups | 36 GB | 15.8% | Disk images and phone backups kept on the sample drive. |
| System Data | 28 GB | 12.3% | A simplified stand-in for Windows files, restore points, and temporary files. |
Compare a real scan with the used space shown for that same drive in Settings. A close match means the walk saw most of the volume. A large gap means the two tools are counting different things, or the scan could not open part of the tree. The storage problems guide walks through that gap.
What a disk analyzer cannot detect
Often visible in the result
- Folders the account is allowed to read
- Which child holds most of a parent total
- Personal libraries such as video, pictures, and downloads
- Installed software that lives in ordinary program folders
Easy to miss or misread
- Files another user owns, or folders Windows blocks
- Reserved storage that is not a normal folder of documents
- Cloud files that Explorer lists but that are not fully stored locally
- Whether a large folder is safe to delete
If you want to practice the picture before you open a real drive, the interactive treemap uses this same sample. For a closer reading of area, color, and nesting, continue with the disk space visualizer.