All articles
Guides3 min readNovember 7, 2026

What Is “System Data” on Mac Storage, and How to Shrink It Safely

System Data can take 50 GB or more and macOS doesn't say what's inside. Here's what it actually contains, what's safe to clear, and what you should leave alone.

Clearbay TeamGuides from the people building Clearbay

Open System Settings → General → Storage and you'll often see a big grey block labelled System Data. On many Macs it's 30, 50, even 100 GB, and macOS gives you no way to look inside it. It's the most confusing part of Mac storage, so let's open it up.

What “System Data” actually is

System Data isn't one thing. It's everything macOS can't neatly put into Applications, Documents, Photos or the other categories. Typical contents:

  • Caches from apps and macOS (~/Library/Caches and system caches).

  • Time Machine local snapshots — hourly snapshots macOS keeps on your internal disk when your backup drive isn't connected.

  • iPhone and iPad backups made by Finder (~/Library/Application Support/MobileSync/Backup).

  • Developer data: Xcode DerivedData, simulators, device support files.

  • Virtual machines and container images (Docker Desktop, Parallels, UTM).

  • Logs, app support files, and the swap and sleep image files macOS uses for memory.

“Purgeable” space: the part macOS cleans for you

Some of System Data is marked purgeable. That includes local snapshots and some caches, which macOS deletes automatically when it needs room. In Finder, select your disk and press ⌘I to see “Available” space, which includes purgeable space. If “Available” is much larger than “Free”, macOS will reclaim that space on its own when an app asks for it.

What's safe to clear

iPhone and iPad backups

Often the single biggest item. Go to Finder → your iPhone → Manage Backups and delete backups for devices you no longer own. If you want to keep a backup but not on your Mac, move the backup folder to an external drive first.

Old developer data

If you use Xcode, ~/Library/Developer/Xcode/DerivedData and old iOS DeviceSupport folders can be huge. Both rebuild when needed. Unused simulators can be removed with xcrun simctl delete unavailable.

App caches

Caches rebuild themselves, so removing one won't break the app, but it will be a bit slower the first time. Focus on the few big ones rather than clearing everything.

Virtual machines and container images

Docker Desktop keeps all images in one large disk image. Use Docker Desktop → Troubleshoot → Clean / Purge data or docker system prune rather than deleting the file by hand.

What to leave alone

  • Anything in /System or /private/var. macOS manages these, and they're protected for good reason.

  • Swap and sleep image files. macOS recreates them immediately.

  • Keychains, Mail and Messages data, even if they look big.

If a guide tells you to run sudo rm -rf on system folders to shrink System Data, don't. The space you save isn't worth a broken install.

Why System Data grows back

Much of System Data is supposed to be temporary. Caches refill as you use apps, and snapshots come back until your Time Machine drive is connected again. That's fine. The goal isn't to get System Data to zero. It's to remove the big, stale items you don't need: old device backups, abandoned simulators, forgotten VMs.

The short version

System Data is mostly caches, snapshots, backups and developer files. Let macOS handle the purgeable part, remove old device backups and developer leftovers, and never delete protected system folders.

Clearbay explains these locations in plain words, labels each item Safe, Review or Caution, and lets you offload big items to a drive instead of deleting them. Coming soon to the Mac App Store.