Cache & Junk

Developer Caches on Mac: What They Are and How to Clean Them

June 7, 2026·2 min read

The Developer Storage Problem

Developers face the worst storage problems on Mac. Xcode, Android Studio, Docker, Homebrew, npm and other tools generate caches that consume 50 GB or more. If wondering how to clean up mac as a developer, targeting these caches is your biggest opportunity.

Developer tools cache compiled code, downloaded dependencies, build artifacts, and simulator data. These speed up builds but grow endlessly. Most developers never clean them.

Xcode Caches and Data

Xcode is the biggest consumer for Apple developers. Derived Data at ~/Library/Developer/Xcode/DerivedData stores build products for every project ever opened. This folder alone can be 10 to 30 GB. Safely deletable since Xcode rebuilds what it needs.

iOS Simulator data at ~/Library/Developer/CoreSimulator/Devices stores full iOS version copies. Old simulators stay around. Delete unused ones through Xcode's Devices and Simulators. Essential for how to clean up mac as a developer.

Reclaim Mac finds and removes junk files automatically.

Android Studio Caches

Android Studio creates large cache directories. AVD folder at ~/.android/avd stores emulator disk images, 5 to 15 GB each. Delete old emulators through AVD Manager.

Gradle caches at ~/.gradle/caches store dependencies and build outputs, commonly 2 to 5 GB. Deletable and Gradle re-downloads when needed. The Android SDK might include old platform versions. Use SDK Manager to remove outdated components. How to clean up mac for Android developers.

Node.js and npm/yarn Caches

Every Node project creates node_modules with all dependencies. Multiple projects means duplicate packages. The npm cache at ~/.npm can grow to several gigabytes. Run npm cache clean --force.

Delete node_modules from inactive projects. Use Terminal to find all node_modules folders. This helps how to clean up mac by removing redundant dependency copies.

Docker and Container Caches

Docker stores images, containers, and volumes in its data directory. This can reach 20 to 50 GB for active users. Old images accumulate silently.

Run docker system prune -a to remove all unused images, containers, and networks. Add --volumes for unused volumes. Can recover 10 to 30 GB. Essential how to clean up mac step for Docker users.

Homebrew and Other Package Managers

Homebrew keeps old package versions. Run brew cleanup to remove old versions. Run brew autoremove for unneeded dependencies.

Python virtual environments, Ruby gems, Go modules, and Rust cargo caches all contribute. Check ~/.cargo, ~/go, ~/.gem. Delete caches for unused tools. Thorough how to clean up mac approach for developers.

Reclaim Mac

Clean your Mac in 60 seconds

Lifetime license. Offline. No subscription.

Frequently Asked Questions

Will deleting DerivedData break projects?

No. Xcode rebuilds when you next open a project. First build takes longer, subsequent builds are normal.

How much space can developers recover?

Commonly 20-60 GB from Xcode data, Docker images, node_modules, and package manager caches.

Should I clean regularly?

Monthly. Focus on Xcode DerivedData, Docker, and npm/yarn caches.

Safe to delete old iOS simulators?

Yes. Old runtimes take 3-5 GB each. Not needed unless actively testing those versions.

Keep Reading

Cache & Junk

How to Delete Xcode Derived Data and Free Up Space