Categories

What each Caches category contains, and what usually recreates it.

Node.js

node_modules directories inside projects, reinstalled with npm, yarn or pnpm from the project's lockfile. Also node versions kept by nvm that nothing is using: the newest, the one nvm's own alias points at, and any version a running process is using are never offered. A version you do remove comes back with nvm install, so it is tier 2.

Python

Virtual environments, __pycache__, and the caches left by pytest, mypy, tox and ruff, all of which live beside a project and are recreated from its requirements. The uv download cache in ~/.cache/uv is shared by every project instead, so removing it costs a re-download rather than a rebuild — which is why it is tier 2 and the rest are tier 1. Python versions installed by pyenv are listed on the same terms as node versions: the newest, the one pyenv points at, and any version in use are held back.

Rust

target directories next to Cargo.toml. Rebuild them with cargo build.

Java/Kotlin

build, .gradle, and target directories next to Gradle or Maven project files. Rebuild them with the project's build command.

Xcode

DerivedData rebuilds on the next build. Device support and simulator runtimes can be downloaded again. Xcode Archives and simulator Devices may contain crash-symbol files, installed apps, and simulator data, so review those carefully.

Go

The Go build cache recompiles from local source. The module download cache can be fetched again when a project needs it.

Docker

Docker Desktop stores images and named volumes together in its data directory. Removing it can remove volume data as well as images.

Homebrew

Downloaded Homebrew packages and source archives. Homebrew downloads them again when an install or upgrade needs them.

Package Caches

Download caches for npm, pnpm, Cargo, Gradle, pip, Maven, NuGet, and similar tools. They can be fetched again, but removing them may slow the next build or install.

IDE & Editor

The VS Code and JetBrains caches rebuild on next launch. Workspace storage in Code/User/workspaceStorage is not a cache: it holds each project's editor state — open files, undo history, per-workspace extension data — which comes back empty rather than rebuilt, so it is tier 2. Installed extensions and JetBrains application support hold settings, keymaps and licences, which is why they are tier 3.

macOS Dev Caches

Xcode cache data can be recreated from the installed toolchain. Swift Package Manager cache data may need to download again.

Terraform

.terraform directories next to Terraform configuration. Restore them with terraform init.

Web Frameworks

Framework build output such as .next, .nuxt, and .angular. Rebuild it with the project's build or dev command.

Build Output

dist directories next to package.json. Rebuild them with the project's build script.

Game Engines

Export templates, derived data and store downloads kept by Godot, Unity and Unreal. A version's files are listed only when no editor of that version is installed. The engines themselves are not listed here; remove those from the Uninstall view.

App Caches

Per-app cache folders under ~/Library/Caches and app container caches. HTTPStorages may include website data such as cookies, so review that category before enabling it.

Browser Data

Browser caches can be downloaded again as you browse. Local storage, databases, and service workers may hold site data or sessions, so they are treated as destructive.

iOS Backups

Local iPhone and iPad backups. They may be the only copy of a device's data; DDCC cannot tell whether the same device is backed up elsewhere.

Saved App State

Saved application state used to reopen windows and documents after an app relaunch. Removing it resets that restore state.

Mail Downloads

Mail downloads and attachments stored locally. Some accounts can download them again; local-only mail may not.

System Caches

Cache data created by macOS services. User-owned caches can be rebuilt by the system. Root-owned caches are shown for information only.

Logs & Crashes

Diagnostic logs and crash reports. Removing them frees space but also removes history you may want for troubleshooting.

App Deep Clean

Known cache and support-data locations for specific apps. DDCC only lists paths it recognizes; nearby app data is left alone.