What's Taking Up Space on Your Mac? (And Why You Can't Tell)
By Anjasmoro Bayu, developer of FileNav
Every Mac owner eventually meets the same dialog: "Your disk is almost full." And every Mac owner then opens the storage settings, stares at a colorful bar where the biggest segment is labeled System Data, and thinks: okay… and what exactly am I supposed to do with that?
This article is about why that moment is so frustrating, why clicking through folders almost never finds the real culprit, and why a disk visualizer — any disk visualizer, though I'll obviously show you mine — turns an evening of detective work into about a minute of clicking.
The storage bar that tells you nothing
Apple's built-in storage overview groups your disk by category: Applications, Documents, Photos, and the infamous System Data. Categories sound helpful until you need to act on them. Say the bar shows 80 GB of "Documents." Which documents? Where? The panel won't tell you. And System Data is worse — it's a grab bag of caches, logs, old backups, developer junk, and anything else macOS couldn't classify. I've seen it swallow a third of a drive.
The core problem: categories tell you what kind of data you have, but deleting happens by location. You can't right-click a category. To free up space you need a path to a folder — and that's exactly the thing the storage panel hides.
Why you can't find it by browsing
So you do what any reasonable person does: you open your home folder and start looking around. This fails for three reasons, and none of them are your fault.
First, Finder doesn't show folder sizes by default.In list view, every folder just says "--". There's a setting to fix this (View Options → "Calculate all sizes"), but it's off by default and per-folder sizes calculate lazily while you wait. Most people never find the checkbox at all.
Second, numbers in a list are hard to compare.Even with sizes visible, a column reading 1.2 GB, 348 MB, 24.6 GB, 891 MB doesn't look like anything. You have to read each value, parse the unit, and do mental math. Our eyes are bad at comparing numbers and excellent at comparing areas — which is the entire reason pie charts exist.
Third — and this is the killer — the big stuff is buried.Disk space problems are almost never one giant file sitting in plain sight. They're a folder, inside a folder, inside a folder you forgot existed. Old iPhone backups live five levels deep in ~/Library. Xcode's cache folder quietly grows to tens of gigabytes. A node_moduleshere, a forgotten video export there. Browsing top-down means checking every branch of a very large tree, and you'll give up long before you find the one that matters.
The Terminal crowd will point out you can run du -sh *and sort the output. True! I did that for years. It works, one directory at a time, in a monospaced wall of text, and you get to re-run it for every level you descend. It's the same drill-down a visualizer does — just with you as the rendering engine.
What a disk visualizer actually does differently
A disk visualizer does two things, and the combination is what makes it work.
It shows proportion instead of numbers.Your folder becomes a chart where each item's slice matches its share of the space. You don't read anything — you just see it: that folder is a third of everything. Your visual system does in a glance what your inner accountant needs minutes for.
It lets you follow the big slice down. Click the biggest slice, and the chart recalculates for that folder. Click the biggest slice again. Space hogs are nested, so this is exactly the search you need: each click eliminates everything else. Three or four clicks usually lands you on the actual culprit — the 40 GB of old simulator files, the downloads folder from 2023, the video project you already delivered.
That's it. That's the whole trick. Proportion plus drill-down. It sounds almost too simple to pay for, which is probably why everyone tries browsing and Terminal first — I certainly did.
How this works in FileNav
In FileNav the disk visualizer lives in the preview panel, so it's part of normal browsing rather than a separate ritual. Select any folder, open the preview panel, and you get a ring chart with the folder's true total in the center — including everything nested inside it.
- Below the ring, the top 15 items are listed largest-first, each with its size and percentage side by side. Everything smaller gets grouped into an "Others" bucket so the list stays readable.
- Click any item in the list and FileNav navigates into that folder — and the chart recalculates for it. That's the drill-down loop: keep clicking the big one until you hit bottom.
- Scanning runs in the background, so the app stays responsive while big folders are being measured. Selecting a different folder cancels the scan and starts a new one.
- One small detail I'm fond of: it respects your hidden-files setting. If you show hidden files, the chart includes them — which matters, because the space eaters love hiding in ~/Library and other dotted corners.
Fair warning about the limits: it measures local folders. Cloud-only folders (Google Drive, OneDrive and friends) don't report meaningful local sizes, so FileNav doesn't pretend otherwise.
The honest alternatives
Dedicated disk-analyzer apps exist and some are genuinely good — DaisyDisk is lovely, GrandPerspective and OmniDiskSweeper are free and have been around forever. If all you want is a once-a-year deep clean, one of those plus Finder will serve you fine.
The reason I built it into FileNav instead: cleanup isn't an annual event, it's a byproduct of noticing. When the visualizer is one panel away while you're already working with your files, you catch the 12 GB folder in passing, months before it becomes a crisis. A separate app you have to remember to launch tends to get launched only when the disk-full dialog is already on screen. (If Finder's other habits annoy you too, I've written a fuller comparison of FileNav and Finder.)
Before you start deleting
A visualizer will happily show you enormous folders whose names mean nothing to you. Two rules keep you out of trouble:
- Don't delete what you can't name. If a folder deep in ~/Library or /Systemis huge and you don't know what it does, look it up first. Some caches rebuild harmlessly; some folders are load-bearing.
- Start with the usual suspects.Downloads, old video exports, forgotten disk images, developer caches (Xcode alone is famous for this), and duplicate copies of things you've already backed up. These are boring, safe, and usually plenty.
The good news is that the visualizer makes both rules easy to follow — you're always looking at real folders with real names in their real locations, not an anonymous "System Data" blob. You decide what goes; you just finally get to see what's there.
Give FileNav a try
Free for 14 days with full Pro features. No credit card, no account. If it doesn't click, delete it and you've lost nothing.