Is It Safe to Clear Caches on a Mac?
Is it safe to clear caches on a Mac? Yes for most folders — here is what each one does and the few system ones to leave alone.

Is it safe to clear caches on a Mac? For almost every folder people mean when they ask, yes — "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.
How much space clearing caches actually frees
It depends entirely on what you have installed and how long you have used it. A Mac with a few browsers and chat apps might only reclaim a gigabyte or two from ~/Library/Caches; a developer's Mac with Xcode, several years of DerivedData, old simulator runtimes and a long-lived Docker install can reclaim tens of gigabytes in one pass. There is no universal number, which is why "is it safe to clear caches on a Mac" is usually the more useful question to answer first than "how much will I get back" — the safety is consistent even when the size isn't.
What to do if a cache folder refuses to shrink back down
Sometimes you clear a cache, the app rebuilds it within minutes, and the folder looks almost as large as before. That is not a sign something went wrong — it means the app genuinely needs that data for normal use (a browser re-caching the sites you visit daily, Spotify re-buffering the playlist you listen to every day). Clearing a cache trades disk space for a slower first use afterward; if you use the app constantly, the cache comes back because the app is doing its job, not because the clear failed.
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. Safari's cache (com.apple.Safari) falls under this same exclusion, which is why clearing Safari's cache has to go through Safari itself rather than a general cleanup tool.
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. There's a 7-day free trial with every feature unlocked and no card required, plans from $6.99/mo after. See how it works.
Frequently asked questions
Is it safe to clear caches on a Mac without backing anything up first?
Yes, for the folders this guide covers — ~/Library/Caches, developer caches like DerivedData, and ~/Library/Logs. Every one of them is data an app rebuilds on its own; none of it is a user file you created, so there is nothing to lose that the app itself won't regenerate.
Will clearing caches delete my saved passwords, photos or documents?
No. Caches are a separate category from the files you actually created or signed in with. Clearing ~/Library/Caches does not touch ~/Documents, ~/Pictures, browser-saved passwords (those live in the Keychain, not a cache folder) or any app's actual saved data.
Why does my cache folder fill back up right after I clear it?
Because the app needs that data to run normally and rebuilds it as you use it — a browser re-caching sites you visit daily, or Spotify re-buffering a playlist. That is the cache working as intended, not a sign the clear didn't work.
Does clearing caches speed up a slow Mac?
Sometimes, if an app's cache had grown pathologically large or corrupted, but it is mainly a storage fix, not a performance fix. A Mac that's slow from high CPU, not low storage, needs a different check — see macos 27 golden gate slow for that case.
Is it ever unsafe to clear a cache on a Mac?
Yes — the three folders this guide names as off-limits (/System/Library/Caches, the system-level /Library/Caches, and Apple's own com.apple.* caches under your user folder) can cause garbled app text, a forced iCloud re-sync, or require disabling macOS protections you shouldn't disable. Everything else covered here is safe.