The 80 GB mystery: what "System Data" on your Mac really is — and how to shrink it
You open storage settings, and there it is: System Data, 80 GB, with no explanation and no button to clean it. Apple doesn't tell you what's inside, Finder doesn't show it, and it keeps growing.
Here's the good news: System Data isn't one mysterious blob. It's a handful of very ordinary things — caches, snapshots, leftovers — and most of them are safe to remove. Let's break it down.
What's actually inside System Data
macOS lumps into "System Data" everything that doesn't fit its other categories (Apps, Documents, Photos). In practice, the big chunks are usually:
| What | Typical size | Safe to clear? |
|---|---|---|
| App & browser caches | 5–20 GB | Yes — apps rebuild them |
| Time Machine local snapshots | 10–50 GB | Yes, if you have backups |
| Developer caches (npm, Xcode, Docker) | 10–60 GB | Yes — tools re-download |
| App leftovers from deleted apps | 1–10 GB | Yes |
| System logs and diagnostics | 1–5 GB | Mostly |
| macOS itself, dyld caches, VM swap | 15–25 GB | No — leave alone |
Step 1: Check Time Machine local snapshots first
This is the most common culprit and the most invisible one. macOS keeps local copies of your backups on your startup disk before they're written to your backup drive — and they don't appear in Finder at all.
Open Terminal and run:
tmutil listlocalsnapshots /
If you see a list of dated snapshots, they're occupying real gigabytes. You can delete a specific one:
tmutil deletelocalsnapshots 2026-08-15-120000
Step 2: Clear app caches — the right way
Caches live in ~/Library/Caches. The folder is safe to explore: sort by size and look at the biggest offenders — browsers, Spotify, Slack, design tools.
- Do: delete cache folders of apps you recognize. They'll rebuild on next launch (first launch may be slower).
- Don't: empty
/Systemor/privatefolders manually — that's where "one weird trick" articles get people into reinstalling macOS.
Step 3: Developers — your tools are hoarding
If you write code, odds are your biggest System Data chunk is developer junk:
npm cache clean --force— npm's cache can quietly reach 10+ GB~/Library/Developer/Xcode/DerivedData— safe to delete entirely; Xcode rebuilds it- Old
node_modulesfolders in projects you finished months ago — each one is 200 MB–1 GB, and they add up fast - Docker images and volumes:
docker system prune
Step 4: Leftovers from deleted apps
Dragging an app to Trash leaves its support files behind in ~/Library/Application Support, ~/Library/Preferences and ~/Library/Caches. Years of installing and deleting apps leaves gigabytes of orphans. You can hunt them manually by app name — tedious, but free.
What you should never touch
Swap files, /System, dyld caches, and anything you can't name. If a guide tells you to sudo rm -rf something inside /private/var — close the tab. The 2–3 GB you might free isn't worth an unbootable Mac.
Or just ask your Mac what's going on
Gigatidy is a conversational AI cleaner: it scans locally, explains what every gigabyte of System Data actually is, and clears only what's safe — with a checklist you approve first.
Meet Gigatidy →FAQ
Why is System Data so huge on my Mac?
Usually a combination of Time Machine local snapshots, app caches, and (for developers) tool caches. On a long-lived Mac, 40–80 GB is common — and most of it is reclaimable.
Is it safe to delete System Data?
You can't delete the category itself, and shouldn't try. But its biggest components — caches, snapshots, leftovers — are safe to clear individually, as described above.
Will clearing caches speed up my Mac?
Indirectly. macOS slows down when the startup disk is nearly full (memory swapping suffers). Freeing space below ~85% disk usage often makes a visible difference; clearing caches alone doesn't.