SiftMac
Who it’s for · Updated 21 November 2026

What fills a developer’s Mac, and what’s safe to delete

By Mohit Nippanikar, who makes SiftMac

The short answer
On this page
  1. What fills a developer’s Mac
  2. What’s safe to clear, and what to keep
  3. How SiftMac helps a developer
  4. A cleanup routine for a developer’s Mac
  5. Questions

1. What fills a developer’s Mac

Every language keeps its own folders, scattered through your home folder rather than in one place, and most of them are hidden. These are the usual ones, with whether they come back:

WhatWhere it livesComes back?More
Packages and build output in old projectsnode_modules, .venv, target, build, .gradle inside each projectYes, with the project’s install or buildnode_modules, Rust target
Homebrew downloads and old versions~/Library/Caches/HomebrewYes, downloaded again when neededHomebrew cache
Rust crates~/.cargo/registryYes, downloaded againCargo registry
Go modules and build cache~/go/pkg/mod, ~/Library/Caches/go-buildYesGo caches
Gradle and Maven dependencies~/.gradle/caches, ~/.m2/repositoryYes, on the next buildGradle, Maven
IDE caches and logs~/Library/Caches/JetBrains, VS Code’s cache foldersYesJetBrains, VS Code
Docker images, containers and volumesOne disk image, Docker.rawImages pull again; volumes don’tDocker.raw
Virtual machines~/Parallels, or UTM’s own folderNo: each holds a whole systemParallels, UTM
Old language versions~/.nvm, ~/.pyenv, ~/.rustupOnly by installing them again—
Android SDK and emulators~/Library/Android/sdk, ~/.android/avdDownloaded again in Android StudioAndroid SDK, emulators
Repositories you cloned onceAnywhere, each with its .git folderOnly from the remote.git folders

Measure before you delete. This lists the shared caches and toolchains, biggest last; folders you don’t have are skipped:

du -sh ~/Library/Caches/Homebrew ~/.cargo ~/go/pkg/mod ~/Library/Caches/go-build ~/.gradle ~/.m2 ~/Library/Caches/JetBrains ~/.nvm ~/.pyenv ~/.rustup ~/Parallels 2>/dev/null | sort -h

Build folders hide inside projects. For Rust’s target folders, for example (change ~/code to wherever you keep projects):

find ~/code -name target -type d -prune -exec du -sh {} + 2>/dev/null | sort -h | tail -20

If most of your work is one stack, there’s a closer page: iOS and Mac developers for Xcode, web developers for Node and Docker, AI developers for local models and coding agents, and data scientists for conda, notebooks and datasets.

2. What’s safe to clear, and what to keep

Clear with each tool’s own command

Delete by hand, in projects you’ve finished

Dependency and build folders in a project you haven’t touched for months are the safe bulk: target, build, .gradle, node_modules, .venv. Check first that the file that rebuilds each one is still there (Cargo.toml, build.gradle, package.json with its lockfile, requirements.txt or pyproject.toml), because that file is how it comes back.

Keep, or think twice

3. How SiftMac helps a developer

SiftMac’s developer files walk the folders in your home folder looking for projects. They list build folders and packages only in projects you haven’t changed for 1, 3 or 6 months (3 by default), and only when the file that rebuilds them sits next to them: Cargo.toml for target, a Gradle build or settings file for build and .gradle, Package.swift for .build, Podfile for Pods, pubspec.yaml for Flutter, package.json for node_modules, and a requirements file or pyproject.toml for a Python environment.

What it leaves to you: ~/.cargo, ~/go, ~/.gradle, ~/.m2, ~/.npm, ~/.nvm, language versions and virtual machines. SiftMac doesn’t clean those. The space map shows how big each one is, with a plain note on the folders it knows, so you can clear them with the commands above.

4. A cleanup routine for a developer’s Mac

  1. Push your work, and note the projects you’re in this month. Those are off limits today.
  2. Measure with the commands above, or open the space map, and write down the three biggest things.
  3. Clear shared caches with their own commands: brew cleanup, go clean -modcache, and the npm or pip equivalents if you use them.
  4. In finished projects, run each one’s own clean (cargo clean, ./gradlew clean, flutter clean) or delete its dependency folders.
  5. Remove language versions and toolchains nothing uses, with nvm, pyenv or rustup.
  6. If you use Docker, docker system df shows what’s reclaimable and docker system prune frees stopped containers, unused networks, dangling images and build cache. Leave volumes unless you know what’s in them.
  7. Empty the Trash and measure again. Repeat when you finish a project, or when the disk-full forecast says you’re a few weeks from full.

Questions

Is it safe to delete ~/Library/Developer or ~/.cache all at once?

Not in one go. Both hold a mix: ~/Library/Developer has simulators with app data and Xcode archives you may need, and ~/.cache can hold downloaded models next to tool caches. Clear them piece by piece, with each tool’s own command.

Will deleting build folders break my projects?

No, as long as the file that describes the build is still there: Cargo.toml, build.gradle, package.json with its lockfile. The next build or install recreates the folder; it just takes longer the first time.

Can I keep caches somewhere other than the internal disk?

Several tools let you choose: HOMEBREW_CACHE for Homebrew, GOCACHE for Go’s build cache and GRADLE_USER_HOME for Gradle, and Docker Desktop can move its disk image in its Resources settings. Point them at an external SSD that stays connected.

Does SiftMac delete anything in a project I’m working on?

No. Build folders are listed only in projects unchanged for the period you pick, at least a month, and only where the file that rebuilds them is present. Nothing is ticked until you tick it.

How SiftMac handles it. SiftMac lists build folders and packages only in projects you haven’t changed for months and only where the file that rebuilds them is present, skips anything a running program uses, and frees Docker space only through Docker’s own prune commands when you turn that on.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works