# Developer files: what SiftMac clears, and how it knows it comes back

Features · Updated 21 November 2026. By Mohit Nippanikar, who makes SiftMac.

## The short answer

- **Only stale, only rebuildable.** SiftMac lists packages and build folders in projects you haven’t changed for 3 months, and only when the file that recreates them, like `package.json` or `Cargo.toml`, sits next to them.
- **Xcode and Docker too:** DerivedData for projects that are gone or idle, old device symbols, unused simulators and, if you turn it on, Docker’s unused images and build cache.
- **Removed, not shelved:** these come back with your next install or build, so they’re deleted when you clean. None is ticked until you tick it.

## 1. How SiftMac finds them

SiftMac walks the visible folders in your home folder, up to 12 levels deep, skipping Library, Applications, Pictures, Music, Movies and Public. A folder holding `.git`, `package.json`, `Cargo.toml`, `Package.swift`, `Podfile`, `pyproject.toml`, `build.gradle`, `pubspec.yaml` or `requirements.txt` marks a project. In a monorepo the outermost project counts, so every package in it shares the repository’s activity. Toolchains that are git checkouts, like the Flutter SDK, are left alone.

| Folder | Listed when this is next to it | Comes back with |
| --- | --- | --- |
| `node_modules` | `package.json` | `npm install`, or yarn, pnpm or bun |
| `.next`, `.nuxt`, `.svelte-kit`, `.parcel-cache`, `.turbo`, `.angular` | `package.json` | the next build or dev run |
| `target` | `Cargo.toml` | the next Rust build |
| `.build` | `Package.swift` | the next `swift build` |
| `Pods` | `Podfile` | `pod install` |
| `build`, `.gradle` | `build.gradle` or `settings.gradle` (or their `.kts` versions) | the next Gradle build |
| `build`, `.dart_tool` | `pubspec.yaml` | the next Flutter build |
| a Python environment: any folder with `pyvenv.cfg` | `requirements*.txt`, `pyproject.toml`, `Pipfile`, `setup.py`, `environment.yml`, `uv.lock` or `poetry.lock` | `pip install` or `uv sync` |

A project counts as untouched when none of its own files has changed for 3 months (1 or 6 if you change it in **Settings › Developer files**). Build folders don’t count towards that, and neither do folder dates, which change when Finder merely writes a `.DS_Store`. Git’s index and HEAD do, so a commit or a checkout marks a project as active.

### Xcode

- **DerivedData** for a project whose workspace no longer exists, or that Xcode hasn’t opened for 3 months. Folders every project shares, like `ModuleCache.noindex`, stay.
- **Device support:** the debug symbols Xcode copies from each device, one folder per OS version. The newest for each platform stays; older ones unused for 3 months are listed.
- **Simulators** whose OS version is no longer installed, marked Safe, and ones not started for 3 months, marked Rebuilds. They’re deleted with `xcrun simctl delete`, the way Xcode does it. A booted simulator is In use.

### Docker, if you turn it on

With **Include Docker** on in Settings, SiftMac asks `docker system df` what Docker could give back, and lists unused images, build cache and stopped containers. They’re freed with Docker’s own commands, `docker image prune --all --force`, `docker builder prune --all --force` and `docker container prune --force`, which the panel on the right shows before you clean. Images and build cache come back with your next pull or build; stopped containers are marked You decide, since anything written inside them, outside a volume, goes with them. Volumes are never touched.

Package caches in `~/Library/Caches`, such as Homebrew’s, pip’s, uv’s, Yarn’s, pnpm’s, bun’s, CocoaPods’, Swift packages’, Go’s build cache, JetBrains’ and Playwright’s browsers, are listed with the other app caches, marked **Rebuilds**.

## 2. Why it waits for stale projects

On a developer’s Mac, many of the biggest folders are ones that come back: every project carries its own `node_modules` or virtual environment, every Xcode project its DerivedData, and old simulators and device symbols stay behind after you’ve moved on. Clearing them costs nothing but time, the next time you need them.

That cost is why SiftMac only lists projects you’ve left alone for months: clearing the build folder of today’s project would just make your next build slow. Requiring the recipe file next to each folder means nothing is listed that your usual install or build can’t make again. And checking for running programs means a server or script running from inside an environment keeps it.

## 3. What it doesn’t touch

- **Your code and its history.** Source files and `.git` folders are never listed.
- **Recently active projects,** however big their build folders.
- **Folders without their recipe.** A `node_modules` with no `package.json` beside it isn’t listed, since nothing would bring it back.
- **Docker volumes,** ever. Docker itself is off until you turn it on, and it has to be running for SiftMac to ask it anything.
- **Xcode Archives,** the builds you shipped, and global tool folders like `~/.npm`, `~/.gradle`, `~/.m2` and `~/.cargo` or nvm and pyenv versions. The space map explains them; their own tools clear them.
- **Projects in other places:** outside your home folder, inside Library, Pictures, Music, Movies or Public, or in Desktop, Documents and Downloads before SiftMac has Full Disk Access.
- **The Undo Shelf.** Developer files skip it because they come back with an install or a build. A simulator comes back only if you add it again in Xcode, and the apps and data on it go with it.

## Questions

### Will deleting node_modules break my project?

No. Running `npm install` (or yarn, pnpm or bun) in the project brings it back from `package.json`. SiftMac only lists a `node_modules` folder when that file sits next to it and the project hasn’t changed for 3 months.

### Why isn’t my project’s build folder listed?

The project changed recently, the file that recreates the folder isn’t next to it, a program is running from inside it, or the project lives somewhere SiftMac doesn’t look, like Library or outside your home folder.

### Does SiftMac delete Docker volumes?

Never. With Include Docker on, it lists unused images, build cache and stopped containers and frees them with Docker’s own prune commands. Volumes hold databases and other data, so they’re left alone.

### How does SiftMac remove a simulator?

With `xcrun simctl delete` and the simulator’s ID, the same way Xcode does it. You can add it again in Xcode under Devices and Simulators; the apps and data on it go with it.

## How SiftMac handles it

Developer files lists stale build folders, Python environments, Xcode data and, if you turn it on, Docker’s unused images and build cache, each with the project it belongs to and how it comes back. None is ticked until you tick it, and what you remove is deleted, since your next install or build makes it again.

Download: https://siftmac.com/SiftMac.dmg (scanning is free, and so is the first 2 GB of cleaning).

## Related

- [Xcode DerivedData, node_modules and Docker: what’s safe to delete on a developer’s Mac](https://siftmac.com/guides/developer-files-on-mac)
- [Is it safe to delete Xcode’s DerivedData folder?](https://siftmac.com/guides/xcode-deriveddata)
- [Is it safe to delete node_modules?](https://siftmac.com/safe-to-delete/node-modules)
- [Is it safe to delete Xcode simulators and CoreSimulator?](https://siftmac.com/safe-to-delete/xcode-simulators)
- [Is it safe to delete Docker.raw?](https://siftmac.com/safe-to-delete/docker-raw)

Canonical: https://siftmac.com/features/developer-files
