What Is the ~/Library/Caches Folder on Mac? A Plain-English Guide (2026)

If you have ever opened Disk Utility and wondered where dozens of gigabytes disappeared to, the answer is usually library caches mac — specifically the hidden folder at ~/Library/Caches. Most users never see it because macOS tucks it out of sight by default, yet it is routinely the single largest accumulation of data that an ordinary user can safely shrink.

What Is the ~/Library/Caches Folder?

Every macOS user account has a Library folder at /Users/your-name/Library/. Inside it, the Caches subfolder is where applications store temporary data they want to reuse across launches — but do not consider important enough to put in a recoverable location like iCloud Drive or a database backup.

Apple's design intention is clear: caches are disposable working storage. The operating system itself will occasionally purge parts of this folder under memory pressure, and a healthy app is required to function correctly even if its cache is wiped completely. In practice, many apps accumulate caches for months or years without ever cleaning up after themselves.

What Exactly Lives Inside ~/Library/Caches?

Open a Finder window, press Cmd + Shift + G, type ~/Library/Caches, and press Return. You will see a folder for almost every app and framework that has ever run under your account. Common residents include:

• Browser caches — Safari stores its page cache under ~/Library/Caches/com.apple.Safari/; Chrome maintains its own cache directory inside ~/Library/Caches/Google/Chrome/. These can each grow to several gigabytes on a machine used daily.
• Xcode derived data and simulator caches — Developers frequently find that ~/Library/Caches/com.apple.dt.Xcode/ alone exceeds 10–20 GB after a few months of active development.
• App Store and software update assets — macOS caches downloaded installers and update metadata in ~/Library/Caches/com.apple.appstore/ and related paths.
• Media and streaming caches — Music, Podcasts, and third-party video apps cache artwork, audio buffers, and download queues here.
• Framework and language runtime caches — Swift, Python (pip), npm, and other package managers write compiled module caches and downloaded package indexes into subfolders.
• Spotlight and index caches — Various subsystems write private index fragments that speed up searches.

The folders use reverse-domain-name identifiers (like com.company.appname), which makes them accurate but cryptic. Unless you know that com.apple.dt.Xcode means Xcode, connecting a folder to the app that created it requires guesswork.

Why Do Apps Use ~/Library/Caches?

Caching is a performance strategy. When an app has to render the same image, parse the same JSON response, or compile the same module repeatedly, storing the result locally means subsequent operations finish in milliseconds instead of seconds. Browsers are the clearest example: a cached copy of a website's stylesheet means it does not need to be downloaded again on the next visit.

The tradeoff is disk space. An app that aggressively caches can deliver noticeably faster performance, but each user session adds a little more data that may never be cleaned up. Over a year of use, the total easily reaches 5–20 GB on a typical developer or power-user machine.

Is It Safe to Delete ~/Library/Caches?

For most subfolders: yes, with a caveat. Because apps are required to rebuild their caches on demand, deleting them does not corrupt any app or cause data loss. The worst case is that the affected app runs more slowly the first time it launches after a clean, while it regenerates what it needs.

A few specific cautions apply:

• Do not delete while the app is running. An open app may be actively writing to its cache and could misbehave if the folder disappears mid-operation. Quit apps first.
• CloudKit and sync caches. Some folders under ~/Library/Caches/CloudKit/ are used by system sync processes. These are generally safe to delete, but macOS may take a few minutes to re-sync state afterward.
• Homebrew's cache. ~/Library/Caches/Homebrew/ holds downloaded package archives. Deleting it is safe; Homebrew will simply re-download archives on the next install. If you are on a metered connection, leave it.
• The deletion is permanent. There is no Undo and the files do not go to Trash by default when cleared programmatically. Be intentional about what you remove.

How to Check What Is Taking Up Space

You can get a quick summary from Terminal without deleting anything:

du -sh ~/Library/Caches/*/ | sort -rh | head -20

This lists the twenty largest cache subfolders in descending order. The output might look like:

14G    ~/Library/Caches/com.apple.dt.Xcode/
3.2G   ~/Library/Caches/Google/Chrome/
1.8G   ~/Library/Caches/com.apple.Safari/
...

Reading raw folder names is where most users get stuck. A folder called com.apple.dt.Xcode is Xcode; io.tailscale.ipn.macos is Tailscale — but dozens of others are genuinely opaque without research. Crumb solves this by labeling each subfolder with a plain-English app name in its Visualize view, so you see "Xcode" and "Google Chrome" rather than reverse-domain identifiers, and can immediately connect each entry to the gigabyte count beside it.

How to Clear ~/Library/Caches Manually

1. Quit all apps you want to clear caches for.
2. Open Finder, press Cmd + Shift + G, and enter ~/Library/Caches.
3. Identify the subfolder for the target app (use the du command above to find the largest ones).
4. Move specific subfolders to the Trash, or select everything inside and move it to the Trash if you want a full clear.
5. Empty the Trash.
6. Relaunch your apps.

A full manual clear of every subfolder in one pass is technically safe, but you will notice slower app launches for an hour or so while each app rebuilds what it needs. Targeting only the largest offenders — Xcode, browsers, and any media apps — is a more practical approach.

System Caches vs. User Caches: What Is the Difference?

The user-level folder at ~/Library/Caches is by far the most approachable. The system-level folders at /Library/Caches and especially /System/Library/Caches are managed more tightly by macOS and System Integrity Protection (SIP), and deleting the wrong thing there can briefly disrupt system services until they rebuild.

How Often Should You Clear Your Cache Folder?

There is no universal answer, but a reasonable rule of thumb for most users is once or twice a year, or whenever your available disk space drops below a comfortable buffer. Developers who build large Xcode projects may want to clean Xcode-specific caches monthly. Casual users who only browse the web and use productivity apps may never notice a meaningful problem.

If you want a one-step approach rather than manual folder hunting, download Crumb and use its Clean tab, which targets user caches alongside system logs and temporary files in a single pass — and shows you exactly what was removed and how much space was reclaimed.

Summary

The ~/Library/Caches folder is macOS's designated scratch space for app-generated temporary data. It is intentionally hidden from casual view, designed to be discardable, and is almost always the right place to look when you need to reclaim a meaningful amount of disk space without touching your actual files. Most of its contents are safe to delete with apps closed, the main cost being a brief slowdown while caches are rebuilt. Understanding what lives here — and which subfolders belong to which apps — is the first step toward keeping your Mac's storage genuinely tidy.