Protect project work
Free Xcode disk space without deleting projects
Low disk space can make broad cleanup advice feel urgent. The safer response is classification: identify generated storage, protect evidence, and act on only a narrow reviewed subset.
The bounded answer
Start with diagnosis, not deletion. BuildSweep does not scan project source trees and does not permanently delete or empty Finder's Trash. Its first release only makes two exact DerivedData leaves actionable.
A safer review sequence
- 1Use the manual planner below to understand the shape of storage you already measured.
- 2Treat Archives, SourcePackages, simulators, and test-result bundles as protected review categories.
- 3Use BuildSweep to diagnose supported DerivedData locally.
- 4Review the frozen plan and decide separately when to empty Finder's Trash.
Check the storage shape locally
Use the manual planner without sharing paths, project names, inventories, or exact values with VaultDevLabs.
Open the Xcode storage planner →Primary references and product boundary
- Apple: Running tests and interpreting results
- Apple: Distributing apps for beta testing and releases
- Apple: Managing files and folders in an Xcode project
Apple documents Xcode archives, test-result bundles, and project-file operations. The exact two-leaf action boundary described here is BuildSweep 1.0's deliberately narrower product policy, not a claim that Apple designates every DerivedData item as safe to remove.
Diagnose before you move anything
BuildSweep reviews supported Xcode-generated storage locally and requires an exact frozen plan before selected leaves move to Finder's Trash.
View BuildSweep in the Mac App Store