Mac App Caches: Is It Safe to Clear ~/Library/Caches?
Low riskGeneral macOSUpdated
- Location
~/Library/Caches
- Risk level
- Low riskRebuilt automatically by macOS or the app that made it. Freshist selects these for you — you still see every item before anything moves.
- Selected by default
- Yes
- What Freshist does
- Moves the selected items to the Trash, so you can undo. Nothing is deleted outright.
- In the app
- Clean → App Caches — “Caches apps rebuild automatically — first launches may feel slightly slower.”
From Freshist's own cleaning rules — the same catalog the app uses.
What lives in ~/Library/Caches
Each app gets space in your user Library to store data it can regenerate. Apple's File System Programming Guide describes the Caches directory as the place for "app-specific support files that your app can re-create easily," and makes each app responsible for managing what it keeps there.
Inside, most folders are named after an app's bundle ID, such as com.apple.Safari or com.spotify.client, or after the developer. Typical contents:
- Image and thumbnail caches
- Web content (many apps embed web views)
- Downloaded updates and installers
- Offline audio or video for streaming apps
- Compiled shader or code caches for games and editors
- Logs some apps write here instead of in
~/Library/Logs
Sandboxed apps, including most Mac App Store apps, keep their caches inside their own container in ~/Library/Containers instead, so they don't show up here. Some developer tools do use subfolders here: the Homebrew, Go, CocoaPods and Composer caches all live under ~/Library/Caches.
Why the folder keeps growing
macOS doesn't cap the folder size. Each app decides how much to keep, and many never trim their own cache. Streaming apps can hold gigabytes of offline media, chat apps keep every image you've scrolled past, and apps you deleted months ago leave their cache folders behind, because dragging an app to the Trash doesn't touch its Library files. Uninstalling apps completely covers that side.
What happens if you clear it
| Effect | How long it lasts |
|---|---|
| Slower first launch while an app rebuilds its cache | One launch, sometimes a few |
| Thumbnails, previews and artwork reloaded | Until the app has seen the items again |
| Re-downloaded content (offline media, updates) | Until you download it again |
| Documents, settings, passwords | Not affected; they live elsewhere |
There are exceptions. An app that stores offline-only content here (for example downloaded playlists) loses that copy and needs to download it again. That breaks Apple's guideline, but it happens.
Find the biggest app caches
du -sh ~/Library/Caches
du -sh ~/Library/Caches/* 2>/dev/null | sort -h | tail -20
The second command lists the 20 largest app caches. Some folders, such as Safari's, are protected by macOS privacy controls and show as unreadable unless Terminal has Full Disk Access. In Finder, choose Go → Go to Folder… and enter ~/Library/Caches.
Clear it the safe way
- Check whether the app has its own option first. Many apps (browsers, chat apps, music apps) have a "clear cache" or storage setting that does the job without guessing.
- Quit the app whose cache you're clearing. Deleting files an app has open can corrupt its cache and confuse it.
- In Finder, open
~/Library/Caches, select that app's folder, and move it to the Trash. - Open the app and check that it works, then empty the Trash.
Work app by app rather than selecting everything. Clearing the whole folder at once affects system services as well as apps, and you gain little: most caches come straight back.
Caches worth leaving alone
Leave a cache alone when the app is mid-download or mid-sync, when you're about to go offline and rely on cached content, or when the folder is small. The library-level view of the same folder is in ~/Library/Caches explained, and the safety page explains what Freshist refuses to touch.
Sources
Frequently asked questions
Should I delete the Caches folder itself?
No. Delete the contents, or better, specific app folders inside it. The folder is expected to exist, and removing it can cause permission errors for apps and system services until macOS recreates it.
Will I be logged out of apps?
Usually not. Passwords and login tokens belong in the keychain, and settings in Preferences or Application Support. A few apps cache account data here, so expect an occasional extra sign-in or a re-sync rather than lost data.
Why does the folder fill up again so fast?
Because apps are doing what caches are for. Browsers, messaging apps, music and video streaming apps cache aggressively and rebuild within days of normal use. Clearing helps most when a cache belongs to an app you no longer use.