Disclosure: this article links to CleanMyMac, a commercial product developed by MacPaw. We may earn a commission from purchases made through those links. CleanMyMac is Apple-notarized and distributed through the MacPaw Store, Setapp, and the Mac App Store. Every method described here also works manually at no cost, and the manual method is shown first in every case.
Key takeaways:
- System Data is a leftover category, not a folder. It holds everything macOS could not sort into a named category.
- Because it is defined by exclusion, its size tells you nothing by itself — two Macs at 100 GB can have entirely different causes.
- Large figures usually trace to one or two specific sources, not to gradual accumulation: snapshots, disk images, build artifacts, old device backups.
- You cannot delete System Data. You reduce specific things counted inside it, and safety varies enormously between them.
- The number lags reality by up to an hour, so judging a cleanup immediately is the most common self-inflicted confusion.
- A stable figure is fine at any size. A steadily climbing one is the actual warning sign.
What System Data actually is
System Data is a reporting category in the macOS storage breakdown, not a directory you can navigate to. When macOS builds that breakdown, it sorts what it can into named buckets — Applications, Documents, Photos, Mail, Music, Messages — and everything it cannot confidently classify falls into the remainder. That remainder is System Data.
This matters more than it first appears. The category is defined by exclusion, which means its contents are heterogeneous by design. Caches sit next to swap files, which sit next to disk images, which sit next to fonts and plugins and log files. Nothing about being counted as System Data implies a file is systemic, protected, or important.
The practical consequence: the size of System Data carries almost no diagnostic information on its own. Two machines showing an identical 100 GB can be in completely different situations — one holding months of local snapshots, the other holding a single oversized virtualization image. Any advice that tells you to reduce System Data without first establishing what is inside yours is guesswork.
What ends up inside it
The category is a catch-all, but in practice a limited set of things account for most of its volume.
| Contents | Typical location | Shrinks on its own? | Safe to reduce? |
|---|---|---|---|
| Local Time Machine snapshots | Managed by tmutil; not visible in Finder |
Yes, eventually | Yes, at the cost of restore points |
| User and app caches | ~/Library/Caches |
No | Yes — apps rebuild them |
| Virtual memory swap | Managed by the system | Yes, on restart | No — leave it alone |
| Application support files | ~/Library/Application Support |
No | Only for apps you have removed |
| Log files | ~/Library/Logs, system log stores |
Partially, via rotation | User logs yes; system logs leave alone |
| Disk images and VM containers | App-specific | No | Only through the owning app |
| Developer build artifacts | ~/Library/Developer/Xcode/DerivedData |
No | Yes — regenerates on next build |
| Old iOS device backups | ~/Library/Application Support/MobileSync/Backup/ |
No | Yes, if the device is gone |
| Spotlight index | Hidden index stores per volume | No | Only via a supported rebuild |
| Fonts and plugins | ~/Library/Fonts, various plugin folders |
No | Rarely worth touching |
Two rows deserve emphasis because they cause the most confusion. Swap appears in System Data and looks like waste, but it is the system doing its job under memory pressure; deleting it is neither possible nor desirable, and it clears on restart. Disk images almost never shrink when you delete their contents — freeing space inside a virtual disk leaves the image file on your real volume exactly as large as before, and reclamation has to be triggered through the application that owns it.
Why it reaches 100GB
A System Data figure in the hundred-gigabyte range is rarely the result of slow accumulation across many categories. In most cases one or two sources dominate, and identifying which is the entire job.
Local snapshots on a machine with an absent backup drive
When a Time Machine destination has not been seen for a long time, macOS keeps local snapshots on the internal volume rather than discarding them. On a machine whose backup drive lives in a drawer, these can accumulate over weeks. This is the single most common cause of a large, mysterious System Data figure.
Virtualization and container images
Disk images used by virtual machines and container tooling grow as they are written to and do not shrink when data inside them is deleted. A developer who has been building and discarding container images for months may be carrying a very large file that appears nowhere obvious in Finder.
Developer build artifacts
Build output directories accumulate across projects and branches. They regenerate on the next build, which makes them safe to clear, but nothing removes them automatically.
Old device backups
Backups made through Finder persist indefinitely, including backups of devices you no longer own. Each one can be substantial, and there is no prompt suggesting you review them.
A corrupted Spotlight index
Uncommon, but it happens, and when it does the effect can be dramatic. An index that has failed in a loop can consume space far beyond anything reasonable for the volume it describes. This is worth suspecting only after the more common causes have been ruled out.
How to find out what is actually in yours
Before reducing anything, establish which of the above applies. These commands read only.
Start with real free space, unmediated by the storage breakdown’s arithmetic:
df -h /System/Volumes/DataThen check whether snapshots are involved:
tmutil listlocalsnapshots /
tmutil listlocalsnapshotdates /A long list with dates stretching back weeks confirms the most common cause outright. An empty list rules it out and moves you down the list.
Then find the large directories:
du -sh ~/Library/* 2>/dev/null | sort -rh | head -20sudo and traverses the entire data volume, which can take several minutes. It reads only and deletes nothing, but back up before acting on what it shows.
sudo du -xh -d 2 /System/Volumes/Data 2>/dev/null | sort -rh | head -30Run it twice a few minutes apart and compare. A directory that changes size between runs is being actively written to, which is a different problem from one that is merely large.
If working through directory listings is not how you want to spend an afternoon, a Mac storage optimizer will map the same territory visually in one scan. The commands above cost nothing and tell you the same thing, so run them at least once — knowing where your space goes is worth more than any single cleanup.
Reducing it safely
Order matters. Work from lowest risk upward and stop when the number is reasonable.
- Empty Trash and restart. This clears swap and releases anything held only by a Trash reference. Costs nothing, risks nothing, and resolves a surprising share of cases.
- Reconnect the Time Machine drive. If snapshots are the cause, letting a real backup complete lets macOS thin them normally. Safer than manual deletion, and it restores your backup coverage at the same time.
- Clear user caches selectively. Work through
~/Library/Cachessubfolder by subfolder rather than emptying it wholesale, so you can confirm nothing breaks as you go. - Remove old device backups. Review these through Finder’s own backup management rather than deleting the directory directly.
- Clear build artifacts. Build output regenerates; this is among the safest large reclamations available on a developer machine.
- Reclaim disk images through their owning application. Never delete a VM or container image directly unless you are certain you no longer need what is inside it.
The step-by-step procedure for each of these, with the exact paths and the order that reclaims the most space fastest, is covered in the companion cleanup guide rather than repeated at length here.
App leftovers deserve a note of their own, because they are counted in System Data and are invisible in Finder. Removing an application leaves its support files, preferences, caches, and logs behind in four separate locations, and the residue accumulates for years across apps you no longer remember installing. Hunting four folders per application manually is tedious rather than hard, which is where CleanMyMac app genuinely saves time: an uninstaller module catches all four in one pass. It is developed by MacPaw and Apple-notarized, which is worth verifying in a category that has historically attracted scareware.
Why the number refuses to drop
You cleaned up, and System Data is unchanged. Three explanations cover nearly every instance.
The pane has not caught up. The storage breakdown recalculates on a delay, and Spotlight often needs to reindex changed folders first. Give it a full hour before concluding anything. Judging a cleanup thirty seconds after finishing it is the most common self-inflicted confusion in this entire topic.
A snapshot still holds the blocks. If a local snapshot predates your deletion, it references those file blocks so the backup remains restorable. The space returns when the snapshot ages out or is removed, not when you press delete.
It regenerated. Sync clients re-download libraries. Logs fill again. Build systems rebuild. If the figure returns within minutes rather than days, something is actively writing, and the repeated du comparison above identifies it.
Deleting snapshots by hand
Listed last deliberately — reconnecting the backup drive is better whenever it is possible.
tmutil listlocalsnapshotdates /
sudo tmutil deletelocalsnapshots [date-from-the-output-above]sudo and permanently removes a restore point. Only delete snapshots whose dates you have confirmed in the listing output, and never remove your most recent snapshot unless a current backup exists elsewhere.
What this won’t fix
Reducing System Data addresses caches, snapshots, backups, artifacts, and leftovers. It does not shrink your Photos library, your Documents, or applications you actively use — none of which are counted in System Data anyway. If the figure stays high after everything above, the remaining candidates are narrow: a corrupted Spotlight index needing a rebuild, a log in a failure loop, a snapshot that will not release, or a disk image whose owning application must reclaim it.
It also will not help if the volume is simply too small for the workload. A machine that fills again every few weeks despite a clean System Data figure is telling you something about its capacity, not its hygiene, and the answer is external or cloud storage rather than another cleanup.
Whether you use CleanMyMac app for system cleaning or its malware scanner, both make maintaining your Mac effortless. If you haven’t tried CleanMyMac yet, it’s one of the most effective tools for macOS.
Frequently asked questions
What is System Data on a Mac?
It is a leftover reporting category, not a folder. macOS sorts storage into named categories and puts everything it cannot classify into this one. In practice that means caches, logs, local snapshots, swap, application support files, disk images, plugins, and fonts sitting together. Because the category is defined by exclusion rather than by content, its size alone tells you very little, and two Macs showing the same figure can have entirely different underlying causes.
Why is my System Data 100GB or more?
Figures that large usually trace to one or two dominant sources rather than gradual accumulation. The most common are local Time Machine snapshots on a machine whose backup drive is rarely connected, virtualization or container disk images that grow without shrinking, developer build artifacts, and old iOS device backups. A corrupted Spotlight index can also inflate it dramatically. The number itself does not identify which applies, which is why diagnosis matters more than cleanup here.
Is it safe to delete System Data on a Mac?
You cannot delete it directly, because it is a category rather than a location. You reduce specific things counted within it, and safety varies enormously. User caches and build artifacts are safe and regenerate automatically. Snapshots can go but cost restore points. Swap and anything on the protected system volume should be left alone entirely — System Integrity Protection blocks the latter regardless. Never delete files simply because they are counted as System Data.
Why does System Data not go down after I clean up?
Usually the pane has not recalculated yet — it lags by up to an hour and often waits for Spotlight to reindex. Failing that, a local snapshot predating your deletion may still hold the blocks, so the space cannot be released. The third possibility is that the data regenerated immediately, which is common with sync clients and virtualization images. Wait a full hour before assuming the deletion failed.
What is a normal System Data size?
Apple publishes no official figure, and any specific number quoted elsewhere is an observation rather than a standard. The trend on your own machine is more informative than the absolute value. A figure that stays roughly stable month to month is behaving normally whatever its size. One climbing steadily without a corresponding change in how you use the Mac indicates accumulation worth investigating, even if the current number looks unremarkable.
Does System Data include my iCloud files?
Locally cached iCloud content is generally attributed to its own categories, such as Documents or Photos, rather than to System Data. The sync machinery around it does contribute, though — cache directories, transfer staging areas, and partially downloaded files all land in the catch-all. A sharp rise right after enabling a large iCloud library points at the sync process, and the figure usually settles once initial synchronization finishes.