Storage clarity for macOS developers

Know where your developer disk space went.

ExactDisk understands your projects, toolchains and generated artifacts—then explains what may be reclaimed, what can be rebuilt, and what should stay put.

ExactDisk for macOS Coming soon · No App Store download yet
Local-firstNo accountNo AI decides what gets removed
ExactDisk 1.0.0 · Actual app capture with demo projects. Click to enlarge.
Inside ExactDisk 1.0.0

See the app in action.

Actual macOS app captures using demo projects. Explore storage, review the reclaim checks, and see how each outcome is explained. Select any screenshot to enlarge it.

Projects

See which project owns the space.

Ecosystems

Compare the developer tools detected on your Mac.

Review before reclaim

Confirm the selected items before moving them to macOS Trash.

Local-first settings

Offline scanning, no account, and folders you choose.

Reclaim History

Review outcomes and observed storage after a matching rescan.

Visible app blockers

Reclaim waits while visible developer tools are open.

More reclaim safety states

Quiet window

A 60-second quiet window is one of the checks before reclaim.

Changed files

Changes after a scan disable reclaim until you rescan.

Used plans

A used plan cannot be replayed. Rescan to build a new one.

The developer storage problem

Your tools build up more than code.

Build output, package installs, caches and generated files spread across a Mac. A folder and byte count rarely tell you what created them—or whether cleanup is a good idea.

Toolchains leave artifacts

Xcode, Flutter, Gradle, Node and Docker all create their own layers of generated storage.

Projects share ecosystems

One development tool can consume space across many repositories. Project totals alone miss that bigger picture.

Cleanup needs context

Some artifacts rebuild easily. Others are shared, active, or authoritative project data. They should not look the same.

Two ways to understand it

Projects show where. Ecosystems show what.

ExactDisk keeps the project as the main view, with an ecosystem lens that aggregates a toolchain's footprint across projects.

01 / Projects

Where does storage belong?

See the storage associated with each project.

Desktop Client18.4 GB
Mobile App12.7 GB
API Service8.2 GB
02 / Ecosystems

What created it?

Compare technologies across your projects.

Xcode / AppleAcross projects
Node / JavaScriptAcross projects
Gradle / AndroidAcross projects
A clear path from scan to reclaim

Understand first. Act only after fresh checks.

Scanning and planning are read-only. Reclaim requires your confirmation and a final validation before anything moves.

Choose scope

You select the folders ExactDisk may inspect.

Scan

Read-only analysis maps projects and developer storage.

Classify

Rules explain risk and storage attribution.

Revalidate

Fresh checks can block an item if conditions changed.

Move to Trash

Approved items go to macOS Trash, never silent permanent deletion.

Clear classifications

Know the risk before you reclaim.

Classification is explicit and rule-based. The most protective applicable classification wins.

Safe

Disposable output with low recreation cost and a rule showing it is non-authoritative.

Rebuildable

Can be recreated from project or tool inputs, though rebuilding may take time or compute.

Review

Context makes automatic removal too uncertain or potentially disruptive.

Never touch

Source, credentials, signing assets, repository-critical data and items outside approved scope.

Safety-first reclaim

Conservative by design. Explainable at every step.

ExactDisk uses deterministic rules and documented safety signals. When a required check is unavailable or ambiguous, reclaim is blocked.

Your selected folders

The Mac App Store design uses the App Sandbox and user-selected folder access. Permission denial reduces visibility; it does not make cleanup more permissive.

Active project protection

Visible developer apps, filesystem activity, Git evidence and project protection signals can block reclaim when a project appears active or uncertain.

A bounded quiet window

The initial App Store gate requires 60 seconds without relevant writes. This is one conservative signal—not proof that a project is inactive.

Fresh checks before Trash

ExactDisk checks paths, identity, scope, permissions and protection state again immediately before acting. Changed or stale items are skipped.

Only the narrow eligible set

Initial one-click reclaim is limited to project-local, exclusively attributed Safe or Rebuildable artifacts. Shared, global, unattributed, Review, Never-touch and worktree items are excluded.

Trash, with no fallback

