How to Clear Cache on Mac (and When It's Actually Worth It)
Caches are not junk: they're the reason your Mac feels fast. Here's when clearing one fixes a real problem, which caches are safe to touch, and what you'll actually get back.
"Clear your cache" is tech support's favorite instruction, right up there with restarting the thing. It's also the most misunderstood cleanup on a Mac, because a cache is not junk. It's the reason your Mac feels fast: Safari keeps parts of every page you visit so it stops re-downloading the same logo, and apps store thumbnails so they don't rebuild them from scratch on every launch. Wipe all of it blindly and you don't get a faster Mac, you get a slower afternoon while everything rebuilds.
The real skill is knowing when clearing a cache fixes an actual problem, and which caches are safe to touch when it does. The useful clearing is easy to separate from the busywork once you know what each cache is for.
What a cache is doing on your Mac
A cache is a shortcut. Your browser downloads a page once, then keeps the pieces nearby so the next visit loads without a second trip. Your photo app builds a thumbnail once, then reuses it. Your code editor keeps compiled bits around so opening a project doesn't mean redoing work. In every case the trade is the same: a little disk space for a lot of saved time.
That trade only breaks down in two situations. First, the cache goes stale: a website updates its design but Safari shows you the old one, or an app update ships new artwork and you keep seeing the old icon. Second, the cache grows out of control: a cache that was supposed to hold a few hundred megabytes sits on several gigabytes, usually because an app keeps writing to it and never prunes it.
Both are real, and both have clean fixes.
When clearing a cache is the right fix
Clear a cache when something is visibly wrong, not as a routine tune-up. The symptoms that point at a cache:
- A page looks broken or outdated even after you reload, and you suspect you're seeing a saved copy.
- An app behaves oddly right after an update, as if it's still running on old data.
- You're chasing disk space and one cache folder is plainly the culprit.
For those, a targeted wipe is safe. For everything else, chasing caches is a bit like dusting: satisfying for a minute, and it doesn't change how the machine runs. A Mac that's genuinely slow is a different problem, and the last section says when cache clearing is the wrong tool.
Browser caches: the ones you'll actually clear
Browser caches are the most common source of stale-page weirdness, and they're the easiest to clear because the browser does it for you.
In Safari, open Settings, go to Privacy, and choose Manage Website Data. You can remove one site's data or hit Remove All. This is the fix when a site you use daily keeps serving you yesterday's layout. In Chrome, click the three-dot menu, choose Clear browsing data, tick Cached images and files, and clear. Firefox has the same under its history menu. None of this touches your passwords or bookmarks, which live separately.
You don't need to clear browser caches on a schedule. A browser holding a gigabyte of cache is not a problem. A browser showing you a broken page is. Clear for the symptom, not for sport.
App caches on your disk: the big ones
Every app on your Mac keeps its working files in a folder called Caches, inside your user Library. Open Finder, press Shift-Command-G, and paste in ~/Library/Caches to see the list. Every folder here belongs to an app, and the folder name usually matches.
Before deleting anything, look. Sort the folder by size, or use DiskBrew to see which cache folders are actually eating space. The apps with the biggest cache folders are usually the ones you use hardest: browsers, creative tools, video callers that store processed frames, and anything that generates previews.
When you've found a real hog, quit the app first, then move its cache folder to the Trash instead of deleting it outright. If the app misbehaves without its cache (it won't, but this is the safe way to find out), you can put the folder back. macOS and most apps recreate a missing cache automatically on next launch, which is also why you should never clear a cache while its app is running: a live app may be mid-write, and a half-written cache is the one kind that can cause a crash. If you're spring-cleaning more than caches, the leftover-files tour covers the other folders apps leave behind.
Two things I'd never do, even on a slow day: run a sudo command that empties system-wide cache folders, and pay a subscription for an app that does the same clicking for you. System caches exist for a reason and macOS manages them itself. And the cleaner apps that promise to speed up your Mac are mostly selling fear about the same folders you can check by hand in two minutes. DripCleaner, from the Espresso shelf, clears the common junk folders with one click if you want the convenience without the subscription, and it sticks to the safe list.
The cache footprint nobody talks about: Electron
Most cache guides skip the biggest caches on a modern Mac. Apps built on Electron, the framework behind many popular desktop apps, each bundle their own copy of a Chromium browser, and that means each one runs its own cache, GPU cache, code cache, and service-worker storage. Install ten of them and you're maintaining ten separate browser caches you never see, on top of the app's real data. The heavy ones quietly pile up past a gigabyte each.
A native Mac app keeps one small cache for its own UI, because it shares the system frameworks instead of shipping a browser. That difference shows up in the disk-space math and in the memory footprint, and it's the quiet reason this café only serves native apps. If you want to spot the Electron ones on your own machine, open ~/Library/Application Support: each keeps Code Cache, GPUCache, and Service Worker folders next to its real data.
When cache clearing won't fix it
To keep this honest: cache clearing fixes stale content and reclaims disk from runaway caches. It does not fix a slow Mac, a fan that won't shut up, or apps that beachball. Those have different causes and different fixes, covered in the guides on checking your RAM and diagnosing a slow Mac before you reinstall.
The café version
getapps.cafe runs on the idea that your Mac shouldn't need a monthly cleaning subscription any more than it needs a monthly cache tax. Every app on the menu is native, local-first, and light on disk, and the two utility apps for this job, DripCleaner for one-click junk clearing and DiskBrew for seeing what's really taking space, are included in the same subscription as the rest of the menu.
One subscription, the whole menu, and no app that nags you to buy a cleaner. Start your 7-day free trial and see what a native-only Mac feels like.