Topic clusters
Why is System Data so large on a Mac?
System Data is a catch-all, not a folder. It holds caches, logs, local snapshots, swap and a lot of developer data. This guide shows how to find your largest pieces and how to reduce System Data safely.
Open System Settings > General > Storage and the bar may show a huge grey System Data block. It is not one folder you can open. macOS puts anything it cannot attribute to Apps, Documents, Photos or another named category into System Data: app caches and logs, local Time Machine snapshots, swap and sleep files, app support data, and, on a developer Mac, a lot of build output and virtual disk images.
That makes the number hard to act on, but the large pieces are usually few. This guide finds them with read-only commands, then separates what macOS manages for you, what is safe to remove, and what to leave alone.
Older versions of macOS called most of this "Other" storage. If you are looking for what is in Other on a Mac, it is the same catch-all with a new name, and the same steps apply.
Step 1: Check how much room you really have
Storage settings includes purgeable space, which macOS can reclaim when it needs to. The free-space figure from df is the plain number. If you have tens of gigabytes free, a large System Data is not an emergency.
df -h /Read the Avail column. On a nearly full disk, macOS also has no room to grow swap, which makes the Mac slow and can bring on the out-of-memory Force Quit window sooner.
Step 2: Find the biggest folders in your Library
Most of the pieces you can safely act on live in your own Library folder. This lists its largest subfolders. Some entries under Caches are protected and print a permission message; ignore those.
du -d 1 -h ~/Library 2>/dev/null | sort -rh | head -10du -d 1 -h ~/Library/Application\ Support 2>/dev/null | sort -rh | head -10Step 3: Know what each big piece is
These are the usual large items and what to do about each.
- Local Time Machine snapshots. macOS keeps these on the startup disk and removes them on its own, usually within a day or sooner when space is needed. List them with
tmutil listlocalsnapshots /. Leave them alone unless you are certain you do not need them. - App caches (
~/Library/Caches). They rebuild themselves. Quit the app before clearing its cache. Clear only folders you recognise. - Xcode DerivedData and simulators (
~/Library/Developer). Safe to remove and rebuilt on demand. See how to clear DerivedData safely. - Docker Desktop's disk image (
~/Library/Containers/com.docker.docker). One file,Docker.raw, holds every image and volume. It looks bigger in Finder than it is, because it is a sparse file. Usedocker system dfto see what is reclaimable. - iOS device backups (
~/Library/Application Support/MobileSync/Backup). Often tens of gigabytes. Delete old ones through Finder (select your device, then Manage Backups), not by removing folders by hand. - Swap and sleep image (
/private/var/vm). Managed by macOS. Do not touch them. Large swap means memory pressure, which is a memory problem, not a disk-cleaning one.
tmutil listlocalsnapshots /Listing is read-only and harmless. Each line is one snapshot named for the time it was taken.
How to reduce System Data, in order
You cannot clear System Data in one go, because it is not one thing. Work down this list and stop when you have the room you need.
- Empty the Trash and restart. A restart clears temporary files and lets macOS remove snapshots and caches it no longer needs.
- Remove developer data that rebuilds itself. Xcode DerivedData, old simulators, and package caches are usually the largest pieces on a developer Mac.
- Prune Docker.
docker system dfshows what is reclaimable, anddocker system pruneremoves stopped containers and unused images. - Delete old device backups through Finder, not by removing folders by hand.
- Clear the cache of one app at a time, with the app closed, and only for apps you recognise.
- Wait a day. Local snapshots expire on their own, and Storage settings is slow to recount. The number often drops without you doing anything else.
What not to delete
Do not delete anything inside /System, /private/var or /Library unless you know exactly what it is. Do not remove folders from ~/Library/Application Support for an app you still use, because that is where its data lives. If you are not sure what a folder is, search its name before touching it, or leave it.
When to let an app do it
Disk Housekeeper gathers the developer part of System Data, such as Xcode DerivedData, npm, Gradle and Cargo caches and node_modules, into one preview, and sends removals to the Trash by default. It does not describe or delete APFS snapshots. Scanning, previews and your first 2 GB of cleaning are free.
Questions
What is System Data on a Mac?
A catch-all category in Storage settings for everything macOS cannot file under Apps, Documents, Photos or another named group: caches, logs, local snapshots, swap, app support data and developer files.
Why is my Mac System Data so large?
Usually a few big pieces: app caches, local Time Machine snapshots, Xcode DerivedData and simulators, Docker's disk image and iOS backups. Use du -d 1 -h ~/Library | sort -rh | head to see which are biggest on your Mac.
Can I delete System Data?
Not as a whole. It is made of many unrelated things. Remove the specific pieces you recognise and that rebuild themselves, such as DerivedData and app caches, and leave macOS-managed items like swap and snapshots alone.
Do Time Machine local snapshots fill System Data?
They can. macOS removes them on its own, usually within a day, or sooner when it needs the space. You can list them with tmutil listlocalsnapshots /.
Why does System Data not shrink after I delete files?
Files go to the Trash first and still count until you empty it. Storage settings also takes a while to recalculate, and purgeable space can be counted in the bar without being freed.
How do I reduce System Data on a Mac?
Empty the Trash and restart, then remove the large pieces that rebuild themselves: Xcode DerivedData, old simulators, package caches and unused Docker images. Delete old device backups through Finder. Leave swap and local snapshots to macOS.
Is System Data the same as Other storage?
Yes, for practical purposes. Before macOS 12 Monterey, the Storage bar called this catch-all "Other". Newer versions call it System Data. Both mean files macOS does not list under a named category.
How do I get rid of Other storage on a MacBook?
The same way as System Data: find the largest folders in your Library, remove the ones that are safe to rebuild, and let macOS manage the rest. There is no single Other folder to delete.
Why does System Data keep increasing?
Caches, logs and build output grow as you use the Mac, and local snapshots are added between backups. On a developer Mac, each build, simulator and container image adds more. It grows until something removes it.