What is System Data on Mac (and how to actually clear it)

By Irshad PC · Published July 17, 2026

System Data is the storage category macOS uses for everything it can’t file under apps, photos, documents, or the operating system itself. Most of it is caches, logs, app support files, Time Machine local snapshots, and old iPhone backups. Much of it is safe to clear, and you can do the whole job by hand for free. This guide shows you how, folder by folder.

What counts as System Data

When macOS calculates storage, it sorts your files into named buckets: Applications, Photos, Documents, Music, and so on. Anything it can’t confidently place lands in System Data. That’s why the number feels so mysterious. It isn’t one thing. It’s the leftovers pile.

It’s also why the number keeps growing. Every app you run writes caches, logs, and support files. Build tools download dependencies. Time Machine quietly keeps hourly snapshots on your internal disk. None of this shows up in a normal Finder search, so it accumulates unseen for years.

What’s actually inside it

These are real folders on your Mac, and all of them count toward System Data:

Why macOS leaves most of it behind

To be fair, macOS does reclaim a little of this by itself. It clears temporary scratch files at restart, and it thins local snapshots when the disk gets genuinely full. That’s about it.

The rest stays put by design. A cache exists to save an app work later, and macOS has no way to know whether a given cache still earns its keep, so it leaves it alone. No app cleans up after another app, either. Xcode never deletes DerivedData for projects you abandoned in 2023, and npm’s cache still holds packages from installs you ran years ago. Junk your Mac can rebuild just sits there until something removes it.

Step 1: see what you’re dealing with

Open System Settings, then General, then Storage. Give it a minute, the categories calculate slowly. System Data is usually the light gray segment at the end of the bar. Apple’s own walkthrough of this screen is in their storage guide.

Don’t panic at the number. Some of it is healthy, and the goal is to remove the stale part, not to reach zero.

How to clear System Data by hand

Everything below is free and uses nothing but Finder and Terminal.

Clear app caches

In Finder, press Cmd+Shift+G and go to ~/Library/Caches. Sort by size, open the biggest folders, and delete their contents rather than the folders themselves. Quit an app before clearing its cache so it isn’t writing to the folder while you empty it. Apps rebuild what they need on the next launch.

Three folders in there deserve to be left alone: CloudKit, com.apple.HomeKit, and FamilyCircle. They hold sync state, which is disruptive to rebuild, not junk.

You can repeat the same process in /Library/Caches, though the sizes there are usually smaller.

Clear logs

Go to ~/Library/Logs and delete what’s inside. New logs are written as needed. This rarely frees much space, unless an app has been crashing in a loop and writing the same report for months.

Thin Time Machine local snapshots

When Time Machine is on, macOS keeps hourly snapshots on your internal disk so it can back up even when your backup drive isn’t connected. They can quietly hold a lot of space. List them in Terminal:

tmutil listlocalsnapshots /

Each line looks like com.apple.TimeMachine.2026-07-16-093515.local. Delete one by its date stamp:

tmutil deletelocalsnapshots 2026-07-16-093515

Your real backups on the backup drive are untouched. macOS simply creates a fresh snapshot at the next hourly cycle, so this only releases the space old ones were holding.

Remove old iPhone and iPad backups

Go to ~/Library/Application Support/MobileSync/Backup. Each folder is one device backup, and they’re often tens of gigabytes. A backup can’t be rebuilt like a cache can, so before you delete one, make sure the device backs up to iCloud or that you no longer need to restore it.

Clear developer leftovers

If you write software, this is usually the single biggest win. ~/Library/Developer/Xcode/DerivedData is rebuilt the next time you build. iOS DeviceSupport is re-extracted when you plug a device in. ~/.npm refills on the next install, and brew cleanup handles Homebrew’s download cache. The full list, including Gradle, CocoaPods, and node_modules, is in our developer junk guide.

What not to touch

• Anything inside /System. That’s the operating system.
• ~/Library/Application Support folders you don’t recognize. Plenty of apps keep your actual data there, not just caches.
• ~/Library/Keychains. Your saved passwords live here.
• ~/Library/Containers as a whole. Sandboxed apps keep documents and settings inside it, next to their caches.

When in doubt, don’t. A cache costs you disk space. A wrong delete costs you an afternoon.

What SpaceUp Mac automates

The manual route above works. It’s just tedious to repeat every few months, and it’s easy to miss folders you didn’t know existed.

SpaceUp Mac does the same job from a hand-curated catalog of these folders. Every item comes with a plain reason, like “Xcode rebuilds these the next time you build,” and nothing is deleted without your approval on a review screen. Rebuildable junk such as caches and logs is cleared directly, because trashing gigabytes of cache would just move the problem. Your own files, like big files found in Deep Scan, go to the Trash so you can undo. The few permanent actions, old iPhone backups and Empty Trash among them, say so clearly before you approve. The full model is in Cleaning and safety, and the reasoning behind it in Why Trash first.

The direct build also thins local snapshots for you through Advisor, which runs tmutil, Apple’s own tool, so you don’t have to remember the command. It asks for Full Disk Access to measure and clean the folders it shows, and you can revoke that anytime in System Settings (how that works).

One real scan found 117.45 GB of clearable junk. On a 256 GB MacBook Air, the whole process took free space from 39 GB to 168 GB. Your first scan and first clean are free, so you can see your own number before paying anything.

Some System Data is healthy

System Data will never be small, and it shouldn’t be. Caches come back by design, because apps genuinely use them, and a freshly cleared cache starts rebuilding within days. That’s normal, not a failure.

The win is removing the stale part: snapshots from weeks ago, the backup of a phone you sold, DerivedData for projects you’ll never open again. Clear those, let the rest live, and check back every few months. For the bigger picture beyond System Data, see our guide to freeing up disk space on a Mac.