Approved items move to macOS Trash. If that operation fails, ExactDisk reports it and leaves the item in place.

Activity has limits. The App Store sandbox cannot inspect every process working directory. A headless or read-only process with no observable filesystem writes may not be detectable. ExactDisk does not claim to detect every active process.
Private by default

Your storage map stays on your Mac.

Core scanning and classification are local-first and offline-capable. No account or cloud service is required.

No analytics
No telemetry
No source-code upload
No external AI API required
No cloud sync required
History stays local and user-clearable
Made for developer storage

Useful detail, without the junk list.

Project-aware scanning

Understand storage in the context of the projects that use it.

Ecosystem breakdown

See how development technologies add up across projects.

Explainable Reclaim Plan

Review the rule and risk behind each eligible recommendation.

Reclaim History

See what ExactDisk attempted; history never authorizes a later cleanup.

Post-reclaim reconciliation

Compare expected and observed storage after a matching rescan.

Thoughtful interface

Light and dark mode, keyboard accessibility and VoiceOver support.

Safety & privacy FAQ

Good questions deserve clear answers.

Does ExactDisk permanently delete files?

No. The current contract moves approved reclaim items to macOS Trash. If Trash fails, ExactDisk reports the failure and leaves the item in place; there is no silent permanent-delete fallback. Items remain recoverable through normal Trash behavior until you empty it.

Can ExactDisk delete my source code?

Source files and other authoritative project data are classified Never touch. The initial App Store reclaim gate is narrower still: only project-local Safe or Rebuildable artifacts are eligible for one-click reclaim. Review and Never-touch items cannot be upgraded by confirmation.

Does AI decide what is safe to remove?

No. Deterministic detectors, attribution rules, risk levels, activity and protection evidence, path checks and fresh pre-execution validation govern reclaim. An LLM does not authorize deletion.

Does scanning remove anything?

No. Scanning and planning are non-destructive. A reclaim action requires explicit confirmation and fresh safety checks immediately before the item moves to Trash.

What happens if files change after I scan?

Reclaim is blocked for the changed item. Relevant filesystem activity after the scan invalidates the clean state and causes the item to be skipped.

Why wait for a quiet period?

The initial App Store gate requires a bounded 60-second write-quiet window. It is an additional conservative signal, not proof that the project is inactive. Relevant writes block reclaim until a fresh valid scan/session.

Can ExactDisk detect every process using a project?

No. The Mac App Store sandbox cannot inspect every process working directory. A headless or read-only process that creates no observable filesystem write may not be detectable. ExactDisk protects against observable and ambiguous sandbox-compatible signals and limits reclaim to project-local Safe or Rebuildable artifacts.

What happens if ExactDisk cannot verify activity?

It blocks reclaim. Unavailable app information, interrupted or incomplete filesystem monitoring, lost folder permission, project or volume mismatch, stale sessions and other failed checks make ExactDisk fail closed.

What about Git worktrees and shared caches?

Git worktrees are Review by default and stay outside the initial one-click reclaim scope. Shared, global or unattributed storage is not treated as belonging exclusively to one project, so it is also excluded from that initial gate.

Does clicking Confirm override a safety warning?

No. Confirmation is required for an otherwise valid reclaim, but it cannot override a safety block. If an item becomes uncertain or fails revalidation, ExactDisk skips it.

Does ExactDisk require Full Disk Access?

Not for the current Mac App Store design. ExactDisk uses the App Sandbox with user-selected folder access. You choose what it may inspect; permission denial reduces visibility and does not make cleanup more permissive.

What data leaves my Mac?

Core scanning and classification are local-first and offline-capable. Core operation does not require an account, cloud sync, analytics, telemetry, source-code or inventory upload, or an external AI API. Project paths, tool metadata, measurements and reclaim history are intended to stay on-device.

Does ExactDisk read my source code?

It prefers filesystem and tool metadata over source-file contents and does not need source-code upload for core operation. Source contents are not intended to be persisted.

Built for the Mac you build on

ExactDisk for macOS — coming soon.

A clearer view of developer storage, designed to let you decide with confidence.

Coming soon for macOS

ExactDisk screenshot