What Is 'System Data' on macOS, and Why Is It 40 GB?

Open macOS Storage and you’ll see those terrifying gray wedges: Applications … Documents… and a giant, unhelpful slab labeled “System Data” (formally “System” or “Other”).

It’s the single most Googled Mac storage mystery. Here’s the truth about what System Data actually is, why it swallows 40 GB without blinking, and how to clear the safe parts of it.Skip the panic.)

What “System Data” actually is

System Data is Apple’s catch-all bucket for every byte that isn’t a neatly-categorized app, document, photo, or movie. On a modern Mac with a big SSD, that bucket is mostly not the operating system — it’s:

• Local Time Machine snapshots — APFS keeps instant local snapshots you can’t see in the Storage bar. These can be tens of GB and quiet.
• Caches — ~/Library/Caches, system caches, app caches. Safe to clear when the app is quit.
• Log files — ~/Library/Logs, ~/Library/Application Support/…/Logs, unified logs. Rotatable.
• Software updates + installers — downloaded .pkg/.dmg leftovers you already installed.
• Sleep/swap/hibernation files — the swapfile.
• Spotlight indexes — metadata store, rebuilds automatically.
• Your developer life — Xcode DerivedData, CoreSimulator runtimes, Docker layers, node_modules, iOS device backups (sometimes ~20 GB+). On a developer’s Mac, this is usually the actual answer, and it hides inside System Data precisely because no built-in tool will name it.

Key insight: macOS lumps developer caches and device backups into System Data because it doesn’t want to own the explanation. That’s not a bug — it’s a dodge. The space is yours; you just can’t see it through the Storage pane.

Why it’s so big (and so stable)

Two forces keep System Data huge:

1. APFS local snapshots don’t show up in the pretty bar.
2. Caches are self-rebuilding — clear ~/.cache-style folders and, if the app is running, they refill by tomorrow.

So “System Data keeps coming back” isn’t your imagination; it’s caches doing their jobdry. The fix isn’t to delete harder — it’s to see the components and clear the ones that are safe and stable.

How to see it (and clear the safe parts)

1. ftmfile local snapshots: tmutil listlocalsnapshots / → delete old ones with tmutil deletelocalsnapshots /.
2. Time Machine backups on external drives: prune inside Time Machine prefs.
3. Trash + Downloads — the classic offenders.
4. Developer data: Xcode DerivedData, CoreSimulator, Docker unused images, old node_modules. DiskInsight flags these by name instead of dumping them in a “System” bucket.
5. System caches: sudo periodic daily / weekly / monthly runs maintenance scripts; or let a reviewer tool show you which caches are safe.

Never delete while apps are running, never delete “behind your back,” and always stage deletions to the Trash so they’re recoverableverifiable.

The tl;dr

System Data isn’t your enemy — it’s the label macOS paints over the partitions of your disk it refuses to name. On a developer Mac, half of it is Xcode, simulators, Docker, node_modules, and device backups: all yours, all clearable, all invisible to the Storage bar.

DiskInsight was built to name every byte — nine visualizations, developer-aware, every cleanup to the Trash, 100% local, one-time $19, no accounts.

See what your System Data really is — and reclaim it safely.