Is it safe to delete cache files on Mac?

Is it safe to delete cache on Mac? Short answer: mostly yes, for the user caches in ~/Library/Caches. Those are disposable by design: macOS and the apps that made them rebuild them the next time they run. The only cost is a slightly slower first load. The one folder to leave alone is /System/Library/Caches, and the one catch is that clearing caches rarely stays cleared.

What a cache actually is

A cache is a local copy of data an app or the OS expects to reuse, kept so it doesn't have to fetch or recompute it every time. Your browser caches website assets so revisited pages load instantly. Apps cache thumbnails, search indexes, downloaded resources, and compiled artifacts. It's a deliberate trade: disk space for speed.

That framing is the whole answer to whether deleting them is safe. A cache is not your data; it's a shortcut to your data or to work already done. Delete the shortcut and the app takes the long way once, then rebuilds it. Caches are also a big reason your Mac hides so much space; for the wider picture, see hidden storage on Mac.

Which caches are safe to delete on a Mac

Per-user application caches live in ~/Library/Caches, one subfolder per app. These are generally safe to clear:

• macOS treats them as disposable. When space runs low, macOS itself clears caches and logs it considers safe to delete: temporary database files, interrupted downloads, staged updates, Safari website data, and more.
• Apps rebuild them on next launch. Reopen the app and it re-fetches or recomputes what it needs.
• The only immediate cost is a slower first load while the cache repopulates.

The best candidates are apps you've stopped using: their caches sit there taking up space with no upside. Clearing those is a clean win.

Which caches to leave alone

Two folders and one edge case deserve a wide berth.

• /System/Library/Caches: OS-managed. Don't hand-delete these. The intended way to clear system caches is to boot into Safe Mode: macOS clears certain system caches and then automatically recreates them as needed. Apple documents this as a legitimate step when a task needs temporary room. See Apple's Free up storage space on Mac.
• /Library/Caches (system-wide, no ~): shared caches you generally shouldn't touch either.
• Apps that misuse the Caches folder. Some apps store real, non-disposable state there instead of in Application Support. Blanket-nuking every cache folder can lose that state. So don't mass-delete the caches of apps you actively rely on; clear them one at a time, and only when you have a reason to.

The honest catch: caches come back

Here's the part cleaner apps skip. The gains are temporary. A cache exists to make things fast; clear it and the app rebuilds it the next time you use it. So clearing caches constantly is a treadmill, not a speed-up. You pay a slower first load, reclaim some space, and then the space fills right back in as you keep working.

Two things follow from that. First, clearing caches won't make your Mac faster in any lasting way; if anything the next launch is slower. Second, because macOS already frees safe-to-delete caches on demand, routinely scrubbing them by hand is low-value maintenance. Do it to reclaim space from apps you no longer use, not as a weekly ritual. (This is also why a lot of "System Data" is just caches waiting to rebuild; more on that in what System Data is on Mac.)

How to clear a cache safely

If you do want to reclaim the space, here's the careful way.

1. Reveal the folder. ~/Library is hidden by default. In Finder, open the Go menu, hold down the Option key, and Library appears in the list; open it, then open Caches. Or, from Terminal:

open ~/Library/Caches

2. Find the big ones. No point deleting a 4 MB folder. List cache subfolders by size, largest first:

du -sh ~/Library/Caches/* | sort -rh | head

Some app caches can reach several gigabytes; most are tiny. Target the big ones for apps you don't use.

3. Quit the app first, then clear its cache. Deleting a running app's cache can confuse it or corrupt state. Fully quit the app, then delete the files inside that app's cache subfolder, not the subfolder itself. Some apps expect their cache folder to exist and get grumpy if it's gone. Empty it; don't remove it.

For the broader "what's actually safe to remove" rundown beyond caches, see what you can safely delete on Mac.

The short version

User caches in ~/Library/Caches are safe to delete; they rebuild, and the only cost is a slower first load. Leave /System/Library/Caches to macOS (Safe Mode if you must), skip apps that hide real data in Caches, and remember the wins are temporary. It's a space reclaim, not a performance fix.

Doing this by hand means unhiding a folder, telling disposable caches apart from apps that abuse the folder, and quitting each app before you touch it. Plumby clears only the caches that are actually safe, shows you the exact path for each before it moves anything, and lets you send what it clears to the Trash rather than delete it, in case you change your mind. When a cache is just going to rebuild on next launch, it tells you, so the number it reports is real, not padded.