What it looks for
Derived Data, Xcode archives and caches, device support, simulator artifacts, Swift Package and other recognized developer-tool caches or logs.
Scan first, review second, delete last. DevCleanr explains generated developer storage before selected items move to the Mac’s Trash.
On the App Store since July 2026
A developer-storage utility
DevCleanr is for Apple developers who can see Xcode and simulator storage growing but do not want a generic “cleaner” making opaque decisions. It scans explainable developer-owned artifacts, shows what they are, and waits for you to select what should move to Trash.
Derived Data, Xcode archives and caches, device support, simulator artifacts, Swift Package and other recognized developer-tool caches or logs.
Not a generic Mac optimizer, malware scanner, duplicate-photo finder, memory booster, or AI cleaner. It does not roam through personal folders or source projects looking for space.
Scan first
The Manage view turns a large storage number into inspectable rows. Search names, paths, or explanations; filter by category or safety; then choose individual items instead of accepting a single all-or-nothing cleanup button.

Understand the shape of the problem
Insights separates simulator artifacts, Derived Data, archives, logs, and caches so you can see where space is going. The readiness counts matter as much as the total: finding 60 GB does not mean all 60 GB should be removed.
DevCleanr uses neutral status language and local history because a developer utility should help you decide, not manufacture urgency.

Review second. Trash last.
A path can change after a scan. Selected items pass through the safety layer again immediately before cleanup. Protected roots, source directories, personal folders, and symlinks stay blocked rather than inheriting an old decision.
Allowed items move to the Mac’s Trash instead of being permanently erased. Xcode or a build tool may recreate generated data later, and moving an item can still interrupt active work, so DevCleanr surfaces tool availability before acting.
Useful before purchase
Maker note
I build enough Apple apps to know how quickly simulator and build artifacts grow—and how expensive an overconfident cleanup can be. DevCleanr is deliberately slower than a magic broom: it classifies, explains, waits, rechecks, and uses Trash. The professional standard is not the biggest reclaimed number. It is knowing what happened and being able to recover.
Daniel · solo developer behind Crafter AppsNo. Source directories and personal folders are outside the cleanup boundary. DevCleanr focuses on recognized generated developer storage and blocks protected paths and symlinks.
“Safe” means it passes DevCleanr’s current path and category checks as generated data. Removing generated data can still force Xcode, simulators, or package tools to rebuild or download it, so you should review selections and avoid cleaning during active work.
No. Eligible selected items move through macOS Trash. That keeps the action recoverable until you empty Trash yourself.
No. It is intentionally narrow: Xcode, simulator, and explainable developer-tool storage. It does not optimize memory, scan for malware, remove personal files, or promise to speed up the whole Mac.
From the same studio