What Is System Data on Mac? (And How to Shrink It)

You open Storage settings expecting apps and photos to be the biggest offenders.

Instead there's a wall of dark gray labeled "System Data," and it's bigger than everything else on the drive combined.

There's no folder to open. No obvious junk sitting in a Downloads folder waiting to be dragged to Trash. Just a number that keeps climbing every time you check.

I've chased this thing across a dozen Macs, from a 2019 Intel MacBook Pro to an M3 machine running the current build of macOS Tahoe. The pattern is almost always the same, and so are the fixes.

Most explanations online either wave their hands at "cache files" or push you straight toward a paid cleaner app. Neither approach tells you what's actually sitting on your drive, which is the part that matters if you're trying to reclaim real space before an update fails.

What System Data Actually Is

Apple's own description of this category is deliberately vague, and that's not an accident.

System Data is a catch-all bucket for anything the Storage pane can't confidently sort into Photos, Apps, Documents, iCloud Drive, or the other named categories.

It isn't a single directory you can browse in Finder. macOS pulls pieces from your user Library, the system Library, private temp folders, and hidden snapshot data, then totals it all into one number.

That's the part that trips people up. You can search for a file called "System Data" for the rest of your life and never find one, because the category describes a calculation, not a location.

Here's what's typically hiding inside that total:

Cached files from apps, browsers, and background system services
Log files macOS keeps around for diagnostics and crash reporting
Virtual memory swap files created when RAM runs low
Local Time Machine snapshots stored right on your internal drive
iPhone and iPad backups made through Finder
Font caches, plug-ins, and leftover app support files
Spotlight index data while it's mid-rebuild
Files downloaded during a macOS update that never fully installed

Any single item on that list can spike on its own without you noticing. Stack three or four together, like a fresh Time Machine snapshot landing on top of a stalled Spotlight reindex, and System Data can balloon past 80GB seemingly overnight.

"Other" Storage Got a Rename, Not a Redesign

If you've owned a Mac since before 2021, you probably know this category by its older name: Other.

Apple renamed it to System Data starting with macOS Monterey, and it also split out a separate "macOS" category to represent the operating system's own footprint.

The rename didn't change what's actually inside the bucket. It just made the label sound more official, which in my experience created more confusion rather than less, since people assumed a fancier name meant a clearer explanation.

Splitting out a dedicated macOS category was arguably the more meaningful change. It let Apple show the operating system's own footprint as a fixed, predictable number, while everything volatile and user-generated stayed grouped under System Data where it could keep shifting day to day.

How Much System Data Is Actually Normal

This is the question I get asked more than any other, and the honest answer is "it depends," but there are real benchmarks worth knowing.

On a machine running a few dozen apps, active iCloud Photos syncing, and normal daily use, somewhere between 10GB and 25GB is unremarkable. Past 30GB, something is quietly accumulating. Past 60GB to 80GB, you're almost certainly carrying an old snapshot or a forgotten device backup.

Here's how System Data stacks up against the other categories you'll see in that same Storage graph:

Storage Category	What's Actually Inside	Effort to Manage	Impact If Ignored	Worth Cleaning Up?
Photos	Your actual image and video library	Low, managed inside the Photos app	Low, since iCloud absorbs most of it	Rarely
Documents & Desktop	Files you personally saved	Low, fully visible in Finder	Low	Sometimes
Applications	Installed app bundles	Low, uninstall by dragging to Trash	Low	Occasionally
macOS	The operating system's own files	None, Apple manages this entirely	High if you tamper with it	Never touch manually
System Data	Caches, logs, snapshots, backups, leftovers	High, scattered across dozens of folders	High, can block installer updates	Yes, on a regular schedule

System Data is the only row on that table where the fix isn't "open an app and delete something obvious." That's exactly why it generates so much frustration compared to every other category.

It also helps to track the number over time rather than reacting to a single reading. Screenshot the Storage graph every few weeks if you can. A slow, steady climb across months usually means genuine buildup, while a sudden jump right after a software update is almost always temporary.

A Quick Note on External Drives

System Data only measures your internal boot volume, not anything plugged in externally.

If you're storing a game library or a Time Machine backup on a USB-C drive, that space shows up in Disk Utility separately and never counts toward this category at all. I've seen people spend an hour hunting for phantom System Data on a drive that was never the problem in the first place.

The Usual Suspects Behind Most of the Growth

Not every Mac accumulates System Data the same way. Developers, gamers, and everyday users each tend to feed different corners of it.

For developers, the usual culprits are:

Xcode's DerivedData folder, which can quietly grow past 20GB on an active project
iOS Simulator runtime files left behind after testing old operating system versions
Docker Desktop images and stopped containers that never get pruned
Homebrew's download cache, which keeps old package archives by default
Duplicate node_modules folders scattered across dozens of abandoned projects

For gamers, it's usually a different set of folders:

Steam's shader pre-caching data, which can reach several gigabytes per demanding title
Old save-game backups and crash logs from titles you uninstalled months ago
Battle.net, Epic, and other launcher caches that survive an app deletion untouched

For everyday users, the growth tends to come from:

Mail's downloaded attachments, which stay cached even after you archive the message
Messages attachments and shared photos synced across every linked device
Photos library derivatives created whenever iCloud Photos re-processes thumbnails
Cloud sync placeholder files from Dropbox or Google Drive that never fully cleared

Once I started sorting a client's Mac into one of these three buckets first, cleanup stopped being guesswork and started being targeted.

My Hands-On Workflow for Finding What's Actually Eating the Space

I stopped guessing years ago and built a routine instead. It takes about ten minutes and works the same whether you're on an aging Intel Mac or the newest Apple silicon chip.

