Clean 50GB+ of Developer Caches on macOS in 60 Seconds

speed 1. The 60-Second Storage Reclamation Benchmark

Here is what typical disk reclamation looks like on an active developer MacBook after running the five cleanup steps outlined below:

Let's break down each step with the exact Terminal commands.

folder_delete 2. Step 1: Purge Orphaned node_modules (~30GB)

JavaScript dependency trees are notorious for consuming immense disk capacity. A single React or Next.js project's node_modules folder frequently weighs between 600MB and 2.5GB, containing over 50,000 loose files. If you have 25 legacy client projects, tutorials, or abandoned feature branches sitting in your ~/Projects directory, you are wasting 30GB to 50GB on duplicated code. (Read our deep dive: What is node_modules? Safe to Delete?)

1. Audit your largest node_modules folders

Before deleting anything, inspect where your heaviest JavaScript dependencies live:

find ~/Projects -name "node_modules" -type d -prune -exec du -sh {} + 2>/dev/null | sort -hr | head -n 10

2. Safely purge stale node_modules

To safely clean node_modules mac dependencies without disrupting projects you're actively working on, target folders whose parent directories have not been modified in the last 60 days:

find ~/Projects -name "node_modules" -type d -prune -mtime +60 -exec rm -rf {} +

💡 Tip: Deleting node_modules is non-destructive. If you return to an older project in the future, running npm install, pnpm install, or yarn will faithfully restore all dependencies in seconds based on your lockfile.

developer_mode 3. Step 2: Flush Xcode DerivedData (~20GB)

Whenever you compile an iOS, macOS, watchOS, or cross-platform Flutter/React Native application, Xcode writes intermediate compilation objects, index stores, and module maps into DerivedData. (See our complete guide on how to clear Xcode DerivedData.)

Xcode never purges old projects. If you compiled a test build six months ago, its 8GB compilation cache is still taking up space.

1. Wipe DerivedData

Run this one-liner to instantly clear all intermediate build artifacts:

rm -rf ~/Library/Developer/Xcode/DerivedData/*

2. Delete unavailable iOS simulators

When Xcode updates, old simulator runtimes and orphaned cache references linger:

xcrun simctl delete unavailable

Xcode will cleanly regenerate whatever indexes and symbols it needs when you next open your active workspace.

layers 4. Step 3: Prune Docker Containers (~15GB)

On macOS, Docker runs inside an APFS virtual disk image (Docker.raw). As you pull base images (such as Ubuntu, Node, Golang, or Postgres) and build multi-stage Dockerfiles, Docker Desktop's build cache and dangling layers expand rapidly. Learn more in our guide to clean Docker disk space on Mac.

1. Check Docker disk consumption

docker system df

2. Execute a full prune

Reclaim stopped containers, unused networks, untagged images, and build caches:

docker system prune -a --volumes --force

3. Clear BuildKit cache

Docker BuildKit preserves intermediate compilation layers for fast rebuilds:

docker builder prune -a --force

This immediately frees gigabytes within the Docker storage engine.

local_cafe 5. Step 4: Clear Homebrew Caches (~8GB)

Every time you execute brew install or brew upgrade, Homebrew downloads pre-compiled binary packages called "bottles" and stores them in your user cache: ~/Library/Caches/Homebrew. (Read our complete walkthrough: Clean Homebrew Cache on Mac.)

Unless you manually trigger cleanup, Homebrew keeps stale formula versions and outdated tarballs.

1. Clear stale packages and source downloads

brew cleanup -s

The -s flag strips download caches for all installed formulae and casks.

2. Flush raw Homebrew cache directory

rm -rf $(brew --cache)

Homebrew continues working flawlessly, and your local package cache is reset to zero bytes.

cached 6. Step 5: Flush CocoaPods/NPM/Yarn (~6GB)

Package managers keep local download caches so repeated installs don't hit remote registries. Over time, these global stores become bloated with outdated package tarballs.

1. Clean CocoaPods cache (iOS / React Native / Flutter)

pod cache clean --all

2. Clean NPM global cache

npm cache clean --force

3. Clean Yarn and PNPM global stores

# If using Yarn classic or Yarn Berry
yarn cache clean

# If using PNPM
pnpm store prune

terminal 7. The 60-Second Speed-Run Script

For developers who want to execute this maintenance routine in one shot, here is a combined shell script:

#!/usr/bin/env bash
echo "⚡ Cleaning developer caches..."

# 1. Clean Xcode DerivedData
rm -rf ~/Library/Developer/Xcode/DerivedData/*
xcrun simctl delete unavailable 2>/dev/null

# 2. Prune Docker (if running)
if command -v docker &> /dev/null && docker info &> /dev/null; then
  docker system prune -a --volumes --force
  docker builder prune -a --force
fi

# 3. Clean Homebrew
if command -v brew &> /dev/null; then
  brew cleanup -s
  rm -rf $(brew --cache)
fi

# 4. Clean Package Managers
command -v pod &> /dev/null && pod cache clean --all
command -v npm &> /dev/null && npm cache clean --force
command -v yarn &> /dev/null && yarn cache clean --all 2>/dev/null
command -v pnpm &> /dev/null && pnpm store prune 2>/dev/null

echo "✅ Dev caches flushed successfully!"