System Data on Mac: what is in it, why it is huge, and how to clear it safely

What is System Data on a Mac, exactly?

Open System Settings, General, Storage, and the colored bar shows categories: Applications, Photos, Documents, Messages, iCloud Drive, macOS, and a grey one called System Data. The named ones are things macOS can attribute to a specific app or kind of file. System Data is the rest. It is not "the system": macOS itself has its own category, usually around 10 to 15 GB and sealed so you cannot touch it. System Data is the catch-all for everything else on the disk that is not a photo, a document or an app bundle.

That catch-all is big because modern Macs keep a lot of state outside the obvious folders. Every app keeps caches and support files in your Library folder. Mail downloads every attachment. Messages keeps every photo anyone ever sent you. If you ever backed up an iPhone to this Mac, the whole backup is there. If you have installed Xcode, there are simulators for every iOS version you have ever run. If you use Docker, its virtual disk can be 60 GB on its own. And underneath all of that, the file system itself keeps hourly snapshots of your disk whenever Time Machine is on, so that you can go back in time even when the backup drive is not plugged in.

Apple's own support page says that System Data "includes files that aren't in one of the other categories" and that the size can vary. That is accurate and not very helpful, which is why this page exists.

Why do I have 100 GB (or more) of System Data on my Mac?

Because several things in it are large and none of them are labeled. Here is what a typical 150 GB of System Data breaks down into on a Mac that has been in use for a couple of years, with Time Machine on and a few developer tools installed. Your numbers will differ, but the shape is usually the same.

Two things make this worse than it looks. First, the Storage chart in System Settings can lag the real state of the disk by hours, and it counts purgeable space (snapshots macOS is willing to delete) as used. Howard Oakley at Eclectic Light documented a Mac where Disk Utility showed 94 GB purgeable, the Finder showed almost none, and a 10 GB copy failed even though Storage listed 100 GB available. His verdict was that "macOS space management needs to be rethought, redesigned, implemented without inconsistencies or bugs, and thoroughly documented." Second, the number moves on its own. One Apple Community poster noted that "The System Data storage amount changes a-lot seemingly due to no reason". It does have a reason: snapshots being created and thinned in the background. But you cannot see that from the chart. The purgeable space page covers the chart's quirks in detail.

Time Machine local snapshots: the usual 50 to 400 GB culprit

When Time Machine is turned on, macOS takes a snapshot of your startup disk roughly every hour and keeps about 24 hours' worth locally, even when the backup drive is not connected. A snapshot does not copy files. It freezes the state of the disk, so any file you later change or delete still exists in the snapshot until the snapshot is removed. That is why System Data can jump by tens of gigabytes right after you delete a large video project: the files are gone from Finder, but a snapshot still holds them.

The size this reaches on real Macs is remarkable. An Apple Community poster running Sequoia found "a snapshot was occupying 416GB of disk space when it should not have been", after reporting they "still have 492GB of system data and I can't get rid of it." Another, on an M1 Air, reported that "system data is taking up over 125 GBs of my 250 GB mac". Howard Oakley's advice on snapshots is blunt: "Snapshots will only grow in size over time. Don't leave them lying around."

The good news is that macOS manages these itself. When free space drops low, it thins old snapshots first. A restart and a day of normal use is often enough for System Data to fall by half with no action on your part. You can see what snapshots exist by opening Terminal and running tmutil listlocalsnapshots /, which only lists them and changes nothing. If you want them gone faster, the supported route is to let Time Machine complete a backup to its drive, which prunes local snapshots, or to turn Time Machine off and on again in System Settings. The local snapshots page explains the lifecycle and the trade-offs.

How to clear System Data on a Mac, in the safe order

Work from the outside in. The first few steps are things macOS does for you if you let it; the later ones are specific, labeled files you can delete without guessing. Stop when you have the space you need.

1. Restart, then wait a day

   A restart clears swap, temporary files and logs, and gives macOS a chance to thin local snapshots. Check Storage again the next day before doing anything else. On many Macs this alone recovers 20 to 50 GB.

2. Run the Storage recommendations

   System Settings, General, Storage. Use Empty Trash Automatically, Optimize Storage (removes watched TV and films you can redownload) and Store in iCloud if you use it. These are Apple's own tools and they remove only things that can be regained.

3. List your local snapshots (listing only)

   Open Terminal and run tmutil listlocalsnapshots /. This shows what exists and how old it is, nothing more. If there are many hours of snapshots and your backup drive has not been connected for a while, connect it and let a backup run; that prunes them. Do not run deletion commands with sudo from forum posts.

4. Delete old iOS backups from Finder

   Connect any iPhone or iPad, select it in the Finder sidebar, click Manage Backups, and delete backups of devices you no longer own or backups older than the latest. Each one can be 5 to 50 GB. Keep the newest backup of each device you still use.

5. Uninstall big apps properly

   System Settings, General, Storage, Applications, sorted by size. Drag unused apps to the Trash from the Applications folder, and if the app has its own uninstaller (Adobe, Microsoft, Docker), use that so its support files go too. Games, old creative suites and VMs are the usual tens-of-gigabytes finds.

