Reclaim gigabytes of forgotten code.
If you write code on a Mac, your biggest space hog isn’t your files. It’s the build artifacts scattered across every old project.
Updated October 2026 · 6 min read
What is eating your Mac’s storage?
When you check macOS storage, developer environments are usually grouped into a massive, unhelpful “System Data” block. CacheDrop specifically targets:
- Xcode DerivedData: intermediate build output and indexes
- Abandoned node_modules folders in old projects
- Docker images and build cache, plus Homebrew, npm and Yarn package caches
All three are rebuildable: your tools recreate them the next time you build or install. Deleting them frees disk space without touching your source code.
1. Xcode DerivedData
Xcode generates massive amounts of intermediate build information. CacheDrop safely clears ~/Library/Developer/Xcode/DerivedData without touching your actual code.
Delete DerivedData manually
Quit Xcode first, then run this in Terminal. You can also open Xcode › Settings › Locations, click the arrow next to Derived Data, and move the folders to the Trash.
With CacheDrop
CacheDrop shows DerivedData’s size under Developer caches and build files, so you can see it and clear it when you confirm.
2. Abandoned node_modules
You probably have dozens of old React or Node projects you haven’t touched in a year. Each node_modules folder can be 500MB+. CacheDrop finds them in the folders you choose and lets you pick which to drop.
Find and clear node_modules manually
List every node_modules folder under a directory with its size. Swap in the folder where you keep projects:
Delete the ones you don’t need with rm -rf path/to/project/node_modules. If you return to a project, npm install brings them back.
With CacheDrop
CacheDrop scans the folders you choose and lists each node_modules folder with its size, so you can pick the ones to drop. It skips projects you changed this week, and what you drop goes to the Trash.
3. Docker Caches & Package Managers
Clear out unused Docker images, Homebrew caches, .pub-cache, and npm leftovers that are quietly eating your SSD.
Clear Docker cache manually
This removes stopped containers, unused networks, dangling images and build cache. Add -a to also remove every image no container is using. Volumes are kept unless you add --volumes.
Package manager caches
| Tool | Cache location | Clear it with |
|---|---|---|
| Homebrew | ~/Library/Caches/Homebrew | brew cleanup --prune=all |
| npm | ~/.npm | npm cache clean --force |
| Dart / Flutter | ~/.pub-cache | dart pub cache clean |
With CacheDrop
CacheDrop groups the Docker, Homebrew and npm caches under Developer caches and build files, shows the total, and clears them together. No commands to remember.
Developer storage FAQ
Is it safe to delete Xcode DerivedData?
Yes. DerivedData holds build products, logs and indexes that Xcode recreates automatically. Your next build and code indexing will take longer once while Xcode rebuilds them.
Will deleting node_modules break my project?
No. As long as package.json and your lockfile are still there, npm install (or yarn or pnpm) restores the same dependencies.
Does docker system prune delete my volumes?
Not by default. Volumes are only removed when you add the --volumes flag.
Why does my Mac show developer files as “System Data”?
macOS Storage settings don’t break down caches inside your Library or project folders, so most developer build files are counted as System Data. A developer Mac cleaner like CacheDrop names each one and shows its size.
What does CacheDrop clean for developers?
Xcode DerivedData, old node_modules folders, unused Docker images and build cache, and Homebrew, npm and Yarn package caches. You review every item before it’s cleared.
Skip the Terminal.
CacheDrop finds DerivedData, node_modules and Docker caches in one scan. Free while in beta.
Download CacheDrop (Free)