Why is System Data so large on your Mac?
Short answer: “System Data” is not a category. It is the bucket macOS uses for every file it cannot file anywhere else — caches, app containers, virtual machine disks, downloaded AI models, old device backups and local snapshots. It grows quietly because nothing ever cleans it up, and macOS gives you no way to look inside it.
If you open System Settings → General → Storage and see a grey block labelled System Data taking 100 GB or more, you are not looking at system files. You are looking at everything macOS declined to classify.
What is actually inside System Data
On a 512 GB MacBook Pro that reported 96% full, the breakdown looked like this. None of it was visible in Finder without deliberately hunting for it.
| What it was | Where it lived | Size |
|---|---|---|
| Messaging app media | ~/Library/Group Containers/ | 92 GB |
| Dependency folders | node_modules across projects | 46 GB |
| Build output | 42 stale .next caches | 20 GB |
| Local AI models | ~/.ollama/models | 16 GB |
| Docker disk image | ~/Library/Containers/com.docker.docker | 14 GB |
| Orphaned Xcode runtimes | /Library/Developer/CoreSimulator | 13 GB |
| Developer caches | ~/.cache | 10 GB |
| Trash | ~/.Trash | 9.3 GB |
That is 220 GB of “System Data” that was, in reality, eight identifiable things.
Why it keeps growing
Three reasons, none of them a bug:
- Nothing prunes caches. Applications write cache and scratch files freely. Very few ever delete them. Video editing applications are the worst offenders — After Effects and Premiere disk caches routinely reach hundreds of gigabytes.
- Uninstalling an app leaves its data behind. Dragging an app to the Trash removes the bundle. Its container in
~/Library/Containersand its support files in~/Library/Application Supportstay exactly where they are, sometimes for years. - Some files are sparse. A Docker disk image can report 494 GB while occupying 9 GB, or the reverse — grow to hundreds of gigabytes while Docker itself reports a fraction of that.
The single biggest cause people miss
A forgotten screen recording. macOS will happily record for hours if the recording is never stopped, and the resulting file lands somewhere you never look. Cases of a single recording consuming 300–500 GB are reported regularly in Apple support threads. It is worth checking before anything else:
mdfind -onlyin ~ "kMDItemFSSize > 1000000000" 2>/dev/null
That lists every file over 1 GB in your home folder, using Spotlight rather than walking the disk.
What not to do
Two pieces of advice circulate widely and are both wrong:
“Delete everything in ~/Library/Caches.” Most of it is small and it will be rebuilt within minutes. The gigabytes are almost never there — they are in
Application SupportandContainers, which are not caches and hold real data.
“Reclaim your purgeable space.” Purgeable space is managed by macOS itself. No third-party application can reliably free it, and any tool claiming otherwise is overpromising. Why that is, in full.
How to find out what yours is
The numbers above are from one machine. Yours will differ. The next guide walks through clearing System Data safely, and if you would rather not use Terminal, Dustloft does the same measurement and shows you every item with its real size before anything is deleted.
See exactly what is on your own disk
Dustloft measures every real consumer of space on your Mac and shows each item with its full path and size before anything is removed. Free, open source, no subscription.
Install Dustloft