What System Data actually is
Open System Settings > General > Storage and you’ll see a colored bar split into categories. Apple describes System Data as a general category for Apple and third-party files that don’t fit a more specific one. In practice that means caches, logs, temporary files, virtual memory files, fonts, app support files, plug-ins and local snapshots. Before macOS Monterey the same bar was called “Other”.
Two things are worth knowing before you start hunting:
- It isn’t a folder. System Data is spread across
~/Library,/Library,/private/varand APFS snapshots. There’s nothing called System Data you can open or empty. - It’s an estimate. Storage settings works out the other categories first and lumps what’s left into System Data. Files it fails to recognise (for example music it doesn’t count as Music) end up there too. That’s why the number can jump after a macOS update or a reindex even though you didn’t change anything.
So the goal isn’t to make System Data zero. It’s to find the few big, specific things inside it that you don’t need.
The usual suspects
On most Macs, a large System Data figure comes down to a handful of causes. Here they are roughly in order of how often they’re the culprit.
1. Local Time Machine snapshots
If Time Machine is on, macOS saves a snapshot of your startup disk about every hour and keeps it for around 24 hours, plus one for the last successful backup and one before each macOS update. A snapshot holds on to files you’ve since deleted or changed, so deleting a big file doesn’t free the space until the snapshot that contains it goes away. Apple counts snapshot space as available, but it often shows up inside System Data anyway. Our guide to deleting Time Machine local snapshots covers this in detail.
2. iPhone and iPad backups
If you back up a device to your Mac instead of iCloud, each backup lives in ~/Library/Application Support/MobileSync/Backup. A single backup can be many gigabytes, and old ones for phones you sold years ago often stick around.
3. Developer tools
Xcode’s DerivedData, old simulators and device support files, Docker Desktop’s disk image, and package caches from npm, Homebrew, pip and others can add up to tens of gigabytes. Some of this shows in the Developer category, but plenty lands in System Data. See freeing up space from Xcode, shrinking Docker.raw and deleting node_modules.
4. Caches and logs
Apps cache aggressively in ~/Library/Caches. Browsers, music and video apps, design tools and chat apps are the usual heavy users. macOS clears some caches itself when space runs low, so this is rarely the whole story, but one runaway app cache can be several gigabytes. See how to clear cache on a Mac safely.
5. App data in Application Support and Containers
Apps keep their working data in ~/Library/Application Support, ~/Library/Containers and ~/Library/Group Containers. Offline video downloads, chat histories, virtual machines and game assets often live here, and they stay behind after you delete the app.
6. Swap and temporary files
When memory runs short, macOS writes swap files to a separate VM volume (you can see them in /System/Volumes/VM). They come and go with memory pressure and are cleared on restart. Don’t delete them by hand.
Step by step: shrink System Data with built-in tools
You don’t need any app for this. Work through these in order and check Storage settings after each one.
Step 1: Restart
It sounds too simple, but a restart clears swap and temporary files and gives macOS a chance to finish removing expired snapshots and leftover update files. Check Storage settings again afterwards, and give it a minute to recalculate.
Step 2: Read the other categories first
In System Settings > General > Storage, click the info button next to each category. Applications, Developer, Documents, Messages and iOS Files all have their own tools to review and delete items. Clearing big things there is easier than chasing them inside System Data.
Step 3: Check for local snapshots
This command lists local Time Machine snapshots. It only reads, it doesn’t change anything:
tmutil listlocalsnapshots /If you see a long list and your real backups are working, follow the snapshot guide to remove the old ones.
Step 4: Remove old device backups
Connect the iPhone or iPad, select it in the Finder sidebar, and on the General tab click Manage Backups. Select a backup you no longer need and delete it there. This is Apple’s supported route and it’s better than deleting folders inside MobileSync by hand, because the folder names are random strings.
Step 5: Find the biggest folders in your Library
In Finder, choose Go > Go to Folder, type ~/Library and press Return. Switch to list view, open View > Show View Options and turn on Calculate all sizes, then sort by Size. Folder sizes take a while to fill in.
Terminal is quicker. This shows the 20 largest folders in your Library, smallest first and biggest at the bottom. It only reads sizes:
du -hd 1 ~/Library 2>/dev/null | sort -h | tail -20Then go one level deeper into whatever is biggest, for example:
du -hd 1 ~/Library/Application\ Support 2>/dev/null | sort -h | tail -20If Terminal says “Operation not permitted” for some folders, it needs Full Disk Access (System Settings > Privacy & Security > Full Disk Access). You can turn it off again when you’re done.
Step 6: Delete only what you recognise
When you find something big, ask two questions. Do I know what app this belongs to? And can that app recreate it, or do I really not need it? If the answer to both is yes, quit the app and move the folder to the Trash. Keep the Trash for a few days before emptying it, so you can put things back if an app complains.
What never to delete
Many “clear System Data” tips online suggest deleting whole system folders. Don’t. These are the ones to leave alone:
/Systemand anything under it. It’s on a sealed, read-only volume anyway./private/var, including/private/var/foldersand/private/var/db. macOS manages these and cleans them up itself.- Swap and sleep image files. They’re recreated immediately, and removing them while in use can cause problems.
- Whole
~/Librarysubfolders like Application Support, Containers, Group Containers, Mail, Messages or Keychains. They hold your actual data and settings. Remove a single app’s folder inside them, never the parent. - Snapshots you don’t recognise. Only delete ones named
com.apple.TimeMachine. Other backup tools make their own.
And be wary of any guide that has you run sudo rm -rf on a system path. Moving things to the Trash is slower, but it’s reversible.
Why the numbers don’t add up
Storage settings, Finder and Disk Utility often show different free space. Storage settings and Finder count purgeable space (snapshots, some caches, iCloud files that can be downloaded again) as available, even though macOS only frees it when it decides to. For the most honest figure, open Disk Utility, choose View > Show All Devices, and look at the free space of the container that holds your Macintosh HD volumes. That’s also the number to watch while you clean up.
Doing it faster with a disk map
The manual route works, but it means a lot of du commands and guesswork about what each folder is. A disk map does the same job visually: scan once, see every folder sized by how much space it takes, and click into the big ones. freedisk.space also groups common System Data culprits into catalogs, so caches are listed by app and developer storage (DerivedData, simulators, node_modules, package caches) is listed by project. It doesn’t touch Time Machine snapshots, so use tmutil or Disk Utility for those.
Questions people ask
- What is System Data on a Mac?
- System Data is the catch-all category in Storage settings. Apple describes it as Apple and third-party files that do not fit a more specific category, such as caches, logs, temporary files, virtual memory files, local Time Machine snapshots and app support data.
- Is it safe to delete System Data?
- There is no System Data folder to delete, and you should never remove system folders by hand. You can safely shrink it by removing specific things inside it that you recognise, such as old local snapshots, old iPhone backups, app caches and developer build files.
- Why does System Data keep growing?
- Local Time Machine snapshots, caches, iPhone and iPad backups, and developer tools like Xcode and Docker all grow over time and often land in System Data. macOS also estimates the category, so the number can jump after an update or reindex even when nothing changed.
- Does restarting my Mac reduce System Data?
- Often a little, sometimes a lot. A restart clears swap files and temporary files and gives macOS a chance to finish removing expired snapshots, but it will not touch backups, caches or developer files.
- Why does System Data show a different size in Finder or Disk Utility?
- Storage settings, Finder and Disk Utility calculate space differently, and Storage settings only estimates System Data. Purgeable space, such as local snapshots, is also counted as available in some views and as used in others.