I clear cache on my own Mac roughly once a month, and I test this exact process on a second machine every time I update this guide — most recently on macOS Tahoe 26. The steps below are what actually worked, plus a couple of things that didn’t work the way older guides claim they do.

What Cache Actually Is on a Mac (and Why It’s Safe to Delete)

Cache files are temporary copies your Mac keeps so it doesn’t have to redo work it’s already done — a thumbnail it already generated, a webpage element it already downloaded, a font it already rendered. None of it is a personal file. Delete it, and macOS or the app just rebuilds what it needs the next time you open something.

There are four cache locations worth knowing, and they behave differently:

One folder you should never touch: /System/Library/Caches. That’s Apple’s own protected system cache, and System Integrity Protection blocks normal deletion of most of it anyway — but don’t go looking for workarounds. It’s not where your slowdown is coming from.

Step 1: Clear Your User Cache (This Is the One That Matters Most)

This is the process from my own testing notes, refined slightly from what most guides show — I add a Get Info check first so you actually know what you’re clearing before you clear it.

1. Open a Finder window, then press Shift + Command + G to bring up the “Go to Folder” box. You can also click Go → Go to Folder from the menu bar.
2. Type ~/Library/Caches and press Return. The tilde matters — it points to your personal Library, not the system-wide one.
3. Check the size first (optional but smart). Right-click the Caches folder and choose Get Info to see how much space it’s actually using before you commit to clearing it.
4. Select everything with Command + A, or select individual app folders if you only want to target specific culprits like Spotify, Xcode, Slack, or a browser.
5. Move to Trash with Command + Delete, then empty the Trash from the Dock to actually reclaim the space.

One quirk worth flagging from testing: a handful of app cache folders (I’ve seen this with Adobe Creative Cloud and some Electron-based apps like Slack) will silently rebuild themselves the moment you relaunch the app, sometimes to nearly the same size within a day. That’s normal — it’s not a sign the deletion failed.

If a specific troubleshooting need brought you here rather than general cleanup — say your fan has been running loud and your system is overheating — cache buildup is rarely the root cause of thermal issues, so it’s worth ruling out airflow problems separately.

Step 2: Clear System Cache (Optional, and Only If You Know What You’re Doing)

System cache lives in /Library/Caches — no tilde — and it belongs to macOS itself rather than your user account, which is why it asks for your admin password. In my testing, clearing this rarely frees more than a few hundred megabytes, and it can make some background system processes rebuild their cache on the next boot, which briefly shows up as slightly higher CPU usage. It’s not dangerous, but it’s also not where your real space savings come from, so I only recommend it if you’re specifically troubleshooting a stuck system process.

1. Open Finder, press Shift + Command + G, and type /Library/Caches (no tilde this time).
2. Open individual com.apple.* folders and delete the files inside — never delete the folders themselves, only their contents.
3. Enter your admin password if prompted, then empty the Trash.

If you’re dealing with a Mac that’s freezing, kernel-panicking, or showing unusually high background activity, that’s more often a sign of a runaway process than stale cache — the diagnostic steps in our guide to tracking down high CPU usage from system processes apply the same troubleshooting logic even though it’s written from the Windows side.

Step 3: Clear Browser Cache Separately

Browser cache doesn’t live inside ~/Library/Caches in a way that’s safe to manually pick through — each browser manages it through its own settings, and using the built-in tool avoids accidentally breaking saved passwords or extensions.

Heads up: clearing browser cache through these menus usually clears cookies too if you select “all data,” which will sign you out of most sites. If you only want cache and not your saved logins, uncheck the cookies box specifically before confirming — Chrome and Firefox both let you deselect it.

Step 4: Flush the DNS Cache (For Connection Issues, Not Speed)

This one’s different from the others — it doesn’t free up storage, and it won’t make your Mac faster. Flush it when a website keeps loading an old version, resolves to the wrong server, or won’t connect after you’ve changed DNS settings or a hosts file entry.

Open Terminal (Applications → Utilities → Terminal), paste both lines one at a time, and enter your admin password when prompted — Terminal won’t show any characters or a cursor movement while you type it, which trips people up the first time. No output means it worked. This applies the same way on macOS Tahoe 26, Sequoia, and Sonoma.

The Built-In Alternative: Storage Management

If digging through folders feels risky, macOS has a safer built-in option that never touches personal files: go to → System Settings → General → Storage, and review the Recommendations section. It won’t clear app cache directly, but it surfaces old files, unused apps, and iCloud offload options that often free up more space than manual cache clearing anyway — and every action there is reversible or clearly labeled before you confirm it.

Manual vs. Storage Management vs. Third-Party Cleaner Apps

In my testing, manual clearing and Storage Management together cover nearly every case a normal user runs into. I only reach for a dedicated cleaner app on a Mac I’m setting up for someone else who won’t remember Terminal commands six months from now.

If overheating or fan noise is what actually triggered your slowdown rather than storage, our guide to safely cleaning laptop air vents covers the physical-maintenance side of that problem, and if your Mac’s trackpad or keyboard has been acting up separately, the troubleshooting approach in our MacBook double-typing fix walks through a similar process-of-elimination method.

FAQ

Will clearing cache delete my photos, documents, or app data?

No. Cache folders are completely separate from where your personal files and saved app data (documents, projects, saved games) live. As long as you stay inside ~/Library/Caches or /Library/Caches, nothing personal is at risk.

How often should I clear cache on a Mac?

Once a month for general maintenance is plenty for most people. Clear it sooner if you’re specifically troubleshooting an app that’s misbehaving, freezing, or showing an outdated page.

Why did my cache folder come back after I deleted it?

That’s expected. Apps rebuild their cache the next time you open them — it’s not a failed deletion. If a folder regrows to an unusually large size within a day or two, that’s often a sign the app itself has a caching bug worth reporting to its developer.

Does clearing cache actually speed up a Mac?

It can help if an app’s cache has become corrupted or bloated to the point it’s slowing that specific app down, and it reliably frees up storage space. But for general system speed, other factors — available RAM, startup items, and free disk space overall — usually matter more than cache size alone.

Is it safe to use Terminal’s rm -rf command to clear cache?

It works, but I don’t recommend it for most people. rm -rf deletes permanently, skipping the Trash safety net, and one misplaced space in the command can target the wrong folder. Moving files to Trash through Finder gives you a chance to recover if something goes wrong.

Conclusion

Clearing cache on a Mac is one of the lowest-risk maintenance tasks you can do, as long as you stay inside the right folders. Start with ~/Library/Caches for the biggest win, clear your browser cache separately through its own settings, and only touch system cache or DNS if you’re troubleshooting something specific. None of it puts your personal files anywhere near the Trash — and if a slowdown persists after all of this, it’s a sign to look at storage health or hardware rather than cache.