6. Empty Trash and clear Downloads

   Files in the Trash still count against the disk. Downloads collects installers and archives that you opened once. Sort by size and delete; both are safe by definition.

7. Mail and Messages attachments, from inside the apps

   Mail: Settings, Accounts, Download Attachments set to Recent or None removes the local copies; they stay on the server. Messages: System Settings, General, Storage, Messages lists large attachments you can review and remove. Do not delete these folders in Library directly.

8. Developers: Xcode DerivedData, simulators and Docker

   In Xcode, Settings, Locations, click the arrow next to DerivedData and trash its contents; it is rebuilt on the next build. Xcode, Settings, Components (or Platforms) lets you remove simulator runtimes for iOS versions you no longer target. In Docker Desktop, Settings, Resources lets you shrink the disk image, and Troubleshoot, Clean / Purge data removes unused images. These three together are often 30 to 100 GB.

What is safe to remove, and what grows back

Here is the honest split. Safe and permanent: old iOS backups, apps you no longer use, Trash, Downloads, simulator runtimes you do not need, Docker images you do not need, downloaded TV and films, attachments that still exist on the server. Delete these and the space stays freed.

Safe but regrows: app caches, browser caches, Xcode DerivedData, logs, swap. You can clear these and your Mac will be fine, but they come back within days because they exist to make apps fast. Clearing them to "gain space" is a treadmill, and the should I clear cache page explains why it rarely helps performance either.

Managed by macOS, leave it: local snapshots (let Time Machine and free-space pressure thin them), the sealed macOS system volume, the swap file, purgeable space. These look like targets but macOS reclaims them on its own when it needs to, and forcing them tends to cause the next problem.

Not safe: anything in ~/Library or /Library that you cannot name. Containers hold app data (your notes, your chat history, your game saves). Application Support holds licenses and settings. Mail and Messages folders hold the only local copy of years of correspondence. One Apple Developer Forums poster who had checked found "I checked Library, but that only takes up 16 GB", which is a useful data point: Library is often not where the bulk is anyway. The Apple Community thread about the 416 GB snapshot also noted a quieter leak, "creating a new mediaanalysisd cache file of 64MB probably every hour or so", which is the sort of thing macOS cleans up itself and you would never find by hand.

See what is likely in your System Data

Enter your disk size and what you use the Mac for, and this estimates how the System Data is probably split and which of the steps above will matter most for you.

The estimate is only as good as the categories, so treat it as a map, not a measurement. The one thing it reliably shows is which bucket to open first: snapshots on a Mac with Time Machine on, developer tools on a Mac with Xcode or Docker, and iOS backups on a Mac that has ever been plugged into an iPhone.

Why you should not delete ~/Library blindly (and why cleaners do)

Nearly every "clear System Data" article, and the AI summary at the top of the search results, tells you to open ~/Library/Caches and ~/Library/Logs and delete what you find. Caches and Logs are the two folders where that is mostly harmless, and also where it mostly does not help: on a typical Mac they are a few gigabytes between them, and they are back in a week. The trouble is that the same articles go on to Containers, Application Support, Group Containers and Mail, where deleting the wrong folder removes an app's data, breaks a license, or wipes local mail. The folder names are not self-explanatory. com.apple.MobileSync is iOS backups (fine to manage via Finder). com.apple.mail is your mailboxes (not fine).

Cleaner apps automate the same guesswork. They are good at finding caches and logs, which do not matter, and bad at knowing which container holds data you care about. A MacRumors poster who tested one found "it proposed to delete stuff that clearly shouldn't be deleted", and that matches what Apple Community volunteers have said for years. MacOS Sequoia, as another poster put it, "seems to have many hiding places and is somewhat of a hoarder." True. But the hoard is mostly snapshots and backups, which have proper, labeled ways to remove them, and the rest is small enough that a cleaner's hour of risk buys you a few gigabytes.

If you want a general guide to freeing space that covers Photos, Documents and the rest alongside System Data, the free up space on Mac page is the broader version of this one.

When System Data is actually a problem

Most of the time it is not. 40 GB of System Data on a 512 GB Mac is normal and nothing needs doing. The cases that deserve action are: free space under 10 to 15 percent, where the Mac itself slows down (see why is my Mac so slow); System Data that keeps growing by tens of gigabytes a day, which points at a runaway log, a sync client in a loop or a snapshot that cannot thin because a backup never completes; and a 256 GB Mac where System Data has passed 100 GB, which is the "over 125 GBs of my 250 GB mac" case and is nearly always snapshots plus one big developer or creative tool.

In the growing-daily case, Activity Monitor's Disk tab, sorted by Bytes Written, names the process doing the writing. If it is a sync client (iCloud, Dropbox, Google Drive, OneDrive), pause it and see if the growth stops. If it is a backup agent, check that its destination is reachable. If it is mds_stores, Spotlight is rebuilding and the space is temporary. A reinstall of macOS does not fix any of these, because the data is in your user folder and comes back with it.