You open About This Mac, click Storage, and see a giant gray "System Data" block eating 60, 80, even 120 GB of your SSD. The obvious question: is that normal? Unlike the macOS system files that Apple keeps tight control over, System Data is a catch-all that grows with your habits. This guide gives you concrete normal ranges by drive size, explains the most common culprits, and shows you exactly where to look in Finder and Terminal so you can decide what to reclaim.
What Is System Data on a Mac (and Why Is It So Vague)?
The System Data category in macOS Storage settings (found under Apple menu > System Settings > General > Storage on Sonoma and later) bundles together everything that does not fit neatly into the other labeled buckets: Applications, Photos, Music, and so on. In practice, System Data includes:
- Caches from apps and the OS, stored in
~/Library/Cachesand/Library/Caches - Log files in
~/Library/Logsand/var/log - Time Machine local snapshots (APFS snapshots that macOS stores on the boot drive before a backup completes)
- iOS device backups in
~/Library/Application Support/MobileSync/Backup - Xcode derived data and simulators, typically in
~/Library/Developer - Mail downloads and attachments under
~/Library/Mail - App support data from browsers, virtual machines, design tools, and more
- Orphaned app leftovers: support files whose parent app was deleted but whose data was never removed
Because this category accumulates silently over months and years, it is common for a machine that felt fine at purchase to show a bloated System Data figure after 18 months of normal use.
Normal System Data Size by Mac SSD Capacity (2026 Benchmarks)
The question "how big should System Data be on a Mac" does not have a single answer, but there are reasonable ranges based on drive size and usage profile. The figures below assume macOS Sequoia or Tahoe, a machine that has been in regular use for 12 to 24 months, no active local Time Machine snapshots, and no Xcode installed.
256 GB SSD
- Normal: 15 to 35 GB
- Worth investigating: 40 to 60 GB
- Bloated: 60 GB or more
On a 256 GB drive, System Data above 50 GB will meaningfully constrain free space. This is the configuration where cleanup has the highest practical impact.
512 GB SSD
- Normal: 20 to 50 GB
- Worth investigating: 55 to 80 GB
- Bloated: 80 GB or more
A 512 GB machine that has housed a few iOS backups, a browser with heavy cache use, and a couple of years of app churn will often sit in the 45 to 60 GB range. That is not an emergency, but it is a good time to check for old backups and logs.
1 TB SSD
- Normal: 25 to 65 GB
- Worth investigating: 70 to 120 GB
- Bloated: 120 GB or more
On a 1 TB machine, people tend to accumulate more: larger iOS device backups, browser profiles, and app support data. An 80 GB System Data reading is not uncommon, but anything above 100 GB almost always contains significant recoverable space.
2 TB SSD or larger
- Normal: 30 to 80 GB
- Worth investigating: 90 to 160 GB
- Bloated: 160 GB or more
Developers who run Xcode, Docker, or virtual machines are the outliers here. A 2 TB machine with Xcode simulators fully populated can legitimately show 200 GB in System Data-adjacent folders, so context matters. The key is knowing which specific folders are large.
The Biggest Contributors: Where Average System Data Goes on a Mac
Time Machine Local Snapshots
This is often the single largest hidden contributor. When Time Machine cannot reach its backup destination (a disconnected drive or NAS), macOS creates local APFS snapshots on your boot drive. These can accumulate to tens of gigabytes. To see them, run this in Terminal:
tmutil listlocalsnapshots /To delete them all:
tmutil deletelocalsnapshots /Note that macOS will eventually purge these snapshots automatically when it needs space, but it does so on its own schedule, which may not align with yours.
iOS and iPadOS Device Backups
iTunes and Finder backups of iPhones and iPads live at ~/Library/Application Support/MobileSync/Backup. A single iPhone backup can run 10 to 25 GB. Multiple backups from multiple devices or older superseded backups can quietly stack up. Open Finder, press Cmd+Shift+G, and paste that path to browse what is there. In Finder you can also go to System Settings > General > Storage > iOS Files to review and delete old backups from the GUI.
Xcode Derived Data and Simulators
If you have ever installed Xcode, derived data grows in ~/Library/Developer/Xcode/DerivedData and simulators live in ~/Library/Developer/CoreSimulator/Devices. These two locations alone can add 20 to 80 GB. Run this command to see their sizes:
du -sh ~/Library/Developer/Xcode/DerivedData
du -sh ~/Library/Developer/CoreSimulator/DevicesIn Xcode itself, you can delete derived data via Xcode menu > Settings > Locations > Derived Data. For simulators, use xcrun simctl delete unavailable in Terminal to remove runtimes for simulators you no longer test against.
Application Caches
Browsers are the main offenders. Chrome stores its cache in ~/Library/Application Support/Google/Chrome/Default/Cache. Firefox keeps its cache in ~/Library/Caches/Firefox. Safari's cache lives in ~/Library/Caches/com.apple.Safari. Video editing and rendering apps, creative tools like Figma and Sketch, and package managers like Homebrew all generate substantial cache directories in ~/Library/Caches.
To quickly see what is largest there:
du -sh ~/Library/Caches/* | sort -rh | head -20Log Files
Log files in ~/Library/Logs and /Library/Logs are usually small on a healthy machine (under 1 GB), but crash loops from misbehaving apps can generate gigabytes of diagnostic output. Worth a spot-check if your System Data is unexpectedly large.
How to Measure Your System Data Breakdown Without Guessing
The macOS Storage gauge gives you a single number with no detail. To actually understand what is consuming space, you have two practical approaches.
Terminal Approach (Free, Manual)
Run this command to get a sorted breakdown of your entire home Library folder:
du -sh ~/Library/* | sort -rh | head -30For system-level directories (requires entering your password):
sudo du -sh /Library/* | sort -rh | head -20This is accurate and free. The downside is that the output is a flat list: you need to drill down manually into whichever directories are unexpectedly large.
Using Crumb for a Visual Breakdown
Crumb, a native macOS menu-bar utility, scans your drive on-device (no account needed) and breaks System Data into labeled categories: caches, logs, app leftovers, iOS backups, and more. It shows you each folder's size alongside a plain-English explanation of what it is and whether it is safe to remove. You can compare what you see in Crumb directly against the normal ranges above to understand where your machine stands. The reviewable plan before any deletion is useful if you are not certain about a folder.
What You Can Safely Remove vs. What to Leave Alone
Not everything in System Data is reclaim-able, and some of it should not be touched.
Generally Safe to Remove
- Application caches in
~/Library/Caches(apps rebuild them on next launch) - Log files in
~/Library/Logs(unless you are actively debugging an issue) - Old iOS backups you no longer need
- Xcode derived data (rebuilds on next build) and simulators for old OS versions
- Time Machine local snapshots after confirming your backup destination is healthy
Leave Alone or Research First
- Contents of
~/Library/Application Supportfor apps you still use (deleting these resets the app's data) - Anything in
/Systemor/usrunless you are certain of what it is - Mail message stores unless you have confirmed IMAP copies exist on the server
- Containers in
~/Library/Containers(sandboxed app data, not just caches)
Knowing your actual System Data size and comparing it against the ranges above turns an abstract worry into a specific checklist. A 60 GB reading on a 1 TB machine is within normal range; the same number on a 256 GB drive is worth an afternoon of cleanup. If you want a faster path to the detailed breakdown, Crumb maps your System Data into labeled folders so the investigation takes minutes rather than an hour of Terminal output.