What you will achieve
Understand bloated System Data in Storage and safely reclaim space without breaking macOS.
System Data in Storage settings aggregates caches, snapshots, logs, iOS backups, and VM images — opaque by design. Chasing zero System Data is pointless; chasing disk full errors is not. Target known buckets: local snapshots, iOS backups, developer caches.
1) What System Data includes
Caches, logs, Time Machine local snapshots, iOS backups, VM swap, and “other” APFS metadata — not one tidy folder.
2) Safe cleanups
- Delete old iOS device backups: General → Storage → iOS Files or Finder → iPhone sync.
- Remove local Time Machine snapshots if space critical:
tmutil listlocalsnapshots /
sudo tmutil deletelocalsnapshots SNAPSHOT_DATE
3) Caches
Restart Mac; clear Downloads and ~/Library/Caches subfolders for apps you recognise — not blind rm -rf on all Caches.
4) Developer cruft
Xcode derived data and simulators — Storage recommendations or xcrun simctl delete unavailable for devs.
5) When not to chase
System Data fluctuates 20–40 GB on normal Macs — only act if disk full causes updates to fail. Avoid “cleaner” apps that delete system files.
6) iOS backup path
~/Library/Application Support/MobileSync/Backup holds device backups — delete old iPhones you no longer own after confirming new phone backed up.
7) VM and Docker
Docker.raw and Parallels VMs live inside user home but count toward System Data in aggregate — move VM bundle to external APFS and symlink only if app supports.
8) Log spam
Runaway daemon logging fills /private/var/log — restart clears some; persistent growth needs Console identification of repeating error process.
Verify
Storage chart shows more free space; macOS updates and apps still work; no missing data from targeted deletes only.
Additional troubleshooting notes
If steps above do not resolve the issue on the first attempt, reboot once, confirm System Settings → General → Software Update is current, and retry with a second administrator account to rule out profile or keychain corruption in your daily user. Document exact error text from Console.app with timestamp — vague “it still fails” without logs wastes support time. On Apple Silicon, re-test after full shutdown (not just restart) because firmware and Thunderbolt controllers reset only on cold boot. Intel Macs should repeat test in Safe Mode to bypass third-party login items. Before erase or keychain reset, verify Time Machine or clone backup completed — batch 3 guides assume Monterey/Ventura/Sonoma/Sequoia paths in System Settings; search Spotlight for renamed panes if your macOS version labels differ slightly.