Mac disk cleanup for developers: every cache, what it costs to rebuild
Developer tools leave simulators, build output and package caches across your home folder. Here is where each one lives and what it costs to get back.
Developers
Xcode, Android Studio, Gradle, Homebrew, node_modules and other developer data that fills up a Mac.
Developer tools leave a lot behind: simulators, build products, package caches and toolchains. These articles cover where that data lives, what rebuilds on its own and what costs you time to recreate.
Start here
More in this topic
DevCleaner for Xcode alternatives
DevCleaner for Xcode is a focused tool. Here is how it compares with doing it by hand, with general Mac cleaners, and with DiskJoy, which is our product.
Final Cut Pro, Logic and Adobe caches: reclaim space from creative apps
Creative apps store large generated files next to your projects. Here is which ones the app can recreate, and which ones you should leave alone.
JetBrains IDE caches and old versions: what to delete
JetBrains IDEs keep data for each version you installed. Here are the folders to check and what each costs to recreate.
Cursor and VS Code eating disk space: workspaceStorage and state.vscdb
Editor data sits in a hidden Application Support folder. Here is what workspaceStorage and state.vscdb are, and how to check before you delete.
Go module cache: location, size and 'permission denied' when deleting
Go keeps downloaded modules in a read-only cache. Here is where it is, how to check it, and why plain deletion can fail.
Rust target folders and the Cargo cache: reclaim disk space
Rust build output is large and lives in each project. Here is how to see it, preview a clean, and what the Cargo cache in your home folder holds.
pip and conda caches on Mac: find and clear them
pip and conda both keep downloaded packages. Here is how to find the pip cache, what conda keeps, and what clearing costs.
npm, Yarn and pnpm caches: where they live and how to clean them
Each JavaScript package manager keeps its own download cache. Here is how to find each one and what clearing it costs.
Where is the .m2 folder on Mac and how to clean the Maven repository
The .m2 folder is a hidden folder in your home directory. Here is what is inside it, how to see its size and what is safe to remove.
CocoaPods and Carthage caches: location and cleanup
Both dependency tools keep downloaded copies on your Mac. Here is where they are, and what is safe to remove.
Where is the Swift Package Manager cache, and can you delete it?
Swift packages are cached in a few places depending on whether you use Xcode or the command line. Here is where, and what is safe to clear.
Simulator runtimes and CoreSimulator caches: reclaim tens of GB
Simulators can take tens of gigabytes. Here is the difference between runtimes and devices, and what you lose by removing each.
Find and delete every node_modules folder on your Mac
Each JavaScript project carries its own node_modules. Here is how to find them all, add up the size, and clear the ones you do not need.
Homebrew cache: where it is and how much brew cleanup frees
Homebrew keeps downloaded installers in one folder. Here is how to find it, preview a cleanup and understand why the number can be small.
Is it safe to delete ~/Library/Developer?
Do not delete the whole folder. Here is what each part holds, what is disposable, and what it costs to recreate.
Android Studio taking up too much space: SDK, emulators and AVDs
Android development spreads across several folders. Here is what each holds, how big it gets, and what removal costs.
How to clear the Gradle cache on Mac (and keep builds fast)
The .gradle folder grows with every project and Gradle version. Here is what is inside it, what to remove, and what to leave.
Cleaning up Xcode: DerivedData, device support and old simulators
Where Xcode keeps build data, what each folder is for, and what the next build costs after you clear it.