Which Mac Caches Are Safe to Delete?

"Clear caches" is only a safe instruction after you can name what will rebuild them. A folder called Caches can hold thumbnails that come back in minutes, compiled artifacts that take an evening to recreate, or files that are not caches at all: chat history, local models, deployment keys, and Git-tracked project data.

This article is a decision guide for those boundaries, especially around browsers, chat apps, and AI tools. For the Library layout and measurement commands, start with how to clear cache on a Mac. For developer tool directories, see how to clear dev caches on a Mac. For AI install residue after uninstall, see AI tool leftovers on Mac.

The only definition that matters

A disposable cache is a replaceable copy of data that still exists elsewhere, or that the owner can regenerate from inputs you still have. If you cannot name the source, treat the folder as state or user data.

Apple's developer documentation draws a similar line: cache data should be regenerable; Application Support can hold resources the app needs to run.

Safe-leaning targets (still review them)

These categories are usually rebuildable, but "usually" is not a delete key:

• Browser cached images and files when you use the browser's own clearing UI and leave cookies, passwords, and site data alone.
• Thumbnail and icon caches after you accept a slower first browse of large folders.
• Package-manager download caches when the tools document a cleanup command (brew cleanup is the Homebrew example people actually mean).
• Rebuildable language/tool caches such as SwiftPM and Cargo artifacts when the project and toolchain are still present.
• App-specific CDN or media caches that the vendor labels as safe to remove inside its settings.

Even here, quit or pause the owner when the tool asks. Deleting an open cache database is how you get a "repaired" app that loses a week of offline state.

Keep by default

If a cleanup UI cannot promise these protections in writing, do not hand it a Select All.

AI and chat tools: clear the right slice

AI desktop apps and coding agents often mix four layers in one disk footprint:

1. CDN / HTTP caches – usually safe after review.
2. Conversation databases – user data.
3. Local models and embeddings – expensive voluntary downloads.
4. Tooling caches (indexers, Electron GPU caches, language servers) – often safe when the app is quit or when the cleaner can refresh in place.

Clearing (1) and (4) can reclaim space without erasing your work. Clearing (2) or (3) because a dashboard said "cache" is how people lose threads and re-download multi-gigabyte models by accident.

The same split applies to chat apps: stickers or proxy caches may be disposable; message databases and media libraries are not. Prefer in-app storage settings when they exist. Prefer a cleaner that keeps chats and media selected off by default when you use a third-party review list.

A five-question gate before any delete

1. Who owns this path (bundle id or documented tool)?
2. What exact source rebuilds it?
3. What does a miss cost (time, battery, network, offline access)?
4. Is the owner running, and does anything else have the files open?
5. Can you undo (Trash) or is the tool using permanent deletion?

Unknown answers mean keep. The goal is a short list with complete recovery stories, not a large number on a before/after screenshot.

Measure, then clear, then verify

du -sh ~/Library/Caches/* 2>/dev/null | sort -h | tail -20

Read from the bottom. Match each large child to an owner. After a cleanup:

• Relaunch the owner and confirm sign-in, recent projects, and chat history still behave.
• Run one representative task (build, browse, open the AI thread you care about).
• Check free space with the same tool you used before; APFS snapshots and purgeable space can make Finder disagree with du.

Do not chase System Data as if it were a folder. Apple's storage categories are summaries, not deletion targets (Mac storage).

Where Mole fits

Mole's Clean view is organized for review, not for maximum claimed bytes. It can clear rebuildable caches for browsers, chat apps, and AI tooling while keeping chat history, media, deployment keys, and Git-tracked files protected. Apps that are holding a cache can be quit from Clean so the list can refresh without a full rescan. Categories you mark Never Clean stay out of the way until you undo that choice. Slow folders are not allowed to stall the whole scan.

Use Mole when you want attributed candidates with protections already applied. Use the owner's own UI when the vendor documents a precise reset. Use neither when you cannot explain the rebuild path.

FAQ

Can I delete all of ~/Library/Caches?

No. It is a mixed neighborhood. Clear per owner after you can name a rebuild source, preferably through that owner's UI.

Will clearing caches speed up my Mac?

Sometimes a full disk slows indexing and scratch space, so reclaiming rebuildable caches helps storage pressure. It will not fix a CPU, thermal, or memory bottleneck, and the next miss may use CPU and network to rebuild.

Are AI model folders safe to delete?

Only if you accept re-downloading them. They are usually intentional offline assets, not accidental junk.

Does Mole delete chat history when cleaning WeChat or ChatGPT caches?

Mole's cleanup paths are written to keep chat history and similar personal data protected while offering rebuildable caches for review. Still read the on-screen selection before you confirm; never assume Select All is appropriate.