How to Clear User Caches on a Mac (and What Actually Gets Deleted)
Quick answer: To clear user caches on a Mac, quit your apps, open Finder, press Shift-Command-G, go to ~/Library/Caches, and delete the contents of the folders you want to reset, not the Caches folder itself. Then empty the Trash. User caches are safe to remove because apps rebuild them, but clearing them frees space rather than permanently speeding up your Mac.
TL;DR
User caches live in ~/Library/Caches (plus a second, easy-to-miss location for sandboxed apps). Deleting them is generally safe. Apps rebuild what they need. The biggest wins are usually developer and package-manager caches (Homebrew, pip, npm, Xcode), not browser caches. Clearing caches won’t make a healthy Mac faster. It will reclaim space and can fix a misbehaving app. Local AI models are not caches, even when they sit in a folder called .cache. Treat them separately. The myth: “Clear your cache and your Mac will fly”
That isn’t how caches work. A cache is a store of data an app has already fetched or computed (thumbnails, web assets, downloaded package archives, compiled shaders) so it doesn’t have to do the work again. Deleting a cache forces that work to happen again. The first launch of Safari, Xcode, or Photos after a cache wipe is often slower, not faster.
So why clear caches at all? There are three legitimate reasons:
You’re low on disk space and caches have grown far past what’s reasonable. This happens most often with developer tools that never trim themselves. An app is misbehaving. Stale thumbnails, a web page that won’t refresh, or a crash on launch that started after an update can all come from a corrupted cache. Clearing that one app’s cache is a classic fix. Privacy. Caches can reveal what you’ve browsed, streamed, or opened.
If none of those apply, macOS’s own housekeeping is usually good enough. Keep that in mind and the rest of this guide is about doing it precisely rather than bluntly.
What is the user cache on a Mac?
The user cache is the per-account cache folder at ~/Library/Caches, where the ~ means your home folder. Every app you run as yourself can write here. It’s different from two other cache locations:
Location Who it belongs to Should you touch it? ~/Library/Caches Your user account Yes. This guide is about this one. /Library/Caches System-wide, shared by all users Rarely. Needs an admin password. /System/Library/Caches macOS itself No. It’s protected by System Integrity Protection, and macOS won’t let you modify it anyway.
There’s also a fourth location most guides miss.
The sandboxed-app blind spot
Apps from the Mac App Store, and many Apple apps, run in a sandbox. Their caches don’t go in ~/Library/Caches. They go inside the app’s container:
~/Library/Containers/
If you cleared ~/Library/Caches and an App Store app still looks bloated, this is why. Some apps from the same developer also share data through ~/Library/Group Containers/. Leave that folder alone unless you know exactly what you’re removing, because it often holds real data, not just cache.
A field guide to what’s actually in ~/Library/Caches
Open the folder and you’ll see dozens of subfolders, most named after apps in reverse-DNS style (com.company.app). Here’s what typically matters, grouped by how carefully to treat it.
Usually the biggest, and safe to clear Homebrew: downloaded bottles and source archives. This can reach several gigabytes on a dev machine. A better tool than deleting it by hand is brew cleanup –prune=all. pip: Python package downloads. Use pip cache purge. Yarn: the Yarn package cache. Note that npm keeps its cache elsewhere, in ~/.npm. Use npm cache clean –force for that one. com.apple.dt.Xcode: Xcode’s own cache. The truly huge Xcode folder is actually ~/Library/Developer/Xcode/DerivedData, which isn’t in Caches at all but is equally safe to clear when Xcode is closed. Google/Chrome, Firefox, com.microsoft.edgemac, etc.: browser web caches. They’re safe, but the browser simply refills them over the next few days of normal use. Safe, but expect side effects com.apple.Safari: deleting this works, but you may get “Operation not permitted” in Terminal because macOS protects some Apple folders. Safari’s own setting is cleaner. Enable Settings → Advanced → Show features for web developers, then choose Develop → Empty Caches. Music and streaming app caches (com.spotify.client and similar): cached audio gets re-downloaded, which matters on a metered connection. com.apple.QuickLook.thumbnailcache and similar thumbnail stores: Finder previews regenerate slowly the first time you browse a folder again. Think twice CloudKit and other iCloud-related caches: clearing them can trigger a re-sync of metadata. It’s harmless in principle, but it uses bandwidth and can make iCloud-backed apps briefly look empty. Anything for an app that’s currently running. Deleting files out from under an open app is how “safe” cache cleanups occasionally go wrong.
A good rule: delete the contents of a cache folder, not the folder itself. Some apps expect the folder to exist and handle a missing one badly.
Method 1: Clear user caches manually with Finder
This is free and built in, and it’s the right choice if you only need to do it occasionally.
Quit the apps whose caches you plan to clear. Use Command-Q, not just closing the window. In Finder, choose Go → Go to Folder… (Shift-Command-G). Type ~/Library/Caches and press Return. Switch to List view (Command-2), then choose View → Show View Options and tick Calculate all sizes. Sort by Size so the biggest offenders rise to the top. Open a large folder, select its contents (Command-A), and move them to the Trash (Command-Delete). Empty the Trash. Until you do, you haven’t freed a single byte. Restart if you cleared caches for system-level apps or Apple services.
Finder’s size calculation can take a while on a large Caches folder. Give it a minute before deciding nothing is big.
Method 2: Clear user caches with Terminal
Terminal is faster and more precise, and it lets you see sizes before you commit.
See what’s big first:
bash du -sh ~/Library/Caches/* 2>/dev/null | sort -hr | head -20
This lists your 20 largest cache folders, biggest first. The 2>/dev/null hides permission errors from protected Apple folders.
Check the sandboxed containers too:
bash du -sh ~/Library/Containers/*/Data/Library/Caches 2>/dev/null | sort -hr | head -10
Clear one app’s cache (contents only):
bash rm -rf ~/Library/Caches/com.example.app/*
Prefer the tool’s own cleanup command when one exists:
bash brew cleanup –prune=all pip cache purge npm cache clean –force
These commands know their own cache layout and won’t break anything the tool depends on.
A word on rm -rf ~/Library/Caches/*: it works, and most of the time nothing bad happens. But rm -rf bypasses the Trash, so there’s no undo, and a mistyped path is a real risk. Clearing targeted folders is safer and almost always gets you most of the space back.
Method 3: Clear user caches with MacSnip
MacSnip app is a free native macOS utility that lives in your menu bar and shows Mac health, disk usage, and cleanable caches in one panel. Its value over the manual methods is visibility. You see what’s using space before deciding what to remove, without remembering paths or du flags.
The typical flow:
Click the macsnip.app icon in the menu bar. Open the Clean section to see detected caches, grouped by app with their sizes . Review the list and deselect anything you’d rather keep, such as a streaming app’s cache if you’re on a metered connection . Confirm the cleanup.
Where MacSnip is especially useful is something generic cleaners tend to blur together: AI-model storage. If you run local models with Ollama, LM Studio, or Hugging Face libraries, those