macOS gives you three different answers depending on where you look. Here's what each one actually measures, and how to find the real space hogs.
Open System Settings → General → Storage for a category breakdown, then use a disk-space analyzer to see the actual files behind those categories. Storage settings bucket your disk into broad labels — Apps, Photos, Documents, System Data — and a few of those buckets can't be opened at all. An analyzer walks the filesystem directly, so you see every folder and file with its real size, sorted largest first.
Apple's Storage pane groups everything on your startup disk into categories: Applications, Documents, Photos, Mail, Messages, Music Creation, Trash, and two catch-all buckets — macOS and System Data. The categories are convenient but coarse. Apple's own documentation notes that System Data contains “files that don't fall into the categories listed here” — primarily log files, caches, VM files, fonts, app support files and plug-ins — and that you can't manage the contents of this category. The pane also varies in size depending on the current state of the Mac, so two scans a week apart can differ without you deleting anything.
If System Data is the biggest block, that is the single most common reason people can't find their missing space. We wrote a full breakdown of System Data separately.
Select a folder, press ⌘I, and Finder reports a size. Two problems. First, folders containing many small files are slow to measure and Finder may still be counting when it shows you a number. Second, Finder reports logical size, not on-disk size. On APFS, clones and hard links mean two files can share the same physical blocks — so adding up Finder sizes can overstate what the data actually costs you.
That distinction matters: a disk analyzer should be able to tell you both the apparent (logical) size and the allocated size, and should be hard-link aware so shared blocks are counted once, not once per link.
A scanner walks your filesystem and builds a tree you can sort, filter and drill into. This is the only one of the three approaches that answers “what is the biggest thing on this disk?” directly. What to look for:
| Capability | Why it matters | |---|---| | Sorts by size, largest first | Turns “where did it go?” into a ranked list | | Logical vs. on-disk size | Clone-aware; stops double counting shared blocks | | Visualizer (treemap / sunburst) | Makes a 4-million-file tree readable at a glance | | Category filters | Highlights dev bloat — node_modules, DerivedData, Docker.raw | | Safe cleanup | Moves things to the Trash so a mistake is recoverable | | Local-only scanning | Your file names are sensitive; nothing should be uploaded |
In practice, the biggest wins on a modern Mac are rarely in your Documents folder. They are:
node_modules, package-manager caches (npm, pip, brew, Cargo, Gradle, Maven, CocoaPods, SwiftPM), and Docker's Docker.raw disk image.~/Library.Massive Disk scans with getattrlistbulk(2) — one syscall returning a batch of directory-entry attributes instead of a stat per file — across a worker pool. On an M2 Pro (release build, warm cache) a full home-folder scan covered 4,473,939 entries (3,625,939 files and 848,000 directories, 464 GB) in 38.1 seconds, about 3× faster wall-clock than du -sk on ~/Library alone (51s). It reports both logical and on-disk size, is hard-link aware, and offers a treemap, sunburst, icicle, bars, table and folder view over the same scan.
One note on permissions: macOS protects a handful of locations (Mail, Safari data, other apps' containers, Time Machine snapshots) unless the app is granted Full Disk Access in System Settings → Privacy & Security. Without it the scan still works, but those folders are reported as inaccessible rather than silently shown as zero — which is the honest behaviour you want.
Deleted files may still sit in the Trash until it is emptied, and Time Machine local snapshots can hold a copy of files you removed. Both are recoverable space that macOS reclaims on its own schedule.
They measure different things. Storage settings buckets files into categories using Spotlight, while Finder reports folder contents. Neither shows allocated-versus-logical size differences caused by APFS clones and hard links.
Only if it scans locally. File names and paths are sensitive, so a tool that uploads your directory tree to a server is a privacy problem. Massive Disk makes exactly two network calls: the Pro subscription check and the update check.
Massive Disk is a native Apple Silicon app that maps every byte of your storage across six visualizations — then gives you safe, reversible ways to get space back. Scanning is free forever; cleanup tools are Pro.