Your disk, as a city.
TreeX scans millions of files in seconds and shows where your space goes in a 2D and 2.5D map you can explore. Then it helps you take that space back, safely.
Every developer knows it: node_modules, target, DerivedData, virtualenvs and caches pile up quietly. TreeX recognizes them, tells you which command recreates each one and how long its project has been idle, and moves them to the Trash only after a final check. Free, on macOS, Windows and Linux.
The disk analyzer for developers.
The more space it takes, the taller it stands. Scroll and the city grows.
Animated illustration, sample data
Press 4 and the city turns grey: only the coral towers of build artifacts and caches stay standing. The tallest one is your biggest waste.
Select an artifact and TreeX shows the matching rule, the command that recreates it, like cargo build or npm install, and how long its project has been untouched.
Pick, confirm, and watch the towers sink. Right before touching each folder, TreeX checks it again.
TreeX uses each system's own fast path, down to reading the NTFS Master File Table directly. In its published benchmarks it is the fastest of every tool compared, on every system.
Press Tab and the 2D map rises into an isometric city. Building height shows size, age or file count.
Press T to see space by file extension, U to find duplicate files. TreeX reads as little as possible: sizes first, then the start and end of each file, full contents only when needed.
TreeX quietly keeps the previous analysis of every folder. Press C to see what is new, what grew and what was removed, with nothing to save.
Pick the file for your system. Every download comes straight from the official releases on GitHub.
Open the DMG and drag TreeX into Applications: the treex command-line tool ships inside.
Unzip it and run TreeX.exe; the command-line tool is bin\treex.exe.
One file: make it executable and run it, on most distributions.
Install it with flatpak install --user and launch it from your app menu.
Extract it and run ./install.sh, no root needed.
macOS 13 Ventura or later (Apple Silicon and Intel), Windows 10/11 x64, Linux x86_64 (glibc 2.28 or later).
Free, under your choice of MIT or Apache-2.0.
Yes. TreeX is free, under your choice of MIT or Apache-2.0.
Press 4 in the app or run treex dev ~: TreeX shows build artifacts and caches as coral towers. Pick what to clean in the Dev-Junk panel and confirm; by default everything goes to the Trash.
TreeX checks every item again right before touching it, never follows symlinks, and always refuses system locations and your top-level home folders. Artifacts that may contain manual changes, like virtualenvs, are never preselected.
Yes. The builds are not notarized by Apple yet: right-click TreeX.app → Open, or go to System Settings → Privacy & Security → Open Anyway. You only need to do it once.
macOS protects many folders, such as Mail, Safari and Messages. Without the permission TreeX still works, but skips those folders and tells you. Grant it in System Settings → Privacy & Security → Full Disk Access.
No. TreeX never uses the network, and scans read only names, sizes and dates. File contents are read only when you start a duplicate search, and only for files that share their size with another one.
It is optional. As administrator, TreeX reads the Master File Table directly to analyze a whole drive and, from the second time on, updates it from the USN journal in a fraction of a second.
TreeX is free: if it saved you some gigabytes, or some time, you can return the favor. Sponsorships pay for code-signing certificates, Homebrew, winget and Flathub packages, test machines for the three systems, and the time to keep it the fastest of its kind.
