The short version
- System Data is a leftovers category: everything macOS cannot file under Apps, Photos, Documents and the like.
- The usual heavyweights are local Time Machine snapshots, large app caches, swap, and downloaded updates.
- It is normal for it to be tens of gigabytes. A big number is not automatically a problem.
- Shrink it by reclaiming snapshots and clearing caches you recognise, not by deleting files from system folders.
Why the category even exists
The Storage screen tries to sort your disk into friendly buckets: Applications, Photos, Music, Documents, macOS itself, and so on. But a great deal of what is on a working Mac does not fit any of those neat labels. Rather than show you a dozen obscure technical categories, macOS sweeps all of it into one: System Data (older versions called a similar bucket "Other"). It is defined by what it is not, which is exactly why it is so hard to reason about.
So the honest first answer to "what is System Data?" is: a mixture. The useful question is which ingredients tend to dominate, because a handful of them account for almost all of a large number.
The ingredients that make it big
Local Time Machine snapshots (often the biggest surprise)
If Time Machine is on, your Mac takes snapshots on its own internal disk, not only on the backup drive. A snapshot keeps the blocks of files as they were at a moment in time, which means files you have since deleted are still being held. This space lands squarely in System Data, and it is frequently the single largest contributor. It is also the one that makes people say "I deleted 40 GB and nothing happened."
We dedicated a whole article to this: The disk that won't empty: APFS snapshots and Time Machine, including the exact tmutil commands to see and reclaim it.
Application caches
Apps keep caches under ~/Library/Caches and in their own support folders, and macOS files these under System Data. On an ordinary Mac these are modest. On a developer's or a creative's Mac they are enormous: Xcode's DerivedData, a video editor's media cache, Docker's disk image, browser caches, package manager caches. Any one of these can be tens of gigabytes, and together they often explain most of a startling System Data figure.
Swap and virtual memory
When RAM fills, macOS moves less-active memory to disk as swap. This is normal and healthy, not a sign of a problem, but the files live on disk and count toward System Data.
Downloaded updates, logs and support files
Staged macOS and app updates, system logs, and assorted support files all land here too. The good news is that this group is largely self-managing: macOS removes staged updates after installing, and log management is handled by the system.
The measurement wrinkle that makes it worse
Part of why System Data looks alarming is that the Finder is not always honest about it. Howard Oakley, who has tested macOS storage reporting extensively, found the Finder is inconsistent about whether it counts snapshot space as purgeable, "following no obvious rule," and documented it once overstating available space by more than 80 GB. Because the Storage bar is built from these same estimates, System Data can appear inflated simply due to how the space is being counted, not because there is genuinely that much there.
A large System Data figure is often not a real problem. Check the true free space with Disk Utility or df -h / in Terminal rather than trusting the Storage bar, and only act if you genuinely need the space.
How to shrink it, safely
You cannot click into System Data, so the trick is to target its ingredients directly rather than the category.
- Reclaim local snapshots. List them with
tmutil listlocalsnapshots /and reclaim space withtmutil thinlocalsnapshots / 10000000000 4. This is usually the biggest single win. - Clear large app caches you recognise. Xcode DerivedData, a video editor's media cache, Docker's unused images and build cache. Each has a proper way to clear it; we cover the big ones in their own guides.
- Let macOS manage the rest. Staged updates, logs and the caches the system owns will be purged automatically when space is needed. These are not yours to hand-delete.
- Restart if a number looks stuck. Freed snapshot space sometimes only appears after a reboot.
Do not go spelunking in /System, /Library or /private/var to delete files and shrink the number. Much of what is there is required, and some of it macOS actively manages. Deleting system logs in particular breaks diagnostics that Time Machine and security scanning rely on. Target snapshots and recognisable app caches; leave the system's own files to the system.
The bottom line
System Data is not a mystery malfunction. It is a leftovers bucket, and on a Mac you actually use, it is normal for it to hold tens of gigabytes of snapshots, caches, swap and support files. The way to deal with it is not to attack the grey bar but to understand its ingredients, reclaim the two or three that are genuinely large and genuinely yours to remove, and let macOS handle the rest.
See inside System Data
StorageSage breaks the grey bar into its real parts, snapshots, specific app caches, large files, and labels each by whether it is safe to remove and what it costs to get back. It counts your disk correctly and shows the honest free-space number.
Download for macOSSources
- Apple — Mac User Guide on storage categories and optimizing storage (macOS clears safe caches and logs; staged updates and system support files).
- Howard Oakley, The Eclectic Light Company — on purgeable space, the Finder's inconsistent snapshot accounting, and inaccurate free-space figures.
- Apple on-device manual pages:
man tmutil,man df.