How to Clear System Data on Mac: Fix Large „System Data” Storage

Quick answer: „System Data” (formerly „Other”) is a macOS bucket for caches, logs, local snapshots, app leftovers, and system caches. To free space safely: review Storage Management, delete large iOS backups, remove local Time Machine snapshots, clear caches and unused apps, and reboot in Safe Mode. Use built-in tools first; if you prefer scripts, see the recommended GitHub utility linked below.

This guide explains what System Data contains, why it grows, and gives step-by-step, safe cleanup methods that preserve your data and macOS integrity. Read the short checklist first, then follow the detailed instructions that match your comfort level (GUI, Terminal, or script).

Pro tip: Always have a current backup (Time Machine or clone) before removing system files or running cleanup scripts. Mistakes are rare but recoverability is not optional.

What „System Data” on Mac actually is

System Data is a macOS storage category that aggregates files which don’t neatly fall into Photos, Apps, Documents, or System meaning visible OS files. It typically includes caches, temporary files, app support data, browser caches, logs, disk images, and local Time Machine snapshots. Apple intentionally groups diverse files under this label to simplify the Storage UI.

Because the category contains many file types and locations, its reported size can jump quickly. For example, large Safari or Chrome caches, Xcode derived data, Mail attachments, and iOS device backups stored locally will all inflate System Data. The OS uses some of this space for performance (caches), so not all of it should be deleted indiscriminately.

Knowing the components helps you target cleanup. Some items are safe to delete (temporary caches, stale app caches, old iOS backups), while others—like system logs needed for diagnostics or active local snapshots—require careful handling. This guide highlights safe operations and explains when to avoid aggressive deletions.

Why System Data can grow very large (and how macOS manages it)

macOS dynamically manages storage: it caches to speed up apps and keeps local snapshots to let Time Machine restore recent changes even when your backup drive is offline. When disk space is plentiful, macOS lets caches expand; when space gets tight, the system is supposed to purge caches automatically. But problems arise when purges fail (buggy apps, stalled background jobs, or interrupted backups), leaving stale data behind.

Third-party apps also contribute. Developers often store derived datasets (e.g., Xcode build artifacts, Docker images, or virtual machine files) in locations macOS counts as System Data. These can be huge and are sometimes forgotten. Another common culprit is large, orphaned iOS backups stored in ~/Library/Application Support/MobileSync/Backup.

Understanding this lifecycle explains why manual intervention is sometimes necessary. Regular maintenance—removing old backups, trimming large app caches, and letting macOS rebuild caches—keeps System Data reasonable without sacrificing performance.

How to safely clear System Data on Mac (step-by-step)

This section offers a tiered approach: start with the GUI (least risk), then Terminal commands for targeted cleanup, and finally optional scripts if you prefer automation. After each major action, check Apple menu > About This Mac > Storage to see the result.

Before you begin: close apps, disconnect peripheral drives you don’t intend to touch, and ensure a recent backup. If you rely on Time Machine, connect your backup disk and let a backup finish so there is an external copy of local snapshots if needed.

Follow these ordered steps. Do only what you understand—skip Terminal operations if you prefer GUI-only maintenance.

1. Use Storage Management and built-in cleanup

Open Apple menu > About This Mac > Storage > Manage. This tool surfaces large categories and offers safe options: Recommendations (Store in iCloud, Optimize Storage, Empty Trash Automatically) and Large Files & Reduce Clutter views. Start here to identify obvious space hogs like big downloads, duplicate files, or large app support files visible to the interface.

The „Reduce Clutter” list helps you review large files by date and size. Delete old disk images (.dmg), installers, or downloads you no longer need. For app-related large items, open the app and use its internal preferences (e.g., clear caches within Spotify, Dropbox, or development tools) where available.

When you delete from Storage Management, most items go to Trash—empty the Trash to finalize freeing space. Reboot after heavy deletions: macOS will rebuild some caches and report freed storage more accurately.

2. Remove local Time Machine snapshots and stale iOS backups

Local snapshots can consume gigabytes. To list local snapshots, open Terminal and run: tmutil listlocalsnapshots /. To remove all local snapshots, run: sudo tmutil thinlocalsnapshots / 999999999999 or delete specific snapshots with sudo tmutil deletelocalsnapshots YYYY-MM-DD-HHMMSS. Thinning removes snapshots safely without touching remote backups.

