DiskLens › What is taking up space on my Mac
What Is Taking Up Space on My Mac?
macOS will happily tell you that 128 GB of "documents" and 40 GB of "System Data" exist — and stop there. Here is how to actually find the folders and files responsible, in a few minutes, for free.
Step 1 — Ask macOS itself (30 seconds)
Click the Apple menu → System Settings → General → Storage. The colored bar breaks your disk into Applications, Documents, iOS Backups, Mail, Messages, Photos, System Data and macOS. This answers "which category" — but not "which folder". Two things to know:
- "Documents" is a catch-all: any folder not managed by a system service, including your Downloads, Movies, virtual machines and random disc images.
- "System Data" grows on its own: caches, logs, local Time Machine snapshots. It is the category most likely eating tens of gigabytes you can reclaim — we break it down in Mac System Data, explained.
Step 2 — See the real folder sizes (the missing feature)
Finder does not total up folder sizes by default — which is why "what is taking up space on my Mac" is such a common question. You have three options:
- Finder, per folder: press ⌘J in a Finder window, enable "Calculate all sizes", then sort by Size. Slow — Finder re-counts every time.
- Terminal: du -sh ~/* 2>/dev/null | sort -h lists your home folders by size. Fast but text-only.
- A visual analyzer: a treemap shows every folder as a rectangle sized by disk usage — big blocks jump out instantly. That is exactly what DiskLens does, and unlike desktop apps you don't install anything:
…or drag & drop a folder. 100% local — nothing uploads.
Where the space went
Top 50 largest files
Duplicate candidates
Step 3 — The usual suspects (check these first)
After mapping thousands of disks, the space is almost always in the same ten places. Work down this list against your own map:
- ~/Library/Developer — Xcode's DerivedData and simulators quietly consume 20–100 GB. Fully regenerable; safe to delete.
- Old installers in ~/Downloads — every .dmg you ever downloaded and forgot. 5–10 GB is typical.
- ~/Library/Caches — browser and app caches. Safe to clear; apps rebuild them.
- node_modules / venv / build folders — if you write code, every project has a regenerable dependency folder several hundred MB deep.
- ~/Library/Application Support/MobileSync/Backup — old iPhone backups, 4–10 GB each, often for devices you no longer own.
- Movies & screen recordings — 4K video is ~350 MB per minute. Two holiday clips can outweigh everything else combined.
- Duplicates — "final_v2.mov", "final_final.mov". Our duplicate finder flags them automatically.
- VM images & containers — Parallels/UTM disks and Docker data never shrink on their own.
- Messages attachments — years of photos inside iMessage, counted under "Messages" in Storage Settings.
- Local Time Machine snapshots — invisible in Finder, 10–50 GB. They expire on their own; tmutil listlocalsnapshots / shows them.
What NOT to delete
Inside the map, big is not the same as deletable. Never remove anything in /System, /Library (system-wide) or ~/Library unless you know exactly what it does — and treat photos, documents, code and archives as "back up first", never "delete". DiskLens color-codes this distinction for every file: red means regenerable junk, blue means back-it-up-before-any-cleanup.
Frequently asked questions
How do I see what is taking up space on my Mac?
Apple menu → System Settings → General → Storage shows categories. For folder-level detail, use a visual analyzer like DiskLens (browser-based, nothing installed) or DaisyDisk (native app).
Why is System Data so big on my Mac?
Caches, logs, local Time Machine snapshots and app containers accumulate there — commonly 20–60 GB. Most of it is reclaimable; see our System Data guide for the safe steps.
What can I safely delete?
Xcode DerivedData, old .dmg installers, browser caches, node_modules and other build output. Anything regenerable is safe; anything you cannot recreate (photos, docs, code) should be backed up, not deleted.
Is a web-based analyzer safe for my files?
Yes. The browser only grants the page access to the folder you pick, processing happens locally, and DiskLens never uploads file contents.