Latent

What is System Data on a Mac? What a developer Mac keeps there and what is safe to remove

2026-11-01 · about 5 min · by the Latent team

Open System Settings › General › Storage on a developer's Mac and the biggest bar is often a grey one called System Data, sometimes 100 GB or more, with no way to open it. It is not one thing. It is everything macOS could not file under a named category, and on a machine that runs Docker, Xcode and local models, most of it belongs to those tools.

In short
  • System Data (called Other on older macOS) is the leftover category: caches, logs, virtual memory, local snapshots, and data that apps keep in library or hidden folders.
  • On a developer Mac the heavy parts are usually Docker's disk image, model weights from Ollama, LM Studio and Hugging Face, Xcode simulator runtimes and package caches.
  • There is no safe way to "clear System Data" as a whole. Name each part, then remove it through the tool that owns it. Leave swap, the sleep image and anything under /System to macOS.

Why the Storage panel cannot tell you more

The Storage panel sorts files by kind: Applications, Documents, Photos, iCloud Drive, Mail, macOS, and a Developer item for some Xcode data. A 40 GB Docker disk image is not a document, an Ollama model is not an app, and a folder called ~/.cache is invisible in Finder. macOS has no category for them, so they all land in System Data, next to its own caches and swap.

That is why cleaning tips written for ordinary Macs (clear browser caches, delete old iPhone backups) barely move the number on a developer machine. The weight is in places those tips never mention.

Find out what is inside yours

Three commands cover most developer Macs. The first lists the heaviest hidden and library folders in your home directory:

# Heaviest hidden folders and Library subfolders in your home
du -sh ~/.[!.]* ~/Library/* 2>/dev/null | sort -h | tail -20

# Inside Docker Desktop's disk image
docker system df

# Simulator runtimes installed by Xcode (each one is several GB)
xcrun simctl runtime list

Terminal needs Full Disk Access (System Settings › Privacy & Security) to read some ~/Library folders; without it du prints permission errors and undercounts.

What a developer Mac usually keeps in System Data

The marks follow the same rule as our other guides: R comes back on its own (rebuilt or re-downloaded), I is in your hands because it may be the only copy, P belongs to macOS and should not be touched.

WhatPathTypical sizeSafe to remove?
Docker Desktop disk image~/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw20 to 100 GBR Images re-pull; I volumes may hold databases
Ollama models~/.ollama/models4 to 5 GB per 7B modelR Re-downloaded with ollama pull
Hugging Face cache~/.cache/huggingface/hub5 to 100 GBR Re-downloaded from the Hub
LM Studio models~/.lmstudio/models (or the folder you chose)5 to 100 GBR Re-downloaded from the app
Xcode simulator runtimes/Library/Developer/CoreSimulatorabout 7 to 10 GB eachR Re-downloaded from Apple when needed
Simulator devices~/Library/Developer/CoreSimulator/Devices2 to 30 GBR Unavailable ones; active devices hold test app data
App and package caches~/Library/Caches, ~/.npm, ~/.cache5 to 40 GBR Rebuilt on use
Coding agent sessions and logs~/.claude, ~/.codex, ~/.cursor and similar0.5 to 10 GBI Your conversation history lives here
iPhone and iPad backups~/Library/Application Support/MobileSync/Backup5 to 100 GBI May be the only backup of a device
Local Time Machine snapshotsAPFS snapshots (tmutil listlocalsnapshots /)variesI Backups; macOS removes them when space runs low
Swap and sleep image/private/var/vm1 to 20 GBP Managed by macOS; a restart shrinks swap

Remove each part the way its tool expects

Deleting these folders in Finder works for some and breaks others. Model stores share files between models and keep an index; Docker keeps everything inside one disk image. Use the owner's command:

# Docker: unused images, containers and build cache
docker system prune -a
docker volume ls                 # look before you prune volumes; databases live here

# Ollama
ollama list
ollama rm <model>

# Hugging Face (newer CLI; older versions: huggingface-cli delete-cache)
hf cache ls
hf cache rm model/<org>/<name> --dry-run   # then without --dry-run

# Xcode simulator runtimes and devices
xcrun simctl runtime list
# preview runtimes unused for 90 days, or delete one by its identifier
xcrun simctl runtime delete --notUsedSinceDays 90 --dry-run
xcrun simctl delete unavailable

# Package caches
brew cleanup --prune=all
npm cache clean --force
pip cache purge

LM Studio models are removed from its My Models view. Simulator runtimes can also be removed in Xcode's settings under Components (Platforms in older versions).

Leave /private/var/vm, anything under /System, and folders you cannot name. Swap and the sleep image come straight back, and an unknown folder may be the only copy of something. If a cleanup tool offers to "clear System Data" in one click, ask what is inside first.

Why the number does not drop right away

Questions people ask

What is System Data on a Mac?

It is the catch-all category in System Settings, General, Storage for files macOS cannot put under a named category such as Applications, Documents or Photos: caches, logs, virtual memory, local Time Machine snapshots, and data that tools keep in hidden or library folders. Older versions of macOS called it Other.

Why is System Data so large on a developer Mac?

Because developer tools store their heaviest data where macOS has no category for it: Docker Desktop's disk image, Ollama, LM Studio and Hugging Face model weights in hidden folders, Xcode simulator runtimes, and package manager caches. Together these commonly reach 50 to 200 GB.

Is it safe to delete System Data?

Not as a whole, and there is no button for it. Remove the parts you can name through the tool that owns them, for example docker system prune, ollama rm, hf cache rm or xcrun simctl runtime delete. Leave swap, sleep image and anything under /System to macOS.

Why did System Data not shrink after I deleted files?

Three usual reasons: the files are still in the Trash, a local Time Machine snapshot still references them until macOS removes the snapshot, or the Storage panel has not recalculated yet. Empty the Trash, check tmutil listlocalsnapshots /, and reopen the panel after a few minutes.

Open System Data, tool by tool

Latent scans the same places, puts every store under the tool that made it, and marks each one R, I or P with the reason. Free to scan, and your first 10 GB of cleanup is free.

Download for MacHow it works