Is it safe to delete ~/Library/Caches on a Mac?
- Yes, app by app, with each app quit. Everything in it is a copy an app can make again: images and web content it already loaded, compiled code, package archives. Your documents, settings and passwords are kept elsewhere.
- What it costs you: a little speed for a while. Apps open and load more slowly until they’ve rebuilt what they use, and package managers download again what they need.
- Does it come back? Yes. It starts refilling as soon as you use your apps, so clearing it buys space for a while rather than for good.
- SiftMac’s verdict: Rebuilds
1. What it is
~/Library/Caches is the cache folder of your own user account. Each app gets a folder inside it, usually named after its app ID, such as com.spotify.client, or after the app or tool itself, like Homebrew or pip. What goes in is up to the app: thumbnails, web content, downloaded updates, compiled shaders, package archives.
Apple’s rule for developers is that this folder is for data an app can regenerate as needed, and that an app should never rely on a cache file being there. That rule is what makes it the safest large folder on a Mac to clear by hand.
- Browsers and chat apps keep pages, images and video they’ve already loaded.
- Package managers such as Homebrew, pip and Yarn keep the archives they downloaded, so the next install doesn’t fetch them again.
- Apps that update themselves often leave the downloaded update behind: Cursor’s ShipIt folder is one example.
2. Where it is
~/Library/Caches
The ~ stands for your home folder, so the full path is /Users/<you>/Library/Caches. Finder hides the Library folder: choose Go › Go to Folder (⇧⌘G), type the path and press Return.
Sandboxed apps, which includes most App Store apps, keep their caches inside their own container at ~/Library/Containers/<app ID>/Data/Library/Caches, so they don’t show up here. And /Library/Caches, without the ~, is a different folder with a different answer: the system-wide caches.
3. How big it gets
It depends entirely on the apps you use, so measure rather than guess. The first line gives the total, the second the biggest folders, largest last:
du -sh ~/Library/Caches
du -sh ~/Library/Caches/* 2>/dev/null | sort -h | tail -12
Folders that answer “Operation not permitted” are guarded by macOS, and are mostly Apple’s own. You don’t need to clear those, so there’s no reason to give Terminal extra access just for them.
4. How to delete it safely
- Find the big folders with the command above and work out which app each belongs to. The name usually tells you:
com.google.Chromeis Chrome,Homebrewis Homebrew. - Quit that app with
⌘Q, so nothing is writing to its cache while you clear it. - In Finder, open the app’s folder, select everything inside and move it to the Trash. Keep the folder itself, then empty the Trash.
The same in Terminal for one app, with it quit (put the real folder name in):
rm -rf ~/Library/Caches/com.example.app/*
Where a tool has a clean command of its own, use it instead, because it knows what it can drop: brew cleanup for Homebrew, pip cache purge for pip, yarn cache clean for Yarn. Don’t delete ~/Library/Caches itself, and don’t empty everything at once while apps are open.
5. What happens afterwards
- Apps take longer to open the first time and refill their folders as you use them.
- Websites, album art and previews load from the internet again, so the first visit to each is slower.
- Package managers download packages again the next time a project needs them.
- Nothing you made or chose is lost: your settings are in Preferences, and your apps’ data in Application Support.
- Don’t expect a faster Mac. Clearing caches frees space and can fix one misbehaving app, but apps are quickest with their caches in place.
6. Folders to leave alone in here
Leave the com.apple.… folders to macOS: many are guarded, so you couldn’t clear them anyway, and they belong to system services rather than to apps you can quit. If an Apple app misbehaves, a safe-mode startup is the supported way to reset system caches.
Questions
Can I delete everything in ~/Library/Caches at once?
You can, with every app quit, and nothing important is lost. It’s still better done app by app: you go after the big folders, and the apps you’re working in keep running at full speed.
Will deleting caches delete my files or logins?
Your files, no: documents, photos and settings aren’t stored in caches. Passwords are normally kept in the keychain or in the app’s own data, so they stay too. At most, an app downloads offline content again or takes a moment to rebuild previews.
Why is ~/Library/Caches so big?
Because a few apps cache a lot: browsers, music and video apps, apps that keep downloaded updates, and developer tools that hold on to everything they download. The du command above names them.
Is ~/Library/Caches the same as /Library/Caches?
No. The one without the ~ serves every account and the system itself, and it’s best left to macOS: what’s in /Library/Caches.
How SiftMac handles it. Its App caches category lists every folder in ~/Library/Caches by app, with its size, and clears what’s inside while keeping the folder. It skips Apple’s com.apple.… caches and a few system ones, leaves any folder whose app or program is running, checks that again right before cleaning, and marks package-manager caches such as Homebrew’s and pip’s as Rebuilds.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works