What is "System Data" on a Mac — and how to clear it

What System Data actually is

"System Data" (formerly "Other" before macOS Monterey) is Apple's catch-all for everything that doesn't fit into Documents, Apps, Photos, Music or Browser. It includes:

• Local Time Machine snapshots: incremental backups stored on your internal disk.
• Application Support: databases, state, and hidden files apps never advertise.
• Caches: system caches, app caches, iCloud sync state.
• Containers: sandboxed app data and its hidden support files.
• Language packs: localization files downloaded per-app.
• Build caches (developer machines): Xcode DerivedData, npm/pnpm caches, Docker images and build layers.

Apple doesn't break this down for you — you just see the aggregate bar.

Why it balloons — and why it stays big

Two forces keep the System Data bar huge even after you clean it:

• Local Time Machine snapshots don't show up in the Storage bar at all. APFS keeps instant snapshots on your internal disk, and they can quietly eat tens of GB.
• Caches are self-rebuilding. Clear ~/.cache-style folders and, if the owning app is still running, they refill by tomorrow.

So "System Data keeps coming back" isn't your imagination — the fix isn't to delete harder, it's to see the components and clear the ones that are safe and stable. The honest way to see them is a disk analyzer that scans every folder and file, not just the ones Apple surfaces in Storage.

How to find what's actually inside it

The honest way is a disk analyzer that scans every folder and file, not just the ones Apple surfaces in Storage. DiskInsight scans a folder, your home directory, or the whole Mac, maps everything with an interactive treemap, and shows you the exact byte costs of every subfolder — including the ones Apple lumps into System Data.

• Scan the whole Mac in one pass.
• See the real byte costs of DerivedData, Docker, caches and containers.
• Stage anything suspicious to the Trash with full preview — nothing deleted permanently.

Clearing the safe parts, in order

1. Prune local APFS snapshots: tmutil listlocalsnapshots /, then delete the old ones with tmutil deletelocalsnapshots /.
2. Prune Time Machine backups on external drives inside Time Machine preferences.
3. Empty Trash and Downloads — the classic quiet offenders.
4. Clear developer data: Xcode DerivedData, CoreSimulator, unused Docker images, old node_modules.
5. Run system maintenance scripts: sudo periodic daily / weekly / monthly, or let a reviewer tool show you exactly 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 recoverable. Nothing DiskInsight cleans is ever deleted permanently without your say-so.

The safe approach (no blind deletes)

System Data is big, but most of it is important. Caches are generated on demand, so clearing them is safe (the next launch rebuilds them). Snapshots can be removed from Terminal if they're local. But Application Support and Containers hold real app state — delete those and the app forgets everything.

The safest approach is to scan, identify the largest items first, and clean each one deliberately. Nothing should be deleted wholesale. DiskInsight stages everything to the macOS Trash, so you always have until you empty the Trash to change your mind.

The macOS Storage tab alone isn't enough

Apple's Storage tab shows "System Data" as a single number with no breakdown. A disk analyzer shows you exactly which folders and files contribute to it — and lets you act on them. The difference between "50 GB of System Data" and "17 GB of DerivedData, 11 GB of Docker images, and 9 GB of local Time Machine snapshots" is the difference between confusion and clarity.