If your Mac is running slow or your storage reads "System Data" with an alarming number, you've probably ended up staring at ~/Library/Caches wondering if deleting it will fix things — or break everything. The short answer is: yes, you can delete the cache folder on Mac, but a blanket "select all, delete" is not the right move. This guide explains what caches actually are, which ones are safe to remove, which ones you should leave alone, and the correct step-by-step method to clear them without causing app headaches.
What Is the Mac Cache Folder?
Caches are files that apps and macOS write to disk so they don't have to recompute or re-download the same data twice. Your browser stores rendered pages. Xcode stores compiled build artifacts. Spotlight stores metadata indexes. Mail stores message previews. All of this ends up in one of three main locations:
~/Library/Caches— per-user app caches (the one you can most safely touch)/Library/Caches— system-wide caches shared across users (requires more care)/System/Library/Caches— macOS-managed caches (leave these alone)
The tilde (~) means your home folder. To open it directly in Finder, press Shift ⌘ G and paste ~/Library/Caches.
Is It Safe to Delete the Caches Folder on Mac?
For user-level caches in ~/Library/Caches, yes — in almost all cases. These files are designed to be regenerable. When you delete an app's cache subfolder, the app simply rebuilds it the next time it runs. You won't lose documents, settings, or personal data.
That said, there are genuine caveats worth understanding before you start deleting.
What happens after you delete a cache
- Apps may launch more slowly the first time after their cache is cleared, because they need to rebuild it from scratch.
- Some apps (notably browsers) will lose locally cached media, meaning pages load from the network rather than disk until the cache repopulates.
- A small number of apps store preferences or session data inside their cache folder — a design flaw, but it happens. Clearing those caches can reset app state or log you out.
Caches that are NOT safe to delete
| Location | What's in it | Safe to delete? |
|---|---|---|
/System/Library/Caches |
dyld shared library cache, kernel resources | No — macOS manages these; deleting can prevent boot |
~/Library/Caches/com.apple.Safari (cookies/WebSQL) |
Browser session state | Use Safari's built-in Clear History instead |
~/Library/Caches/CloudKit |
iCloud sync metadata | Risky — can trigger a full re-sync and temporary data gaps |
/Library/Caches/com.apple.iconservices* |
Icon rendering cache | Only with sudo after a reboot; not needed for routine cleaning |
~/Library/Caches/<any app running right now> |
Active app cache | Quit the app first; deleting while it's running can corrupt its cache |
The Right Way to Clear Mac Cache Safely (Step by Step)
Follow these steps to clear ~/Library/Caches without breaking anything.
- Quit all apps you plan to clean up. Deleting an app's cache while it's actively writing to it is a recipe for corruption. Quit browsers, creative tools, and any heavy apps before you start.
-
Open the user cache folder. In Finder, press Shift ⌘ G, type
~/Library/Caches, and press Return. -
Delete by app subfolder, not the entire folder. You will see folders named like
com.google.Chrome,com.spotify.client, orcom.apple.dt.Xcode. Select the specific folders you want to clear and move them to Trash. Do not select and delete theCachesfolder itself — macOS and some apps expect the parent folder to exist. - Identify what's safe using common sense. If the folder name clearly matches an app you recognize and can relaunch, it's safe. If you don't recognize a folder, look it up before deleting — or use a tool with built-in safety heuristics (see below).
- Empty the Trash. Until you empty Trash, the files are still consuming disk space.
- Relaunch your apps and verify. Open each app you cleaned and confirm it works normally. Most will open fine — just slightly slower on the first launch.
Clearing the system-level cache (optional, cautious)
The /Library/Caches folder (no tilde) is accessible with administrator privileges. You can inspect it from Terminal:
ls /Library/CachesMost of what you'll find here is managed by macOS services. Unless a specific folder is consuming an obviously unreasonable amount of space, there is no routine reason to touch this directory. If you do need to clear a specific entry, move it to Trash using Finder with admin authentication — don't delete system-managed entries blindly.
How Much Space Will Clearing Caches Actually Free?
It depends entirely on your usage patterns. On a developer machine with Xcode, derived data alone can accumulate tens of gigabytes. On a general-use machine, clearing caches might recover 2–10 GB. The storage that macOS labels "System Data" in Settings > General > Storage includes purgeable space — macOS will clear some of this automatically under memory pressure, but it doesn't always do so proactively.
If you want to see exactly what's consuming space before deleting anything, open Finder and press Cmd ⌘ I on individual cache subfolders to check their sizes — or use a disk visualizer to get the full picture at a glance.
Using Crumb's One-Click Clean (If You'd Rather Not Do This Manually)
The manual process above works, but it takes judgment and time. Crumb is a native macOS menu-bar app that handles this automatically: it identifies regenerable caches across system and user locations, skips the ones that are risky to remove (CloudKit, active app caches, system-managed entries), and clears the rest in one click. It also covers logs, temp files, and the purgeable "System Data" that manual Finder cleanup can't reach.
If you're ever unsure whether a specific folder is safe to delete, Crumb's built-in "Is this safe to delete?" feature explains exactly what a folder contains and what the removal risk is — without you having to Google every com.apple.* bundle ID.
You can download Crumb and run one free cleanup to see how much it recovers on your machine.
When Cache Clearing Won't Help (And What Will)
Caches are not always the culprit. If your Mac is running slow, consider these other causes before spending time on cache management:
- Too many Login Items. Check Settings > General > Login Items & Extensions.
- Large files, not caches. Duplicate media, old backups, and giant project archives are often far bigger than caches. Use a disk visualizer to find them.
- Insufficient RAM, not disk space. If you're hitting swap constantly, clearing 3 GB of caches won't meaningfully improve performance.
- Old app leftovers. Apps you deleted years ago often leave behind gigabytes of support files in
~/Library/Application Support— these don't appear in~/Library/Cachesat all.
Summary
Clearing the cache folder on Mac is safe for the user-level caches in ~/Library/Caches, provided you quit apps first, delete by subfolder rather than the parent, and leave system-managed caches alone. Caches regenerate automatically — you're not losing data, just forcing apps to rebuild their temporary files. The payoff varies by machine, but on a well-used Mac it's one of the few genuinely lossless ways to reclaim meaningful disk space. Do it manually when you want granular control, or let a purpose-built tool handle the judgment calls for you.