BlitzTree

A fast, native disk-space treemap for macOS, in the spirit of WizTree. It scans a whole Mac (3.6M files) in about 14 seconds.

Download BlitzTree.dmg and drag the app into Applications. Requires Apple Silicon and macOS 14 or later.

Signed with a Developer ID and notarized by Apple, so it opens like any other app. Grant Full Disk Access when prompted, then relaunch.

• Cushion-shaded treemap colored by file type, with a synced Finder-style outline list
• Prefer DaisyDisk? Switch to rings in the toolbar: click a folder to zoom in, the middle to go back
• Zoom into folders, reveal in Finder, or move to Trash (with confirmation)
• Clean Up panel: finds folders that are safe to delete (caches, node_modules, Rust target, Xcode DerivedData and more) so you can trash them in one go
• AI cleanup: click "Clean up with Claude Code" (or Codex) and your own agent plans what can go, live in the panel, while the treemap lights up those folders. BlitzTree does the cleanup itself, in two steps you approve: move to Trash, then delete for good. No agent installed? One click sets up Codex (free with a ChatGPT account) or Claude Code
• Live progress while scanning, and an optional free-space block
• Native AppKit/SwiftUI, with the Liquid Glass design on macOS 26 and later
• No telemetry. BlitzTree itself only goes online to check GitHub for updates once a day (installed when you quit); the AI cleanup only runs when you click it, using your own agent, which sends folder paths and sizes from the scan (never file contents) to Anthropic or OpenAI

• getattrlistbulk(2) reads a whole directory's metadata in one syscall instead of one stat per file.
• A Rust worker pool keeps many directories in flight, and scan threads run at user-initiated QoS: they stay on performance cores without starving the UI.
• The treemap is laid out once and painted on every core in parallel, so zooming redraws in a couple of frames.

Method, full results and a comparison with other tools: BENCHMARKS.md.

Sizes are allocated bytes, matching du. Hard-linked files count once, the scan stays on one volume, and cloud-only iCloud folders are never downloaded. Root-only system data that no app can read is reported in the status bar instead of hidden.

The agent runs headless and read-only: it only writes a plan from the scan BlitzTree already has. BlitzTree then acts on it behind its own checks, whatever the plan says:

• Only paths inside your home folder, never Documents, Desktop, Photos, iCloud Drive, Mail, keychains or ~/.ssh (build output such as node_modules inside them is allowed, and so are the Codex app's chat folders in ~/Documents/Codex), never a git repository or a whole folder like ~/Library/Caches
• Only each tool's own cache cleanup commands (uv cache clean, brew cleanup, npm cache clean and similar, plus xcrun simctl for Xcode simulator runtimes and device data), with no shell syntax
• Codex chats and projects you used in the last 2 days are left alone
• Caches of apps that are open are skipped until you quit them
• "Delete for good" removes only what this cleanup moved to the Trash

Requires Xcode 26 or later and Rust.

./build.sh              # build/BlitzTree.app
./deploy.sh             # build and install to /Applications
cargo test --release    # engine tests

The Rust engine hands the finished tree to the Swift UI as flat arrays over a C interface, with no copying. BlitzTree <path> scans a specific folder.

An optional, read-only CLI uses the same scan engine without opening the GUI or launching an AI agent:

cargo build --locked --release --features cli --bin blitztree
./target/release/blitztree scan --root "$HOME/Downloads"
./target/release/blitztree quick-wins --root "$HOME" --limit 20

scan lists the largest directories and files as JSON. quick-wins includes that inventory plus the Clean Up panel's existing candidates and labels. The panel and CLI share one Rust implementation of the rules, with no new heuristics. Both report incomplete scans; allocated bytes are not a promise of reclaimable space. Neither command modifies the scanned files.

The CLI is built from source separately from the app. Its JSON dependency is only compiled with the cli feature. See the CLI contract and tests.

MIT