What is “System Data” on Mac (and how to shrink it)

Open Storage settings and one grey block is usually bigger than it has any right to be: System Data. Hover over it and macOS tells you nothing you can act on. So what is System Data on Mac, and can you actually shrink it? Short version: it's a rough estimate of everything macOS couldn't file anywhere else, and no, you can't delete it as a lump, but you can shrink the real things inside it.

System Data is a category, not a folder

macOS sorts your disk into named buckets: Apps, Photos, Music, Documents, and so on. System Data is where everything that didn't cleanly match lands. It's a residual, catch-all category, not a place you can open in Finder. There's no /System Data/ folder to go delete.

It's also just an estimate. The macOS-internals community that reverse-engineers this stuff describes the figure as "little more than a guesstimate," and with reason. One documented case had a 100+ GB Music library showing as under 50 GB in Storage settings, with the missing ~50 GB quietly counted as System Data instead. So part of what inflates the number isn't hidden junk at all; it's files macOS simply misfiled.

Apple's own description stays deliberately broad. System Data, or Other on older releases, is a general category measuring "the storage space used by all Apple and third-party files that don't belong to any more specific category." Apple goes on to name the categories whose Info button is worth clicking, and System Data is not among them. The one number people fixate on is the one number macOS declines to itemise.

What actually lives in System Data

It's not one thing. It's a pile of unrelated things that share nothing except "didn't fit elsewhere":

• Caches: disposable copies apps and the system keep to load faster (~/Library/Caches and system-level caches).
• Logs and temporary files: diagnostic and scratch data macOS trims on its own schedule.
• Virtual-memory / swap files: memory paged out to disk when RAM runs tight.
• APFS local snapshots: point-in-time backups Time Machine leaves on your startup disk between backups.
• iOS / iPadOS device backups: full phone and tablet backups made on your Mac, tens of GB each.
• Application Support data: the bulk of what apps store per user: databases, plug-ins, downloaded models, saved state.
• Developer build junk: Xcode DerivedData and simulators, node_modules, package-manager caches, Docker.raw.

For the full teardown of each of these, with exact paths and where the big gigabytes actually hide, see the full breakdown of hidden storage on a Mac. If you're on an older macOS and see it labeled differently, that's what "Other" storage is; same catch-all, earlier name.

How to see it

Apple menu → System Settings → General → Storage. The bar chart at the top breaks your disk into categories; hover over the grey segment to see the System Data figure. That's as far as the built-in tools go. There's no button that opens it, itemizes it, or safely clears it. You get a number and a shrug.

How to safely shrink System Data

You can't shrink "System Data" directly, because it isn't a thing. You shrink it by clearing the specific, real files that get counted into it, and doing that safely means knowing which ones regenerate and which ones don't. The real levers, roughly in order of payoff:

• Clear user caches. Caches in ~/Library/Caches are generally safe to clear, since macOS and your apps rebuild them on next launch; the only cost is a slightly slower first load. Leave the system caches under /System/Library alone. Full detail: is it safe to delete cache on Mac.
• Delete old iOS/iPadOS backups. Often the single biggest quick win, since each backup runs to tens of GB. Delete them by name and date in Finder rather than by hand; see is it safe to delete iOS backups.
• Reduce local Time Machine snapshots. macOS keeps hourly snapshots on your startup disk and thins them automatically when space runs low, but they can occupy a large slice in the meantime. Let macOS reclaim them, or reduce how many Time Machine keeps locally.
• Clear developer build junk. If you write code, this is where System Data balloons: Xcode DerivedData and simulators, stale node_modules, Docker.raw, and package caches. All regenerable, all safe to clear once you know what they are.

Not sure which files are truly disposable? That's the whole question; start with what you can safely delete on a Mac before you delete anything.

One thing to skip: chasing System Data by hand-deleting things inside ~/Library you don't recognize. Fighting the pieces macOS actively manages (purgeable space, snapshots, system caches) risks removing a real backup or breaking an app for near-zero durable gain.

Why System Data on Mac gets so large

Nothing inside System Data prunes itself aggressively. Caches grow because almost no app cleans up after itself. Snapshots and iOS backups accumulate. Developer files stack up per project and per iOS version. Add the misfiled files that shouldn't be there at all, and the number climbs. On a busy Mac it commonly reaches tens of GB; people post to Apple's own forums with 100+ GB, and cases past 200 GB show up. Those aren't outliers. They're what happens when nothing ever cleans up and the tool that's supposed to show you won't.

Seeing it in plain terms

macOS gives you a grey block and no receipt. Plumby breaks System Data back into named pieces (caches, snapshots, iOS backups, developer build-up), each with its exact path and real size, and clears only the safe ones. Freed space is measured as each item goes rather than estimated, and anything it clears can go to the Trash rather than be deleted, so you can put it back. It never touches your documents, photos, or projects, only the regenerable junk that landed in System Data in the first place.