How to Clear Cache on Mac, and What Actually Happens When You Do

Clearing cache trades disk space for speed: cache is what makes the second load of a site or an app faster than the first, so removing it means those things rebuild from scratch once. It genuinely helps in two situations, a nearly full disk or an app misbehaving because of corrupted cache, and does almost nothing for general “my Mac feels slow” complaints. Knowing which case you’re in saves you from clearing cache that was doing useful work.

What a cache is for

A cache is a local copy of something your Mac already fetched or built once, so it doesn’t have to do that work again. A browser caches images and scripts so a site you revisit loads instantly instead of downloading the same logo and stylesheet every time. An app caches rendered data so it opens where you left off rather than rebuilding its interface on each launch. This is the system running well, not a leak to plug.

That’s why the reflex to clear cache “to keep things clean” usually backfires. An empty cache isn’t a faster Mac; it’s a Mac that has to rebuild everything on the next use. The right question is never “how do I clear cache regularly” but “do I have a specific reason to clear it right now.”

The three kinds of cache

Not all caches are the same, and they’re worth clearing under different conditions.

• Browser cache: stored assets from sites you’ve visited. Clearing it logs you out of some sites and makes the next visit reload everything, which is the fix when a page renders stale or shows an old version after an update.
• User and app caches: these live in ~/Library/Caches, one folder per app. This is where real space hides. Apps like Spotify, Slack, and Teams are classic multi-gigabyte offenders because they cache media and message data locally.
• System caches: the ones macOS builds for itself. Leave these alone. The system manages them, they’re small relative to app caches, and clearing them buys you nothing worth the risk.

Most of the time, when clearing cache actually matters, it’s the app caches in the second group you’re after.

How to clear it manually and safely

Start by quitting the app whose cache you want to clear. Clearing a cache while the app is running can corrupt the very data you’re trying to reset, and the app may just rewrite it anyway. With it closed, open Finder, choose Go > Go to Folder, and enter ~/Library/Caches.

Inside you’ll see folders named for each app, usually by bundle identifier, so Spotify’s cache shows up as something like com.spotify.client rather than a friendly name. Open the folder for the app you’re targeting and delete its contents, not the folder itself. Removing the enclosing folder occasionally confuses an app on next launch, whereas emptying it just prompts a clean rebuild. For a browser, skip the Finder entirely: Safari clears cache from its Develop menu or through Settings > Privacy, and other browsers keep the option under their privacy or history settings.

If you’d rather not go folder by folder, a review tool like BlueHammer Cleaner groups cache by app and shows sizes first, so you can see what you’re clearing before it’s gone. To understand how these caches fit into the larger storage picture, our explainer on what System Data means on a Mac covers where they sit.

When clearing actually helps

There are really only a few moments clearing cache is the right call. An app that started crashing or behaving strangely after an update is the strongest case — a corrupted cache is a common cause, and clearing it forces a clean rebuild. A single website showing an outdated layout is another; a browser cache clear fixes that in seconds.

The third is disk pressure. If your startup drive is under roughly 10 percent free, clearing large app caches can hand back several gigabytes and relieve the squeeze. That’s a real result — but it’s about the space, not about speed, and it’s part of a broader cleanup. If that’s your situation, work through freeing up space without removing files you need rather than just wiping caches.

Caches grow back, and that’s fine

After you clear a cache, it fills again as you use the app. That isn’t the cleanup failing — it’s the app doing exactly what it should, rebuilding the local data that makes it fast. A cache that returns to a few gigabytes is a sign of normal use, not a problem to attack every week.

So treat cache clearing as a targeted tool, not a maintenance habit. When an app acts up, a page goes stale, or the disk gets tight, it’s the right move. The rest of the time, the best thing you can do with your caches is leave them to do their job.