What Is System Data on Mac and How Do You Reduce It?

If you have ever opened About This Mac → Storage and stared at a thick grey bar labeled System Data, you are not alone. System data Mac storage is consistently one of the most-searched macOS complaints because the category is enormous, vague, and offers no obvious way to drill into it. This guide explains exactly what lives inside System Data, which parts macOS manages automatically, which parts you can safely shrink, and how to do it — both with Terminal commands and with a one-click tool.

What Is System Data on Mac? (The Real Answer)

"System Data" is Apple's catch-all label in the storage overview for everything that does not fit neatly into the named buckets — Apps, Photos, Documents, and iCloud Drive. It is not one folder; it is a collection of many different low-level categories spread across your drive. On a typical Mac that has been in use for a year or two, System Data commonly reaches 20–60 GB, and on development machines it can exceed 100 GB.

The main things that land under the System Data umbrella are:

• User caches — ~/Library/Caches/
• System caches — /Library/Caches/ and /System/Library/Caches/
• Application logs — ~/Library/Logs/ and /Library/Logs/
• Temporary files — /private/var/folders/ and /private/tmp/
• Virtual memory swap files — /private/var/vm/swapfile*
• Time Machine local snapshots — stored on the APFS volume, reported in System Data when no backup disk is connected
• Purgeable space — APFS content macOS has marked "safe to reclaim" but has not yet evicted
• Hibernation sleepimage — /private/var/vm/sleepimage (one file, usually the size of your RAM)
• Homebrew caches and downloads — ~/Library/Caches/Homebrew/
• Xcode derived data and simulators — ~/Library/Developer/Xcode/DerivedData/ and ~/Library/Developer/CoreSimulator/
• iOS device backups and firmware — ~/Library/Application Support/MobileSync/Backup/

Which Parts of System Data Are Safe to Delete?

Not everything in System Data is fair game. Here is a practical breakdown:

How to Check What Is Actually Taking Up Space

Before deleting anything, it helps to see the breakdown. The storage overview bar in System Settings gives totals but no drill-down. Two options:

Option 1: Terminal (du command)

Run these to get a quick size report for the biggest contributors:

# User caches
du -sh ~/Library/Caches/

# System caches (requires sudo)
sudo du -sh /Library/Caches/

# Logs
du -sh ~/Library/Logs/

# Xcode DerivedData
du -sh ~/Library/Developer/Xcode/DerivedData/

# Time Machine local snapshots
tmutil listlocalsnapshots /

Option 2: A disk visualizer

Crumb's Visualize tab shows a full treemap of your disk, lets you sort by largest folder, and highlights the biggest items inside your Library — so you can see at a glance whether it is DerivedData, a single app's cache, or something unexpected driving the number up. Its "Is this safe to delete?" AI feature lets you tap any unfamiliar folder and get a plain-English explanation of what it is and what the risk of removing it is, which is genuinely useful in the maze of /Library/Caches/ subdirectories.

How to Reduce System Data on Mac — Step by Step

Step 1: Clear user caches

1. Quit all open applications first.
2. Open Finder, press Cmd + Shift + G, and type ~/Library/Caches.
3. Select all subfolders and move them to Trash, then empty Trash.
4. Restart your Mac. Apps will regenerate their caches fresh.

Important: this is permanent. A few apps (notably some Electron apps and games) may take longer to launch the first time as they rebuild. If any app behaves oddly, reinstalling it resolves it.

Step 2: Delete old logs

rm -rf ~/Library/Logs/*
sudo rm -rf /Library/Logs/*

Unless you are actively debugging a crash, old log files have no value.

Step 3: Remove Time Machine local snapshots

1. List snapshots: tmutil listlocalsnapshots /
2. Delete all of them: tmutil deletelocalsnapshots /
3. On macOS Ventura and later you can also delete individual dated snapshots: tmutil deletelocalsnapshots YYYY-MM-DD-HHMMSS

macOS will automatically recreate snapshots on the next Time Machine backup cycle. The freed space will not appear immediately in the storage bar — APFS marks it as purgeable first and may take a few minutes to update the display.

Step 4: Clean up Xcode artifacts (developers only)

# DerivedData — safe to delete entirely
rm -rf ~/Library/Developer/Xcode/DerivedData/

# Old iOS Simulator runtimes (macOS 13+)
xcrun simctl delete unavailable

# Simulator caches
rm -rf ~/Library/Developer/CoreSimulator/Caches/

On an active development Mac, DerivedData and Simulator runtimes can account for 30–80 GB alone.

Step 5: Clean Homebrew

brew cleanup --prune=all

This removes all cached downloads and outdated formula versions. The --prune=all flag removes even recent cached files, not just those older than the default 120-day window.

Step 6: Remove old iOS device backups

1. Open Finder → your iPhone/iPad in the sidebar → Manage Backups (when the device is connected), or open System Settings → General → iPhone Storage on macOS Ventura+.
2. Delete backups for devices you no longer own.
3. For any device you still own, ensure you have an iCloud backup before deleting the local one.

What About the "System Data Huge Mac" Situation?

If System Data is genuinely enormous — say, over 100 GB on a machine that is not a development workstation — the usual culprit is one of three things:

• A single misbehaving app that has written a huge cache or log file. Sort by size inside ~/Library/Caches/ and ~/Library/Logs/ to find the offender.
• Virtual machine disk images or Docker overlays — these are counted as "Other" or "System Data" by the storage bar but live in obvious locations (~/Library/Containers/com.docker.docker/, or your VM library folder).
• APFS snapshots from a failed upgrade — a macOS upgrade that was interrupted or rolled back can leave multi-GB snapshots. tmutil listlocalsnapshots / will surface these.

If you want a single view that surfaces all of these at once without manually navigating each folder, download Crumb and run a one-click Clean + Visualize. The Clean pass targets caches, logs, temp files, and purgeable APFS content in one operation, while the Visualize treemap makes the remaining large items obvious so you can decide what to tackle next.

What NOT to Delete

A few things labeled as System Data must be left alone:

• Active swap files (/private/var/vm/swapfile0, etc.) — these are live virtual memory pages; deleting them crashes running processes.
• Anything inside /System/ — this volume is read-only under System Integrity Protection on macOS 10.15 and later; you cannot delete from it in normal operation and should not try.
• Keychains (~/Library/Keychains/) — these store passwords and certificates.
• Preferences (~/Library/Preferences/) — deleting here resets all app settings and is rarely worth the tradeoff.

Conclusion

System data Mac storage is confusing because Apple uses one label for a dozen different low-level categories. The genuinely shrinkable parts — user caches, logs, Xcode artifacts, Time Machine snapshots, and Homebrew downloads — can often reclaim 10–50 GB on a machine that has been in use for a year or more. The keys are: know what each subcategory actually is, never touch active swap or the read-only System volume, and treat any deletion as permanent. Whether you go folder-by-folder with Terminal or let a tool like Crumb surface and clear the safe items in one pass, the process is the same; it just takes different amounts of time.