What a disk analyzer does that File Explorer does not
File Explorer shows you the size of a folder only after you right-click it and wait for Properties to finish counting — one folder at a time, no ranking, no comparison. A disk space analyzer scans the whole tree in one pass and sorts every branch by size, so the folder eating the most space is always at the top instead of buried three clicks deep.
That single difference — ranking instead of listing — is what turns a vague 'my C: drive is full' into a specific, three-click path to the actual files. For a walkthrough of that path, see finding large files on Windows.
How treemaps, pie charts and bar charts encode size
Most analyzers offer at least two views of the same data. A treemap divides a rectangle into nested tiles, where the area of each tile is proportional to the size of the folder or file it represents. Big tiles are big folders; a treemap lets you spot one huge file among thousands of small ones at a glance, because it will visibly dominate the rectangle.
A pie chart or bar chart does the same comparison but only for one level of the tree at a time — for example, the top-level folders on a drive. They're easier to read for a quick 'which of these five folders is the problem' question, but they don't show nested structure the way a treemap does.
Color in a treemap is usually assigned by file type or by top-level folder, not by size. Don't read color as a size signal — read tile area.
Logical size, allocated space, and cluster slack
Every analyzer can report at least two different numbers for the same file, and they rarely match.
- Logical size is the number of bytes the file actually contains — what you'd see if you opened its Properties dialog in File Explorer.
- Allocated space is what the file system reserves for that file on disk, rounded up to a whole number of clusters.
- Cluster slack is the gap between the two: unused space inside the last cluster a file occupies. On an NTFS volume with a 4 KB cluster size, a 100-byte text file still consumes a full 4 KB of allocated space.
The gap matters most on folders with huge numbers of small files — a source code checkout, a mail archive, a browser cache. A folder can look modest by logical size and noticeably heavier by allocated space once slack is added up across tens of thousands of files.
Scanning a whole volume vs. one folder
A full-volume scan answers 'where did my free space go' across the entire drive, including system folders, hidden folders, and other user profiles you may not normally see. It takes longer and, on a system drive, usually needs administrator rights to read every folder without gaps — see running a scan as administrator.
A single-folder scan is faster and is the right choice when you already know the problem is contained — a Downloads folder, a project directory, a specific user profile. Starting narrow and widening the scope only if the numbers don't add up is usually quicker than always scanning the whole drive.
What Windows Storage settings mean by "System" and reserved storage
Windows' own Settings > System > Storage screen gives a rough breakdown by category, but two entries confuse people specifically because a third-party analyzer can't fully explain them.
- System & reserved bundles the operating system files, the page file, hibernation file, and a chunk of space Windows sets aside for updates. It is not one folder you can scan and clean; a disk space analyzer will show you the pieces (like
pagefile.sys) but shouldn't be used to delete them by hand. - Reserved storage is space Windows deliberately holds back so an update has room to install even when a drive is nearly full. It shrinks the free space you see, but it isn't wasted or reclaimable in the normal sense.
Our comparison of Windows' built-in storage tools versus TreeSize goes through this in more detail if you want to see both side by side.
Visualize before you decide anything
The point of any of these tools is to look before you act. A treemap or a sorted folder list tells you where the space went; it does not tell you whether that space is safe to reclaim. Large folders are frequently supposed to be large — installed games, virtual machine disks, a video project's render cache — and deleting by size alone is how people break things.
Once you can see the shape of the problem, move to a deliberate decision process rather than an impulsive delete. Several implementations exist, and picking one comes down to interface preference and licensing more than raw capability; our comparison of TreeSize alternatives lays out the differences.
Short glossary
- Treemap — a nested-rectangle chart where tile area equals size.
- Logical size — the byte count of a file's actual contents.
- Allocated space — disk space reserved for a file, rounded to full clusters.
- Cluster — the smallest unit of disk space a file system allocates at once, commonly 4 KB on NTFS.
- Cluster slack — unused space inside a file's last allocated cluster.
- Reserved storage — space Windows holds back for updates, shown separately from user data.
Frequently asked questions
Why do two disk analyzers report different sizes for the same folder?
They're usually measuring different things — one shows logical size, the other allocated space — or one had permission to read a subfolder the other couldn't access. Check which size column each tool is displaying before assuming either is wrong.
Does a treemap show file type or size?
Is scanning a whole drive risky?
Why does Windows show less free space than my analyzer's totals suggest?
Continue reading
Last reviewed by the jam-software.org editorial team on . Spotted something out of date? Tell us.