Xcode DerivedData cleaner
Clean Xcode DerivedData, archives, and simulator caches
Xcode can create gigabytes of DerivedData, build products, indexes, archives, and simulator files. Pare keeps those developer caches visible in your menu bar, then lets you clean the ones you choose without touching your source code.
Why Xcode DerivedData gets so large
DerivedData stores build artifacts, indexes, module caches, and intermediate files for Xcode projects. It is useful while you are actively building, but old project data often remains long after a branch, workspace, or simulator session is finished. That is why iOS and macOS developers often recover many gigabytes by clearing it.
Xcode cleanup targets Pare understands
Xcode DerivedData
~/Library/Developer/Xcode/DerivedData Xcode Archives
~/Library/Developer/Xcode/Archives CoreSimulator caches
~/Library/Developer/CoreSimulator/Caches Unavailable simulator runtimes
xcrun simctl delete unavailable Safer than ad hoc cleanup commands
Manual cleanup commands are easy to mistype and easy to forget. Pare keeps the scope explicit, shows the reclaimed size, and stays inside known user-level cache locations. You can review targets before cleaning and leave anything unchecked.
FAQ
Can Pare clean Xcode DerivedData?
Yes. Pare scans ~/Library/Developer/Xcode/DerivedData, shows reclaimable space, and lets you clean it from the menu bar.
Does Pare also clean simulator caches?
Yes. Pare includes CoreSimulator caches and unavailable simulator runtimes, which are common sources of wasted disk space for iOS developers.