What is System Data on Mac (and why it's so big)

Berkay Turk · Updated 2026-11-10

System Data is the one number the Storage panel in System Settings shows for the used space that is not macOS, Apps or Your files. It holds swap and system databases, data that apps keep for themselves, caches, logs and temporary files, and things that do not come back by themselves, such as local models, simulators, worktrees, Docker images and session histories.

That last group is why the number gets so big on some Macs. The rest of this page shows what is inside it, using one real Mac as the example, and which parts are worth your attention.

Where the number comes from

Open System Settings, then General, then Storage. The bar at the top splits the used space of your disk into categories: Apps, Documents, Photos, Messages, macOS and a few more. Most of them have a list behind them. You can see which apps are large, or which documents.

System Data is the remainder. macOS adds up what it can put into a named category, and everything else on the disk goes into System Data. There is no list behind it, so the panel gives you a size and nothing to act on.

This is also why the number can feel random. It moves when you install Xcode, when a simulator downloads, when Time Machine takes a local snapshot, or when an app decides to keep a large cache. None of these show up anywhere else in the panel.

The same disk, two ways of counting

Wipecraft starts from the same used space. It splits every used byte into four parts that add up to the total: macOS, Apps, Your files and System Data. Then it splits System Data again into five buckets, by what happens if you remove something.

The buckets answer one question each.

• Your Mac needs this. Swap, system databases and the data that apps keep for themselves. Shown, never offered for removal.
• Safe to remove. Caches, logs and temporary files that their app rebuilds on its own.
• Comes back. Removable, but it fills up again with use, such as browser and package caches.
• Your call. The only copy of something that does not come back by itself: local models, emulators, simulators, worktrees, Docker images and session histories.
• Not shown by macOS. What is left after everything that can be named, with a reason, such as Full Disk Access being off or folders that only an administrator can read.

The full rules for each bucket are on How it works.

One real Mac, measured

This is the author's own Mac, an M2 Pro used every day for app development with Xcode, Android Studio, Docker and AI coding agents. Wipecraft scanned it on 2026-11-08.

System Data was 271.1 GB. Split into buckets:

Not shown by macOS was empty on this scan.

Read the table from the top. Almost half of System Data was space the Mac needs to run. No cleaner should touch it, and a cleaner that offers to is guessing. The safe part was large, but it is mostly caches, and caches grow back as you use the apps that made them. The part that decides how much space you really get back is Your call.

The largest single sources on the same scan:

These rows are the sizes of single sources: every item a source left on the disk, counted together. One source can spread across several buckets. Most of a simulator runtime is your call, a part of it is something your Mac needs right now, and a part is safe to remove. So the rows are not a split of the buckets above and they do not add up to them; a single source can even be larger than the bucket that holds most of it.

Why it gets so big

Three things make System Data large, and they add up over months.

Caches without a limit. Most apps keep a cache, and most never shrink it. A browser, a design tool and a package manager can each hold several gigabytes. Each cache is reasonable on its own. Together they are a large part of the number.

Copies you forgot you made. A simulator for an old iOS version, an Android emulator from a project you finished, a local model you tried once, a Docker image from last spring. These are real files that took time to download or build. No app removes them for you, because no app knows that you are done with them.

Things macOS keeps for itself. Swap files grow when memory is tight. Time Machine keeps local snapshots on the disk until it needs the space. Spotlight and other system services keep their own databases. These belong in System Data, and they are not yours to remove by hand.

Why it comes back after you clean it

If you delete caches, System Data drops, and a week later most of it is back. That is the caches doing their job. The app rebuilds what it needs the next time it runs. Removing them again gets you the same space for another week.

Simulators and package caches behave the same way. Xcode downloads a simulator runtime again when a project asks for it. A package manager fills its cache again on the next install. That is why Wipecraft keeps Comes back apart from Safe to remove: both can go, but only one of them stays gone for long.

Space that stays free comes from Your call. When you remove a model you will not use again, or a worktree whose branch is merged, it does not grow back.

What is safe to clear by hand

You can do most of this without any app. The short version:

• Usually safe. The caches of an app that is closed, in ~/Library/Caches. Xcode's build data in ~/Library/Developer/Xcode/DerivedData. Simulators that no installed Xcode can run, with xcrun simctl delete unavailable.
• Your decision. Local models, emulators, simulators you still use, Docker images and old iOS backups. Each one is the only copy. Check what it is and when you last used it before you remove it.
• Leave alone. Anything under /System, /private/var and the swap files. Removing these by hand can stop the Mac from starting.

Time Machine local snapshots are a special case. You can list them with tmutil listlocalsnapshots /. macOS does not report the size of a local snapshot, and removing one cannot be undone.

Developer tools and AI agents

On a Mac used for development, most of Your call comes from these tools. Each tool keeps its own data in its own place, and none of them knows about the others.

Xcode keeps build data per project, archives, device support files and previews. Simulators are full copies of iOS, one per device, plus the runtime images they boot from. Android emulators and SDK system images are the same idea for Android. Docker keeps images, volumes and a build cache, and on a Mac all of it lives inside one large disk image file.

AI coding agents add a newer layer. They work in git worktrees: full copies of a repository, one per task, each with its own build output. An agent can make several in a day, and they stay after the task is done. Claude Code and Codex keep session histories, file history and logs. Claude Desktop keeps VM bundles for its sandbox. Local models from Ollama, LM Studio or the Hugging Face cache are often several gigabytes each.

On the Mac above, these were the largest sources on the whole scan. Each of them came from work that was useful at the time.

This data needs more care than a cache. A worktree can hold changes that were never committed. A session history may be the only record of why a change was made. A simulator may be running. Wipecraft locks rows like these: a worktree with uncommitted changes, a booted simulator, the sessions an agent has open. You can see them, but you cannot select them. Items in Your call go to Quarantine, where you can undo them for 30 days. The rules are under how undo works.

What to do with this

If System Data is large on your Mac, start with Your call. That is where the space that stays free is, and it is the part that needs a person to decide. Caches can wait. They come back anyway.

To see the same buckets for your own disk, Wipecraft scans without a license and changes nothing while it scans.

See what Wipecraft finds on your Mac