Open System Settings, then General, then Storage, and let the bar graph fully load before touching anything
Click the info button next to System Data if your macOS build offers one, since recent versions increasingly break out backups and snapshots as separate line items
Open Terminal and run tmutil listlocalsnapshots / to see exactly how many local Time Machine snapshots are sitting on your internal drive
Check ~/Library/Application Support/MobileSync/Backup for old iPhone or iPad backups made through Finder that nobody remembers creating
Open ~/Library/Caches and look for any single app folder that's quietly grown past a gigabyte or two
Restart once, since a plain reboot flushes a surprising amount of stale cache and swap data on its own

In one case on a client's MacBook Air, step four alone recovered 34GB. Three old iPhone backups had been sitting there untouched for close to two years.

One edge case worth flagging: if you recently migrated to a new Mac using Migration Assistant, System Data will look enormous for the first day or two while Spotlight reindexes everything at once. Give it 24 to 48 hours before drawing any conclusions from the number you see.

If you'd rather automate the cache half of this process, I already mapped out the exact folders worth wiping by hand in a separate guide on clearing temp files, and the two routines pair well together.

Pro Tip: Don't trust the Storage number immediately after deleting anything. macOS marks freed space as "purgeable" first and only reclaims it fully once the system decides it's safe, sometimes only after your Mac has sat idle for an hour or more.

The Honest Limitations and Bottlenecks

Apple never shipped a "Clear System Data" button, and that's not an oversight on their part.

Deleting the wrong cache or log file mid-process can crash an app on next launch, or worse, corrupt a macOS update that's only half installed.

Local Time Machine snapshots are the trickiest piece of the puzzle. They're built to auto-thin themselves once space gets tight, but on a drive that's already nearly full, that thinning process can lag noticeably behind reality, showing you a bigger number than what's genuinely recoverable at that moment.

This gets even messier on a shared family iMac, where storage used by other user accounts gets tallied completely separately from System Data. Mixing those two categories up is one of the most common troubleshooting mistakes I run into.

Third-party cleaner apps promise a one-click fix for all of this. Most of them are just running the same Terminal commands you could run yourself, minus any real transparency about what's actually being removed.

FileVault encryption adds another wrinkle worth knowing about. Because the entire volume is encrypted at the block level, some disk-mapping tools can't fully inspect every folder until your Mac has unlocked normally, which is one reason two different apps can report noticeably different totals for the exact same drive.

Apple Silicon Macs behave a little differently here too. Unified memory means the same pool handles both CPU and GPU tasks, so swap files get created more aggressively under heavy load than they did on older Intel machines. A temporarily inflated System Data reading right after rendering video or running a large local AI model usually shrinks back down once you close those apps and let the system settle.

Pro Tip: If System Data spikes right after downloading a macOS update, leave it alone for 24 hours before panicking. The installer stages the entire update package inside System Data first, then cleans up after itself once installation completes.

Practical Setup and Terminal Commands That Actually Help

Once you know what's genuinely inside the category, the fixes are mostly mechanical rather than mysterious. Here's the sequence I run on every Mac I maintain.

Empty Trash from every location, since Mail, Photos, and Finder each keep their own separate bin
Temporarily disable local snapshots with sudo tmutil disablelocal if you already back up to an external drive anyway
Offload old iOS device backups through Finder's own backup manager instead of deleting the raw files by hand
Clear browser caches from inside each browser's own settings rather than deleting the folder blind
Run Disk Utility's First Aid pass afterward to confirm nothing got corrupted during the cleanup

If you're a developer, it's worth adding a few extra commands to that routine:

Clear Xcode's build cache with rm -rf ~/Library/Developer/Xcode/DerivedData/*
Remove unused Docker images and stopped containers with docker system prune -a
Clean out old Homebrew downloads with brew cleanup -s

Run each of those with a little caution, since DerivedData and Docker images will simply rebuild the next time you need them, but a live database container should never be pruned blind.

None of this involves defragmenting anything, and honestly, it shouldn't. SSDs don't fragment the way old spinning drives did, a point I've hammered on before in my full breakdown of Mac defragmentation myths, and it applies just as directly here.

Run df -h / in Terminal before and after any cleanup pass. It reports real physical disk usage, which is often more trustworthy than the Storage pane's graph while that graph is still busy reindexing.

Frequently Asked Questions

Is it safe to delete System Data on Mac? Not directly, since there's no single file or folder actually named that. It's safe to remove the specific things that make it up, like old device backups, stale browser caches, or snapshots you no longer need.

Why did System Data suddenly grow overnight? Usually one of three things: a macOS update staging itself before installation, a fresh Time Machine snapshot being created, or Spotlight rebuilding its index after a major software update.

Does restarting my Mac clear System Data? Partially. A restart flushes some temporary caches and swap files, though it won't touch larger items like old device backups or a bloated Photos library cache.

Is System Data the same thing as the old "Other" storage category? Yes, functionally. Apple renamed Other to System Data starting with macOS Monterey and split the operating system itself into its own separate macOS category around the same time.

Apple has quietly gotten better at explaining this category with each release, breaking System Data into more readable sub-items than Monterey ever offered. Tahoe already shows more granular detail in the Storage pane than Sonoma did a couple of years ago, and I'd expect that trend to continue rather than reverse.

I don't expect an actual "Clear System Data" button to ship anytime soon, since the category is intentionally a moving target that reflects whatever your Mac happens to be doing at that exact moment. Building a single button to safely clear all of it would mean Apple guessing which snapshots, caches, and backups you personally still need, and that's a call no one but you can really make.

The realistic path forward is the one that's worked for years now: check Storage monthly, know the handful of folders that actually cause the growth on your specific setup, and stop treating a gray bar on a graph like a mystery that needs special software to solve. Once you know where to look, ten minutes of Terminal commands beats any paid cleaner app I've tested.