If your Mac is showing a swollen System Data category in Storage settings and every guide you've found tells you to open Terminal and type cryptic commands — this one is different. You'll learn how to clear system data on Mac without Terminal using only clicks, and just as importantly, you'll learn exactly what not to touch so you don't break anything.
What Is "System Data" on a Mac?
Open Apple menu > System Settings > General > Storage (macOS Ventura 13 and later) or Apple menu > About This Mac > Storage (macOS Monterey 12). You'll see a bar chart that breaks your drive into categories: Applications, Documents, Media, and one often surprisingly large one simply called System Data.
System Data is a catch-all for everything macOS can't cleanly classify elsewhere. It typically contains:
- Caches — temporary files apps and macOS create to speed up future work (
~/Library/Caches,/Library/Caches) - Logs — diagnostic and crash reports (
~/Library/Logs,/Library/Logs) - Temporary files — files in
/private/tmpand/private/var/folders - Purgeable space — files macOS has already marked safe to reclaim but hasn't freed yet (iCloud-synced local copies, Optimized Storage placeholders)
- App support data — databases, saved states, and working files in
~/Library/Application Support - Leftover files from deleted apps — support folders and preference files that survived an app drag-to-trash
- Time Machine local snapshots — rolling backups stored locally before they upload
Many of these are genuinely safe to clear. A few are not. The rest of this guide walks you through each category and tells you what to do with it — no Terminal required.
Step 1: Let macOS Free Purgeable Space First
Before doing anything manually, give macOS a chance to do its own housekeeping. Purgeable space appears as part of System Data, but macOS reclaims it automatically when disk pressure rises. You can nudge it faster:
- Open System Settings > General > Storage.
- Next to Recommendations, click Info (the circled i icon).
- Review each suggestion. The safest ones are Empty Trash Automatically and Reduce Clutter (which shows large files you can review and delete one by one).
- If you use iCloud Drive, enabling Optimize Mac Storage here moves local copies of older files to the cloud, which shrinks System Data noticeably.
After making changes, wait a minute and reopen the Storage view. The bar often shifts by several gigabytes with no other effort.
Step 2: Clear User Caches Safely
User caches live in ~/Library/Caches. They are the single biggest safe win inside System Data. Apps rebuild these automatically the next time they run, so deleting stale cache folders is low-risk. The process without Terminal:
- In Finder, press Shift + Command + G to open the Go To Folder dialog.
- Type
~/Library/Cachesand press Return. - Sort by Size (View > Show View Options > Sort by Size).
- Identify folders belonging to apps you recognize — browser caches, Xcode derived data, Spotify, Zoom. Drag individual folders to the Trash (not the entire
Cachesparent folder itself). - Empty the Trash.
Do the same for ~/Library/Logs. Log files contain historical diagnostic information; deleting them loses that history but causes no functional harm.
What NOT to delete in ~/Library/Caches
- Anything labeled
com.apple.*that you don't recognize — macOS system caches can cause odd behavior if removed while the related service is running. Restart first if you want to clear them. - The entire
~/Library/Application Supportfolder — this contains active app databases, not just caches. Deleting the wrong subfolder here can erase saved data, game progress, or local email stores.
Step 3: Delete Leftover Files from Removed Apps
When you drag an app to the Trash, macOS deletes the .app bundle — but leaves behind support files, preferences, and caches scattered across ~/Library. These stranded files accumulate invisibly over years and can add up to gigabytes.
Hunting them manually means cross-referencing at least four locations for every removed app:
~/Library/Application Support/AppName~/Library/Preferences/com.developer.AppName.plist~/Library/Caches/com.developer.AppName~/Library/Containers/com.developer.AppName
This is tedious and error-prone. Crumb handles it automatically: its Uninstall tab finds an app's main bundle and all associated leftover files in one view, so you can review and remove everything together with a single click rather than hunting through four or more Library folders by hand.
Step 4: Remove Time Machine Local Snapshots
If you use Time Machine, macOS keeps rolling local snapshots on your drive before they transfer to the backup destination. These count toward System Data and can be surprisingly large on laptops that haven't connected to their backup drive in a while.
To remove them without Terminal:
- Open System Settings > General > Time Machine.
- Click Options and make sure your backup drive is connected.
- Trigger a manual backup now (Back Up Now). Once the backup completes successfully, macOS automatically trims the local snapshots it no longer needs.
If your backup disk is not available, the snapshots stay until it is. This is intentional — they are your safety net until an offsite backup confirms the data.
Step 5: Clear System-Level Caches (Carefully)
System caches in /Library/Caches (no tilde — the root-level Library) require administrator permission to delete. You can reach them the same way:
- Shift + Command + G in Finder, type
/Library/Caches. - Authenticate when prompted.
- Delete only folders you recognize and know are from third-party software (e.g., old Homebrew caches, updater caches from apps you've uninstalled).
Leave any folder you don't recognize. System caches that macOS actively uses will rebuild automatically, but removing the wrong one while its service is running can produce errors until the next restart.
Safe vs. Not Safe: Quick Reference
| Location | Safe to delete? | Notes |
|---|---|---|
~/Library/Caches (subfolders) |
Generally yes | Rebuilt automatically; apps may be slower on first launch |
~/Library/Logs |
Yes | Loses diagnostic history, no functional impact |
/Library/Caches (subfolders) |
Caution | Only delete recognizable third-party folders; restart after |
~/Library/Application Support |
Caution | Contains active app data; only remove leftovers from apps you've uninstalled |
~/Library/Containers |
Caution | Sandboxed app data; removing active app containers erases its local data |
/System/Library |
No | Core macOS files; SIP protects most of this, but don't try |
~/Library/Preferences |
Only leftovers | Deleting active app prefs resets that app's settings |
| Time Machine local snapshots | Yes, after backup | Trigger a successful backup first |
The One-Click Alternative: Doing It All at Once
If stepping through each Library folder sounds tedious — or if you want a second opinion on whether a specific folder is safe to remove — download Crumb. Its one-click Clean handles user caches, system caches, logs, temporary files, and purgeable space in a single pass without opening Terminal once. The Uninstall tab surfaces app leftovers that manual hunting misses, and the built-in Is this safe to delete? check explains any folder in plain language before you commit to removing it.
Crumb is Apple-notarized, requires no account, and processes everything on-device. The free tier covers one full cleanup — enough to see exactly how much is recoverable before deciding whether to pay for ongoing use.
How Much Space Can You Expect to Recover?
There's no universal answer because it depends entirely on how long the Mac has been in service, which apps you've installed, and whether you've ever cleaned it before. A Mac used for development with Xcode can have 20 GB or more in derived data alone. A lightly used Mac might reclaim 2–4 GB. The built-in Storage view gives you a realistic baseline before you start.
What matters more than the number is doing it correctly: cleaning is permanent. Caches rebuild, but if you delete a folder from Application Support that contained your app's local database, that data is gone. Read labels carefully, and when in doubt, use the Is this safe to delete? feature in Crumb or simply skip the folder.
Conclusion
Clearing System Data on a Mac doesn't require a single Terminal command. Start with macOS's built-in Storage recommendations to let the OS do easy work first, then manually clear user caches and logs through Finder's Go To Folder dialog, remove app leftovers from apps you've already deleted, and let a successful Time Machine backup trim local snapshots. Work folder by folder, delete only what you recognize, and treat cleaning as permanent. Done carefully, you can reclaim meaningful space — and keep your Mac running cleanly — without ever touching the command line.