If you've ever opened ~/Library/Caches and seen gigabytes of folders staring back at you, you've probably asked the same question every Mac user eventually asks: is it safe to delete cache files on Mac? The honest answer is "it depends" — some caches are completely safe to trash, others will slow your Mac to a crawl or break apps if you remove them at the wrong time. This guide walks through every major cache type, what it does, what happens when you delete it, and where to draw the line.
What Are Cache Files, and Why Does macOS Create Them?
Caches are stored copies of data that was expensive to generate or fetch the first time. macOS and your apps use them to launch faster, render pages without re-downloading assets, and remember computation results. The tradeoff: they accumulate indefinitely unless something clears them. On a Mac used for a couple of years, the ~/Library/Caches folder alone can reach 10–30 GB, and the system-level caches under /Library/Caches and /private/var/folders can add several gigabytes more.
Not all of that is waste. Before deleting anything, it helps to know what each folder actually holds.
Cache Types: Safe, Risky, and Off-Limits
User App Caches — Generally Safe When the App Is Closed
Each app you install gets its own subfolder under ~/Library/Caches, named after its bundle identifier (e.g., com.apple.Safari, com.spotify.client). These folders hold thumbnail previews, downloaded assets, API response snapshots, and similar data that the app can regenerate on its own.
Side effects of deleting: The app will feel slower on its next launch and may re-download some content. Nothing breaks permanently. The critical rule: quit the app before deleting its cache folder. Deleting while the app is running can corrupt its internal state or cause a crash.
System Caches — Safe With Care
macOS stores system-level caches in two places:
/Library/Caches— system-wide caches shared across users (e.g., software update metadata, asset catalogs)/private/var/folders/…/C/— per-user temporary and cache files managed by the OS
Apple's own frameworks clean these automatically when storage pressure is high. Manually deleting from /Library/Caches is generally safe, but some subfolders (com.apple.aned, com.apple.iconservices) power system UI elements; clearing them can cause a brief icon-loading delay or force a Finder relaunch.
Side effects of deleting: First boot after deletion is slightly slower as caches are rebuilt. Icon cache clearing may temporarily show blank icons until the system regenerates them. A logout-and-login usually fixes cosmetic glitches.
Browser Caches — Completely Safe
Safari, Chrome, Firefox, and Arc all maintain disk caches for images, scripts, and stylesheets. These are intentionally designed to be ephemeral. Clearing them causes pages to reload all assets from the network on first visit, which means a brief slowdown on bandwidth-limited connections, and nothing else.
Each browser has a built-in "Clear Browsing Data" dialog — use that rather than deleting the folder directly, because the browser tracks cache size internally and manual deletion can confuse it momentarily.
Xcode Derived Data and Simulator Caches — Safe, but Large
If you're a developer, Xcode's derived data folder at ~/Library/Developer/Xcode/DerivedData can grow to tens of gigabytes. It contains compiled build artifacts, indexes, and simulator runtime images.
Side effects of deleting: Your next build will be a full clean build — potentially taking several minutes for a large project. Simulator apps will need to be re-installed. This is safe to do but choose a time when you're not about to demo something.
The simulator runtimes themselves live at ~/Library/Developer/CoreSimulator/Caches and can safely be pruned with:
xcrun simctl delete unavailableCoreData Persistent Stores — Do NOT Delete
Some apps store their actual user data inside ~/Library/Application Support or even inside a Caches-adjacent folder using CoreData SQLite files. These are not caches — they are your data. Deleting them means losing notes, app preferences, or saved state permanently.
The giveaway: files ending in .sqlite, .sqlite-wal, .sqlite-shm, or any folder named after an app that stores user-created content (like a task manager or writing app). If you are not certain, do not delete.
Font Caches — Safe, But Requires a Special Restart
macOS maintains a font cache that can occasionally cause rendering glitches (scrambled text, missing glyphs). It lives at /private/var/folders/…/com.apple.ATS. The correct way to clear it is to boot into Safe Mode (hold Shift at startup on Intel Macs; for Apple Silicon, shut down, hold power until "Loading startup options" appears, then hold Shift when selecting your volume). Safe Mode automatically purges the font cache and rebuilds it. Do not attempt to delete these files while the system is running.
A Quick-Reference Table
| Cache Type | Location | Safe to Delete? | Side Effect |
|---|---|---|---|
| User app caches | ~/Library/Caches |
Yes (app must be closed) | Slower first launch; content re-downloads |
| System caches | /Library/Caches |
Mostly yes | Slower first boot; possible icon flicker |
| Browser cache | Varies per browser | Yes | Slower page loads until cache rebuilds |
| Xcode DerivedData | ~/Library/Developer/Xcode/DerivedData |
Yes | Full clean build required next time |
| CoreData SQLite files | ~/Library/Application Support |
No — this is your data | Permanent data loss |
| Font caches | /private/var/folders/…/com.apple.ATS |
Only in Safe Mode | Glitches if deleted while running |
| Purgeable / System Data | Managed by macOS | Yes (let macOS handle it) | None — macOS reclaims automatically |
How to Clear Cache on Mac Manually
- Quit all apps whose caches you want to clear.
- Open Finder, press Cmd + Shift + G, and type
~/Library/Caches. - Identify the subfolder by its name (usually the app's bundle ID). If you don't recognize it, do not delete it yet.
- Move the folder to the Trash — do not permanently delete yet.
- Relaunch the app and confirm it behaves normally.
- Empty the Trash once you've verified nothing broke.
For system-level caches under /Library/Caches, repeat the same steps but authenticate with your administrator password when prompted.
If you want to clear the DNS cache (which lives separately from app caches), use:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderThe Biggest Risk: You Don't Always Know What a Folder Is
The manual approach works fine for folders you recognize. The dangerous moment is when you see an unfamiliar bundle ID consuming 4 GB and you're tempted to just delete it. Some of those folders belong to system services; others are legitimate app caches that happen to have cryptic names.
This is exactly where Crumb earns its keep. Its "Is this safe to delete?" AI reads the folder name, checks what process owns it, and gives you a plain-English removal-risk rating before you commit — on-device, without sending your file contents anywhere. It also handles the tedious parts automatically: closing apps before clearing their caches, skipping active CoreData stores, and correctly targeting the purgeable System Data blocks that Finder reports but won't let you delete manually. If you'd rather skip the manual steps entirely, you can download Crumb and run a one-click cleanup that applies all of the rules above by default.
One More Thing: Cleaning Is Permanent
macOS caches are not backed up by Time Machine by default (Time Machine excludes ~/Library/Caches). Once you empty the Trash, the files are gone. The data loss risk with true caches is low because apps regenerate them — but if you accidentally delete an Application Support folder or a CoreData store thinking it was a cache, you will not get it back from Time Machine. Move to Trash first, verify, then empty.
Conclusion
Clearing Mac cache files is safe for most user app and browser caches, moderately safe for system caches with a logout afterward, and genuinely risky for anything touching CoreData, font caches while the system is running, or folders you can't positively identify. The upside is real — gigabytes recovered, apps that feel snappier — but it requires knowing which folders you're looking at. Use the table above as your quick reference, follow the step-by-step process, and when in doubt, let a tool that understands macOS internals make the call for you.