Why is System Data so large on your Mac?

Updated September 2026 · 7 min read

You open System Settings › General › Storage and a grey bar called System Data is eating 80, 150, sometimes 250 GB. macOS doesn't say what's inside. On a Mac used for development or local AI, most of it isn't the operating system at all: it's build output, caches and model weights your tools keep and never clean up.

What "System Data" actually means

The Storage panel sorts files into categories it recognises: Applications, Documents, Photos, iCloud Drive, Developer and a few more. Anything it can't classify lands in System Data. That includes genuine system files (virtual memory swap, the sleep image, Time Machine local snapshots), but also every cache and hidden folder in your home directory, such as ~/Library/Caches, ~/.ollama, ~/.cache and ~/.npm.

That's why System Data grows fastest on developer Macs: the tools you use every day write gigabytes into places macOS files under "other".

The biggest culprits on a developer's Mac

WhatWhere it livesTypical sizeSafe to delete?
Local AI models (Ollama)~/.ollama/models4–40 GB per modelYes, re-download with ollama pull
Hugging Face / MLX models~/.cache/huggingface/hub2–30 GB per modelYes, re-downloaded on next use
LM Studio models~/.lmstudio/models4–40 GB per modelYes, re-download in LM Studio
Xcode DerivedData~/Library/Developer/Xcode/DerivedData5–60 GBYes, rebuilt on next build
iOS Device Support~/Library/Developer/Xcode/iOS DeviceSupport3–6 GB per iOS versionYes for versions you no longer test
Simulator runtimes and devices~/Library/Developer/CoreSimulator8–10 GB per runtimeYes, via Xcode or xcrun simctl
node_modules foldersInside every JS project0.2–2 GB eachYes, npm install restores them
Rust target/, Python venvsInside projects1–10 GB eachYes, rebuilt by cargo / pip
Package caches (npm, pip, Homebrew, Cargo, Gradle…)~/Library/Caches, dot-folders1–30 GB totalYes, refilled on demand
Docker images and build cacheDocker's virtual disk10–60 GBReview first: running containers need their images

Most of these are regenerable: deleting them costs a re-download or a slower first build, not lost work. The trick is knowing which ones you still use.

How big each of these really is, measured in September 2026, is in our developer disk-space report.

How to find what's using the space

From Terminal, this lists the largest folders in your home directory, including hidden ones:

du -sh ~/.[!.]* ~/* ~/Library/* 2>/dev/null | sort -hr | head -25

Then drill into whatever tops the list, for example du -sh ~/Library/Developer/*. It works, but it's slow, and it won't tell you whether a folder is safe to delete or when you last used it.

How to clean each one safely

Why System Data doesn't shrink right away

After cleaning, the Storage panel can take minutes to recalculate. Two other things hold space: files you moved to the Trash still count until you empty it, and Time Machine keeps local snapshots that macOS frees automatically when it needs room. tmutil listlocalsnapshots / shows them.

See all of it on one screen. Storage Cleaner scans for every item above, shows its size and when you last used it, marks each one Safe, Review or Caution, and cleans to the Trash so you can undo. Scanning is free.

Try Storage Cleaner free

Frequently asked

Is it safe to delete System Data? Not blindly. Much of it is regenerable developer data, but it also contains swap and system files that macOS manages itself. Clean specific folders you understand, not "System Data" as a whole.

Why is System Data bigger than my Xcode install? Xcode the app is ~12 GB, but its DerivedData, simulators and Device Support live in your Library folder and are counted as System Data, not Developer.

How much space will I get back? On Macs used for iOS development or local AI, 50–150 GB is common, most of it from a few old models, simulator runtimes and DerivedData.