AI Mac CleanerIs it safe to clear caches on a Mac? What to clear and what to leave alone
Caches are the biggest safe win on a full Mac, but not every cache folder is equal. Here is what each one does, what happens after you clear it, and the three you should never touch.
"Clear your caches" is the first advice anyone gives for a full Mac, and it is good advice, with two caveats: not every folder called a cache behaves the same way, and a few of them are not yours to delete. This is the map.
What a cache actually is
A cache is data an app can rebuild. A browser keeps copies of images so pages load faster the second time. Spotify keeps the songs you played. Xcode keeps compiled pieces of your project so the next build is quick. If the cache disappears, the app works exactly as before; it just does the work again once. That is why clearing caches is safe by design, and also why the space tends to come back over a few weeks. Clearing caches is maintenance, not a one-time cure.
The user caches: safe to clear
~/Library/Caches is the folder that matters. Every app you run gets a subfolder named after its bundle identifier, such as com.spotify.client or com.google.Chrome. On the Macs we tested during development, this folder ranged from 2 GB to 14 GB, with browsers, chat apps, design tools and music apps at the top.
Two rules keep it painless:
- Quit the app first. An app that is running may be writing to its cache while you delete it, and at worst you get a crash or a corrupted preference. A cleaner that checks running processes, as AI Mac Cleaner does, skips those folders automatically.
- Expect a slower first launch. Chrome will re-download favicons, Spotify will re-buffer, Photos will regenerate thumbnails. Give it a minute.
Developer caches: safe, and usually huge
If you have Xcode installed, ~/Library/Developer/Xcode/DerivedData is almost always the single largest cache on the Mac. It is regenerated by the next build. Old iOS Device Support folders (debug symbols for iOS versions you no longer connect) and simulator caches are the same story. npm, Homebrew, pip and CocoaPods each keep a download cache too; they re-fetch what they need. Docker is the exception worth attention: its disk image only grows, and pruning it is done from Docker itself, not by deleting the file.
The three cache folders to leave alone
/System/Library/Cachesand anything under/System. Sealed by macOS. You cannot delete it without disabling protections, and you should not try./Library/Caches(the one without the tilde). Shared, system-level caches. Some are safe, but the risky ones live here too, including font caches that make every app open with garbled text until you restart. Leave it to macOS.~/Library/Caches/com.apple.*and the CloudKit and Photos caches inside your user folder. Apple's own apps keep state here that is not always rebuilt cleanly, and iCloud sync caches in particular can trigger a full re-sync if removed.
A good cleaner excludes all three by default. AI Mac Cleaner's Cleanup goes further and only offers direct children of your user cache folder, skipping Apple's, so there is no way to pick the wrong one by accident.
Logs, while you are there
~/Library/Logs is the other reliably safe folder: crash reports and app logs that only matter if you are debugging something today. It is rarely large, but it is never needed.
The honest summary
Clear your user caches and developer caches whenever the Mac is full; quit the apps first; leave the system and Apple folders alone; and expect to do it again in a month or two. That is the whole practice. If you would rather not think about it, Auto Clean in AI Mac Cleaner does exactly this on a schedule and skips anything that is in use.