If your Mac has been running slowly or your storage panel shows an alarming "System Data" figure, clearing the system cache is one of the first things worth trying — but it is also one of the easiest ways to cause problems if you delete the wrong files. This guide explains exactly which caches live where, which ones macOS protects, the safe order of operations, and what to skip entirely.
What Is the System Cache on Mac?
macOS maintains several layers of caches to speed up repeated operations. Most of what users call the "system cache" lives in two places:
- /Library/Caches — system-wide caches written by Apple daemons and third-party services that run as root. Requires administrator privileges to modify.
- ~/Library/Caches — per-user caches written by apps running in your own account. Your account owns these files, so no admin rights are needed.
Beyond those two directories there is a third layer: the /System/Library/Caches path. This is managed directly by macOS and is protected by System Integrity Protection (SIP). You cannot delete files here, even as root, without disabling SIP — and you should not do so on a healthy Mac.
System Data and Purgeable Space
macOS Monterey and later show a "System Data" category in System Settings › General › Storage. A portion of that number is purgeable: APFS-managed caches, iCloud optimized storage placeholders, and OS update caches that macOS reclaims automatically when disk space is needed. You do not need to delete these manually; macOS handles them. The non-purgeable remainder inside System Data includes fonts, drivers, and kernel extensions — leave those alone.
Which Caches Are Safe to Delete?
| Location | Owner | Admin needed? | SIP protected? | Safe to clear? |
|---|---|---|---|---|
| ~/Library/Caches | Current user | No | No | Yes — app caches regenerate |
| /Library/Caches | System / root | Yes | No | Mostly yes — with care (see below) |
| /System/Library/Caches | macOS | Yes (root) | Yes | No — leave entirely alone |
| /private/var/folders | System | Yes | No | Temporary only; macOS manages automatically |
The rule of thumb: if macOS or a system daemon wrote it into a path you do not own, treat it with caution. Apps will recreate their own caches the next time they run, but some system-level caches — especially those tied to kernel extensions or GPU shaders — can cause a slow first boot or a brief login hiccup if cleared incorrectly.
How to Clear the System Cache on Mac Manually
Before you start: close all open apps and make sure you have a recent Time Machine or other backup. Cache deletion is permanent.
Step 1 — Clear your user cache first
- In Finder, press Command + Shift + G and type
~/Library/Caches, then press Return. - Select all folders (Command + A), then move them to Trash. Do not empty Trash yet.
- If any item shows "in use" and refuses to move, skip it — an app currently holds that file open.
Step 2 — Clear the system-wide /Library/Caches
This requires your administrator password. Open Terminal (Applications › Utilities › Terminal) and run:
sudo rm -rf /Library/Caches/*You will be prompted for your password. The command deletes the contents of /Library/Caches but not the folder itself. macOS and third-party services repopulate it on next use.
What to skip inside /Library/Caches: If you want to be conservative, avoid removing subdirectories whose names match kernel extensions or graphics drivers (e.g. anything with com.apple.kext in the name). These are regenerated but can cause a slower first boot.
Step 3 — Flush the DNS cache
The DNS resolver cache is separate from the file-based caches above. To flush it:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderThis takes effect immediately and does not require a restart.
Step 4 — Restart before emptying Trash
Restart your Mac before you empty the Trash. A restart lets macOS recreate essential runtime caches (like the font cache and dyld shared library cache) so the system comes back up cleanly. After the restart, empty Trash to reclaim the disk space.
Step 5 — Let macOS rebuild what it needs
On the first boot after clearing system caches, macOS may take slightly longer to reach the desktop — this is normal. Spotlight may reindex, and some apps will feel slower on their first launch as they rebuild their own caches. This is temporary.
What You Must Not Delete
- /System/Library/Caches — SIP-protected; attempting to delete contents here (even with SIP disabled) risks boot failure.
- /Library/Caches/com.apple.iconservices.store — Deleting this without a proper restart can cause blank icons across the entire Finder.
- ~/Library/Caches/CloudKit — iCloud sync state; removing it forces a full re-sync and can cause temporary data gaps.
- Any cache file currently open by a running process — macOS will write a corrupted replacement if you force-delete an in-use file.
The Easier Route: One-Click System Cache Cleanup
The manual steps above work, but they require Terminal access, administrator privileges, and knowing which subdirectories to skip. Crumb handles admin-protected system caches automatically — it uses the same elevated permissions but applies conservative heuristics to avoid touching protected paths like kernel extension caches or active CloudKit stores. Its one-click Clean mode covers system caches, user caches, logs, and purgeable System Data in a single pass, and it shows you exactly what will be removed before anything is deleted.
If you are ever unsure whether a specific folder inside /Library/Caches is safe to remove, Crumb's built-in "Is this safe to delete?" AI can explain what the folder is for and flag anything it considers risky. That check runs entirely on-device — no file contents leave your Mac.
You can download Crumb and run one free cleanup to see how much space the system caches are actually consuming before deciding whether to buy.
How Much Space Will You Recover?
Cache size varies enormously between machines. A Mac used primarily for development (with Xcode, npm, or Docker) can accumulate several gigabytes in ~/Library/Caches alone. A lightly used machine might see only a few hundred megabytes. The only honest answer is: check your own /Library/Caches directory size before deleting anything.
In Finder, select the /Library/Caches folder, press Command + I, and read the "Size" figure. Do the same for ~/Library/Caches. That tells you whether a cleanup is worth the effort.
How Often Should You Clear System Caches?
There is no universally correct interval. macOS is designed to manage its own caches — it evicts stale entries automatically, and on APFS volumes it can reclaim purgeable cache space without user intervention. Manual cache clearing is most useful when:
- An app is behaving strangely and you suspect a corrupted cache file.
- Your available disk space is critically low and macOS has not reclaimed purgeable space on its own.
- You are preparing a machine for sale or handoff and want a clean slate.
Running a full cache wipe every week is unnecessary and slightly counterproductive — you lose the performance benefit caches provide between cleanups.
Summary
Clearing the system cache on a Mac is straightforward when you know the boundaries: user caches in ~/Library/Caches are yours to delete freely, the admin-owned /Library/Caches is mostly safe with care, and the SIP-protected /System/Library/Caches is off-limits. Always restart before emptying Trash, and never delete files while they are in use. If you would rather not run sudo rm -rf manually, a tool like Crumb can handle the elevated-permission work safely, with a clear preview of what it will remove.