Old iOS backups: open Finder (or iTunes on older macOS) > Manage Backups (or Preferences > Devices) to see device backups, then delete unneeded ones. Locally stored backups are also at ~/Library/Application Support/MobileSync/Backup—inspect that folder and delete verified old backups. Be cautious: delete only backups you no longer need.

After removing snapshots/backups, run diskutil apfs list to confirm space change if desired, then restart your Mac to allow the system to recalibrate storage reporting.

3. Clear caches, logs, and temporary files

Most caches are safe to delete because apps rebuild them. User caches live in ~/Library/Caches and system caches in /Library/Caches. To clear user caches manually: quit apps, then in Finder choose Go > Go to Folder and paste ~/Library/Caches. Delete large subfolders for problematic apps (e.g., com.apple.Safari, com.google.Chrome). Avoid deleting system-level caches unless you know what they are.

Terminal approach for user cache cleanup (careful): rm -rf ~/Library/Caches/* clears many caches but can be heavy-handed. Prefer deleting per-app caches rather than a blanket removal. For logs, inspect ~/Library/Logs and /var/log; remove excessive .log files older than a week if they are unusually large.

Browser caches and plugin caches often reclaim large amounts of space. Within each browser, use Settings to clear cache and site data. After deleting caches, restart apps and macOS to let the system repopulate necessary caches optimally.

4. Find and remove large app data (Xcode, Docker, virtual machines)

Developer tools and virtualization are frequent culprits. Xcode stores derived data at ~/Library/Developer/Xcode/DerivedData — deleting its subfolders can free tens of gigabytes and Xcode will rebuild what it needs. Docker images and containers live in ~/Library/Containers/com.docker.docker and in Docker’s internal VM; prune via Docker Desktop or run docker system prune -a cautiously.

Virtual machines (Parallels, VMWare, UTM) store large virtual disks—back them up if you need them, then remove or relocate to an external drive. Large Mail attachments and Photos caches may also be hidden under Mail and Photos apps; use each app’s storage settings for trimming.

For each app, check preferences for cache paths and consider moving seldom-used large assets (VM images, raw video footage) to external storage. Doing so reduces System Data pressure and keeps local disk lean.

5. Use a vetted script or utility (optional)

If you prefer scripting, use a well-audited tool. The repository at clear-system-data-on-mac provides a conservative cleanup script that targets caches, local snapshots, and common leftovers; read it before running. Scripts can automate repetitive tasks but require trust and understanding of each command.

Run scripts in a Terminal session with explicit confirmation prompts and review what will be deleted. Avoid running random cleanup scripts you find online without inspection. Prefer scripts from reputable sources or open-source repositories you can review line-by-line.

If you run a script, keep a copy of the first run’s output so you can reverse changes manually if needed and check for unexpected deletions. After automated cleanup, reboot and check Storage again.

Precautions, verification, and aftercare

Always have an up-to-date backup before deleting system files. If you accidentally remove something important, a fresh Time Machine backup or a disk image makes recovery straightforward. Don’t use sudo rm -rf commands copied from random web posts without understanding each path.

After cleanup, verify results: Apple menu > About This Mac > Storage should show reduced System Data. You can also use du -sh and ncdu (install via Homebrew) to inspect directory sizes and find remaining large folders. For APFS users, check snapshots with tmutil listlocalsnapshots / and confirm they are gone.

Finally, schedule routine maintenance: empty Trash periodically, remove old iOS backups after device upgrades, and run Storage Management quarterly. If System Data spikes again, inspect logs and large folders to find a persistent source (a misbehaving app or runaway cache process).

Troubleshooting common scenarios

Scenario: System Data didn’t shrink after deletion. Wait a few minutes and reboot; macOS recalculates storage and may take time. If no change after reboot, check for hidden containers (~/Library/Containers) and local snapshots still present. Also ensure you emptied Trash.

Scenario: Space freed but comes back quickly. This often indicates an app regenerating large caches (e.g., browsers, photo apps, podcast downloads). Identify the app by sorting folders in Finder by size or using ncdu. Temporarily quit suspect apps and watch storage usage change.

Scenario: You see huge APFS snapshots. Delete them with tmutil as described earlier, or run a manual Time Machine backup to an external disk—macOS may delete local snapshots after a successful external backup completes.

FAQ

Semantic core (keyword clusters)