What is System Data on a Mac, and why is it 200 GB?

System Data is not a category. It is the leftovers bin in Apple's storage chart, holding everything macOS could not confidently label as something else. That is why it is enormous, and why no single action shrinks it.

Open the Apple menu, then System Settings, then General, then Storage. There is a coloured bar, and a large grey segment called System Data. On a lot of Macs it is the biggest thing on the disk, sometimes 100 to 300 GB, and Apple offers you no way to open it and look inside.

People assume it is a bug, or that something has gone wrong. It is neither. It is a naming problem.

Why it is so big

macOS sorts your disk into categories it recognises: Applications, Documents, Photos, Music, Mail, iCloud Drive. Anything that does not fit one of those definitions gets put in System Data. That includes a lot of things that are completely normal and a few that are genuinely reclaimable.

In rough order of how much space they usually account for:

• Local Time Machine snapshots. Usually the single biggest contributor. Even without a backup drive attached, macOS keeps hourly snapshots on the internal disk. It deletes them when it needs the space, which is why your free space can look wrong and then quietly correct itself.
• Caches. Every application you have ever opened, plus system level caches. Browsers alone can hold several gigabytes.
• iOS and iPadOS backups. If you have ever backed up a phone to this Mac, each backup is the size of that phone's used storage, and old ones are not removed automatically.
• Swap and sleep image. Virtual memory written to disk, plus a file the size of your RAM for hibernation.
• Mail downloads. Attachments Mail has fetched, which is separate from the Mail category itself.
• Developer files. If you use Xcode, DerivedData, simulators and device support commonly run to tens of gigabytes.
• Fonts, plugins, logs, extensions and everything else that is not a document.

None of that is a fault. It is just unlabelled.

The snapshot thing, specifically

This is the one that confuses people most, so it is worth understanding properly.

macOS takes APFS snapshots of your disk roughly hourly, whether or not you own a backup drive. A snapshot is not a copy. It is a record of the state of the filesystem at a moment, and it keeps alive any file that has since been deleted or changed. So when you delete 30 GB of video, your free space may not move, because a snapshot is still referencing those blocks.

macOS removes snapshots automatically when it needs room, and it keeps them at most 24 hours. So in most cases the correct response is to wait, not to intervene. If you genuinely need the space back immediately, you can list and delete them with tmutil, but understand what you are giving up: the ability to roll back to an earlier state if something goes wrong.

What is safe to clear

In the order I would actually do it:

1. Old iOS backups. Often tens of gigabytes for a phone you no longer own. Finder, then your device, then Manage Backups. Check the dates before deleting.
2. Downloads. Not System Data strictly, but it is where the installer disk images accumulate, and it is the safest large win on most machines.
3. Browser caches. Safe. Sites reload slowly once, then it comes back.
4. Application caches in ~/Library/Caches, for apps that are not running. This regenerates.
5. Xcode DerivedData, if you are a developer and Xcode is not building.

What is not worth touching

• The sleep image. Yes it is the size of your RAM. Removing it breaks hibernation and it comes straight back.
• Swap. Managed by macOS. If swap is large, the answer is closing applications, not deleting files.
• /System and /Library at the root level. This is the operating system. It is also read only on modern macOS, which is a good thing.
• Anything inside a Photos, Final Cut or Lightroom library. These look like folders and behave like databases.

The part nobody mentions

A Mac needs headroom. Once you go past roughly 90 percent full, macOS has less room to manage swap and snapshots, and the whole machine starts feeling slow in ways that have nothing to do with the app you are using. If System Data is large but you still have 20 percent free, there is nothing to fix. If you are at 96 percent full, the number to care about is free space, not which category is biggest.

That reframes the question usefully. The goal is not to shrink System Data. The goal is to have enough free disk, and System Data is simply where most of the recoverable space happens to be filed.

If the number looks wrong

Storage figures in System Settings are cached and frequently stale, especially just after deleting something large. Snapshots, as above, mean deletions often do not free space immediately. Before concluding anything is wrong, restart, wait a few hours, and look again. A surprising proportion of "System Data is eating my disk" ends there.

Keep reading

• What is safe to delete on a Mac, and what absolutely is not: which caches genuinely rebuild themselves.
• Why is my Mac slow all of a sudden?: a full disk is one of the four usual causes.