How to Clear Cache on Mac (and When It's Actually Worth It)

"Clear your cache" is the instruction tech support reaches for first, right up there with restarting the thing. It's also the most misunderstood cleanup on a Mac. A cache is the reason your machine 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 everything rebuilds, which makes for a slower afternoon rather than a faster Mac.

The useful part is knowing when clearing a cache fixes a real problem, and which folders are safe to touch when it does.

How to clear caches on a Mac

Three rules cover almost every case. If a website looks broken or is stuck on last month's design, clear that one site's browser data. If an app misbehaves right after an update, quit it and clear its folder inside ~/Library/Caches. If neither is true, leave it alone. A cache doing its job is invisible, and the space it holds is usually smaller than a single video file.

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. The trade is the same in every case: 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 and 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, and a folder meant to hold a few hundred megabytes is sitting on several gigabytes, usually because an app writes 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 one:

• 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 has a different problem, and the last section covers 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 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 serves 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 it touches your passwords or bookmarks, since those live separately.

You don't need to clear browser caches on a schedule. A browser holding a gigabyte of cache is fine. A browser showing you a broken page is the thing worth fixing, so clear for the symptom and not for sport.

App caches on your disk: the big ones

Every app 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. Each 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 biggest ones usually belong to the apps 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 recreates a missing cache automatically on the next launch, which is also why you shouldn't clear one 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 would never do, even on a slow day: run a sudo command that empties the 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 prunes them itself. DripCleaner, from the Espresso shelf, clears the common junk folders in one click if you want the convenience without the subscription, and it sticks to the safe list.

Which caches are safe to clear, and which to leave alone

Sort them into three piles and the cleanup stops being scary.

• Worth clearing: one browser's site data for a site that is misbehaving, and an app's own folder in ~/Library/Caches after you quit it. Both rebuild on the next launch.
• Safe but rarely worth it: the whole browser cache, and the cache folders of apps you open every day. Nothing breaks. You just pay the rebuild time for no gain.
• Leave alone: anything under /Library/Caches and /System/Library/Caches, and any command with sudo in front of it. Those belong to macOS.

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 browser caches you never see, on top of each 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 interface, 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. If you want to spot the Electron ones on your own machine, open ~/Library/Application Support: each one stores Code Cache, GPUCache, and Service Worker folders next to its real data.

When clearing a cache won't fix it

To keep this honest: clearing a cache fixes stale content and reclaims disk space from a runaway folder. It does not fix a slow Mac, a fan that won't shut up, or apps that beachball. Those have different causes, covered in the guides on checking your RAM, diagnosing a slow Mac before you reinstall, fan noise, and startup speed.

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 utilities for this job, DripCleaner for one-click junk clearing and DiskBrew for seeing what is really taking space, come with 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.