Buildshed
See where your Xcode build time goes, and get it back
Buildshed sits in your menu bar and reads every build Xcode finishes. It shows which targets, files, Swift functions and C++ headers eat the time, explains why an incremental build recompiled half your project, and tells you the moment a build gets slower.
Every Build, Automatically
Buildshed watches DerivedData and picks up every build as it finishes, whether from the Xcode app or xcodebuild. While a build runs, the menu bar shows a live timer against your usual time, then how the result compares.
Flame Graph & Timeline
A zoomable flame graph shows where the CPU time went, down to single Swift functions and C++ headers. The timeline lays every task out by target, with a concurrency strip that makes idle cores and serial stretches obvious.
Hotspots & Suggestions
Ranked lists of the slowest files, type-check-heavy Swift functions, expensive headers and templates, with who includes what. Suggestions point at the fixes that save the most time, and every row jumps straight to the line in Xcode.
Why Rebuilt
Changed one header and waited two minutes? Why Rebuilt shows which edit or header made each file recompile, using the compiler's own dependency data and the Swift driver's incremental reasoning.
Compare & Slowdown Alerts
Line up any two builds by target, file, function and header. Builds are tagged with their git commit, and a notification tells you when a clean build uses more CPU than usual or a single file suddenly takes twice as long.
One-Click Profiling
Turn on Swift function timing, rebuild explanations and C/C++ time traces for a project's Debug configuration in one click, and off again just as easily. Only those flags change; the rest of the project file stays byte-for-byte identical.
Private by Design
Everything is analysed on your Mac. No account, no uploads, no tracking. Free to use, with a one-time Pro unlock for compare, rebuild explanations, alerts, git tagging and AI export.