What is Cleaner for Xcode?
Cleaner for Xcode is a single-purpose cleaner for the files Xcode generates and never removes: derived data, build archives, simulator caches and support files for devices and SDKs you no longer use. The developer describes the point as making Xcode faster and saving disk space, and suggests running it weekly or monthly to keep the developer folder in shape. It is not a general Mac cleaner — everything it touches is inside the Xcode and developer folders — and it is meant to be run deliberately rather than left running in the background. The app is distributed on the Mac App Store and the source is published, so it can also be built locally.
Verified product facts
- Type
- developer utilityEditorially reviewed
- Platform
- macOS
- Pricing
- Open sourceDeveloper-stated
- Open source
- Yes
- Relationship to Nuanyue
- Third-party product — not published by NuanyueEditorially reviewed
- Current version
- 26.7.0Developer-stated
- Official website
- github.com/waylybaye/XcodeCleaner-SwiftUI
Last updated , last reviewed . Facts marked developer-stated come from the developer and are not independently confirmed; editorially reviewed marks a Nuanyue judgement.
Key features
What Cleaner for Xcode does at a glance.
Clears derived data, archives and other generated Xcode files
Analyses simulator caches and reports what they occupy
Reports deprecated and leftover files
In the developer folders
SwiftUI rewrite of the original XcodeCleaner
What you can use Cleaner for Xcode for
- Reclaiming disk space after a long run of iOS or macOS builds
- Clearing simulator caches that no longer match the installed Xcode
- Removing device support files for hardware and SDK versions you have moved past
Who is Cleaner for Xcode for?
- Developers who build with Xcode regularly and watch the disk fill up
- Anyone whose Mac has accumulated tens of gigabytes of derived data across several projects
Who is Cleaner for Xcode not for?
- Anyone looking for a general-purpose Mac cleaner — the scope is Xcode only
- People who want a cleaner that runs continuously in the background; this is a tool you open and run
Limitations
- Cleans only Xcode and developer-folder artefacts; caches from other applications are out of scope
- The source licence forbids redistributing binaries, so a modified build cannot be published on any binary-only channel
- Apple Silicon support is not stated in the sources Nuanyue tracks
Strengths and trade-offs
What Cleaner for Xcode does well, and what to weigh before choosing it. Points marked developer-stated come from the developer’s own material and have not been independently confirmed.
Strengths
- Targets generated and deprecated files in the Xcode and developer folders, which the developer presents as both a speed and a disk-space measure.Developer-stated
- Available on the Mac App Store as well as buildable from the published source, so it can be installed without compiling anything.
- The repository is actively maintained: the most recent commit at the time of writing was in July 2026.
- The interface reports simulator cache sizes rather than deleting them blind, so the space at stake is visible before anything is removed.Derived
Trade-offs
- The licence permits using and modifying the source but forbids redistributing binaries, so a fork cannot be shipped through any binary-only channel.Developer-stated
- Scope is limited to Xcode-related files; it will not reclaim space taken by caches from other applications.Derived
Overview
Xcode accumulates files it never cleans up. Derived data is rebuilt on every project and grows with each one; archives pile up per release; simulator caches and device-support files stay behind after the SDKs and hardware they belong to are gone. On a Mac used for development for a year, these routinely add up to tens of gigabytes, and none of it is removed by uninstalling a project.
Cleaner for Xcode scans those locations and removes what it finds. The developer’s framing is that clearing deprecated and leftover files both speeds Xcode up and recovers disk space, and the suggested cadence is weekly or monthly rather than continuous.
What It Covers
The scope is deliberately narrow. Everything the app touches sits inside the Xcode and developer folders — generated build output, archives, simulator caches, and support files for platforms and devices no longer in use. The interface reports what each category occupies, so the decision to delete is made with a size in front of it rather than blind.
That narrow scope is the point. A general cleaner has to know about every application on the machine and is judged on how safely it guesses; this one only has to understand Xcode’s own layout, which is a much smaller problem.
What It Does Not Do
It does not clean caches from other applications, and it is not a background service. There is no monitoring daemon and no scheduled sweep — you open it, review what it found, and run it.
It also does not touch your projects. What it removes is generated output, and the cost of removing it is the rebuild time to generate it again.
Who It Suits
Developers who build regularly and notice the disk filling without being able to say what filled it. If you have several Xcode projects and have never cleared derived data, the first run is usually the largest and the most convincing.
It is less useful if you build occasionally on a machine with ample free space — the accumulation is proportional to how much you compile.
Licensing
The source is published under a licence that permits use and modification, including for commercial purposes, on your own devices. It does not permit redistributing binaries, which means a modified build stays with you rather than being republished on the App Store or any other binary distribution channel.
Questions about Cleaner for Xcode
What kinds of files does Cleaner for Xcode remove?
The developer describes the target as unwanted and deprecated files in the developer folders, and the app reports simulator cache usage as one of the categories it analyses. It is not a general disk cleaner.Editorially reviewed
How often should it be run?
The developer suggests weekly or monthly. Running it more often mainly costs the rebuild time of whatever derived data it removes.Editorially reviewed
Can I build it myself instead of using the App Store?
Yes. The source is published and the repository documents building it by opening the Xcode project and running it. The licence allows this for your own devices; it does not allow redistributing the resulting binary.Editorially reviewed
Links
Sources
Facts on this page are checked against the sources below. Last updated , last reviewed .







