System Data category is huge on Mac

After this, you'll know exactly which parts of System Data are worth clearing and which are normal to leave alone.

M1M2M3M4 · macOS 14–26 · Verified 2026-09-08
On this page
Quick answer

Apple's own definition of "System Data" (also labeled "Other" in older macOS) is deliberately vague — "storage space used by all Apple and third-party files that don't belong to any more specific category." In practice that usually means caches, logs, Time Machine local snapshots, old iOS device backups, and leftover installer files. 70–100GB+ is commonly reported and isn't automatically a problem; check the specific known contributors below before assuming something is broken.

Why this happens

Apple's storage-management documentation doesn't itemize what's in System Data, which is exactly why it feels unaccountable — it's a catch-all bucket, not a single folder you can inspect and clean directly. The commonly cited contents (system caches, log files, Time Machine local snapshots, VM swap files) come from accumulated user reports and support-forum answers, not an official Apple breakdown, so treat any specific number as directional rather than exact.

One claim worth flagging explicitly: it's sometimes suggested that Rosetta 2's translation cache, or universal binaries carrying both x86_64 and arm64 code, meaningfully inflate System Data on Apple Silicon specifically. We looked for solid evidence of this and didn't find it — the one documented report of a large Rosetta cache was an isolated, unconfirmed case, and an Apple Community moderator pushed back on the theory in that same thread. Universal binaries are objectively larger on disk than single-architecture ones, but nothing we found quantifies that as a meaningful driver of a 70GB+ System Data category. Don't spend time chasing Rosetta as the cause without better evidence than that.

Fix it

  1. Check Time Machine local snapshots first — this is the single most common real contributor, and it's covered in full with commands in disk full but no large files to delete. Come back here once you've ruled that out.

  2. Check for old iOS device backups, which aren't removed automatically even after you've made newer ones: open Finder, ⇧⌘G, and go to ~/Library/Application Support/MobileSync/Backup. Delete old ones directly in Finder, or manage them from Finder's own device-backup list if you still have the device.

  3. Check for leftover installer packages and disk images — a .dmg or .pkg sitting in Downloads after installing something is pure waste, and these are often multiple gigabytes each. A quick way to spot the biggest ones:

    Reads the system

    What it does: lists the 15 largest top-level items under your home folder.

    After: nothing changes, this only reads.

    du -x -d 2 ~ 2>/dev/null | sort -rh | head -15

    Be aware that third-party disk-usage visualizers (GrandPerspective, DaisyDisk, OmniDiskSweeper) have limited visibility into System Data specifically, since much of it is sealed/system-owned — they're genuinely useful for finding large personal files, but don't expect them to fully account for the System Data number in About This Mac.

Still broken?

Verified on

ChipmacOSVerified
M1 (MacBook Air)26.62026-09-08
M2 Pro (Mac mini)26.62026-09-08
M3 (MacBook Pro)26.6.22026-09-08
M4 (MacBook Pro)26.62026-09-08

Related problems