BeeClear guide
Review Mac Developer Caches Before Cleaning Them
Developer caches can use significant space while still belonging to an active project, lockfile, running process, or required toolchain. BeeClear checks usage and references before recommending cleanup.
How project and build caches are evaluated
BeeClear considers project manifests and lockfiles, developer-tool settings, running processes and working directories, recent source changes, and Git activity. Content that is active, referenced, or recently used or changed is retained.
Download caches are different from installed dependencies
npm, pnpm, and npx candidates are checked against indexes, project references, hard links, and tool configuration. Referenced dependencies, temporary tools still in use, and content whose rebuild state is uncertain are protected. Orphaned download caches remain optional and unselected by default.
Package managers, runtimes, and developer tools
Homebrew retains current installations, linked and pinned versions, and downloads still kept by its official metadata. Bun and Poetry protect expanded dependencies and virtual environments. Node, Python, and Rust runtimes are checked against defaults, project references, and running processes. Review the path and reason; size or age alone is not enough to judge a cache.
BeeClear for Mac by PangJiong
BeeClear scans and analyzes files locally. Scanning and reviewing results are free; cleaning access is a one-time purchase in the app.
View BeeClear and download the official PKG · About PangJiong