dush

For your Mac, and for your Terminal

What's eating your disk?

Drop a folder and dush lists everything bigger than 512 MB, largest first. It's very fast, it measures like du, and it only looks. It never deletes.

The app is free and needs macOS 26. The command-line tool is free and open source, and needs macOS 14.

It's a tape measure, not a snoop.

dush for Mac

Drop a folder, see what's big.

Drag one or more folders onto the window or onto the Dock icon, or press ⌘O. dush walks them in parallel and counts every file, hidden ones and app bundles included, while you watch the numbers climb.

  • Caches & Temp needs no folder. It checks the caches and temp folders that only hold stuff your Mac can rebuild: system and app caches, logs, the Trash, npm, Yarn, pnpm, Gradle, Cargo, Go, CocoaPods, Xcode's DerivedData and DeviceSupport, the simulator caches and VS Code's. Folders that aren't there or aren't safe are left out, and nested ones are counted once.
  • Downloads & Desktop scans the two usual suspects in one click.
  • Biggest so far: large files show up the moment they're found, folders as soon as they're measured. Press Esc to stop at any time.
  • Your options: a minimum size (100 MB, 512 MB, 1 GB, 5 GB or your own, like 1.5 GiB), files or folders only, skip node_modules, .git and other developer folders, or exclude names and patterns like *.xcarchive.
Mapping your disk galaxy…

The results

The number comes first.

Every size is the space a file really takes on disk, measured exactly like du: hard links count once, symlinks are never followed, and a folder that owes almost all its size to one subfolder shows up as one line, so a big cache doesn't fill the list three times.

~/Library/Developer

64.10 GB

412,806 items in 1.9 s · 7 items over 512 MB · 3 paths couldn't be read

DerivedData · 33%   Devices · 23%   iPhone16,2 27.0 · 11%   Everything else · 33%

  1. DerivedData~/Library/Developer/Xcode/DerivedData21.37 GB
  2. Devices~/Library/Developer/CoreSimulator/Devices14.90 GB
  3. iPhone16,2 27.0 (24A5355q)~/Library/Developer/Xcode/iOS DeviceSupport/iPhone16,2 27.0 (24A5355q)6.72 GB
  4. Archives~/Library/Developer/Xcode/Archives5.31 GB
  5. Caches~/Library/Developer/CoreSimulator/Caches3.08 GB
  6. Watch7,1 11.0 (22R349)~/Library/Developer/Xcode/watchOS DeviceSupport/Watch7,1 11.0 (22R349)2.12 GB
  7. Previews~/Library/Developer/Xcode/UserData/Previews1.21 GB

Safe to delete?

Ask your Mac, not a server.

Not sure what a folder is? Select it and ask. Apple Intelligence answers on this Mac, with a verdict, a one-line summary and what happens if you remove it. Then ask more, like Will I lose my SwiftUI previews?

dush tells the model only about the item:

  • always its path, name, size and whether it's a file or a folder;
  • if you like, how many items sit inside, the names and sizes of the 10 largest, and when it last changed;
  • never what's inside your files.

What it was told is shown under every answer. No server, no account, no key. Nothing leaves your Mac.

Safe to delete

Xcode's build cache. It grows back on its own.

  • Build products, indexes and logs for every project Xcode has opened.
  • Xcode rebuilds what it needs, so your next build will just be slower.
  • Quit Xcode first so it doesn't write new files halfway through.

Asked Apple Intelligence on this Mac: path, size and the names of the 10 largest items inside. Nothing left this Mac. Never file contents.

  • Safe to delete Data that comes back on its own, like DerivedData.
  • Check first It holds things you may want, like simulators.
  • Keep it Important data, like Xcode Archives with their debug symbols.
  • Protected by dush System folders, keys like ~/.ssh, iCloud Drive and whole personal folders get an answer at once. No AI asked, no bytes sent.

AI answers can be wrong. dush never deletes anything. If you decide to remove it, do it yourself in Finder.

Developer Caches

Your tools rebuild most of this on their own.

dush knows where developer tools keep their caches and adds them up: 48.29 GB on a busy Mac. For each one it says what it is, whether it rebuilds itself or is worth a review first, and how to clear it the way that tool suggests. You do the clearing. dush runs nothing.

Every card has Show in Finder, which selects exactly the cache's folders, and Copy Command when the tool has one. Only the tools' own commands, to paste into Terminal yourself.

And the rest

Small things that keep a Mac roomy.

Our promises

dush only looks. It never deletes.

dush never deletes your files
It only looks. Removing something is always your call, in Finder or Terminal. The one thing dush can remove is its own scan history.
No tracking, no profiling
No analytics, no telemetry, no identifiers. Your scans never leave this Mac.
Offline, always
dush for Mac never uses the network. Apple Intelligence answers on this Mac, so nothing leaves it.
No accounts
No sign-in, no email, no cloud sync.
No in-app purchases
Free. No subscriptions, no Pro version, no ads.

These aren't just words: the tests fail if the code ever reaches the network, deletes a file it doesn't own, or gets a delete button.

Even with the keys to every room, dush only reads names and sizes.

In the Terminal

The same engine, in your shell.

dush started as a command-line tool, and it still is one. The app and the CLI share the same engine, so they report the same sizes for the same folder, down to the byte. Install it with Homebrew:

brew tap andre_rori/tap https://codeberg.org/Andre_Rori/homebrew-tap.git && brew install andre_rori/tap/dush

Try it

# The caches and temp folders, no path needed
dush

# Your home, files over 1 GB, the top 10
dush ~ --min-size 1GB --files-only --top 10

# Skip node_modules, .git, DerivedData and friends
dush ~/Code --exclude-dev

# A report for your scripts
dush ~/Library/Developer --json > developer.json

What you get

      Size  Name
-------------------------------
   6.72 GB  iPhone16,2 27.0 (24A5355q)/
   2.43 GB  com.spotify.client/
   2.09 GB  _cacache/

Found 3 items of at least 512.00 MB.
Scanned 200,874 items (18.78 GB) in 0.9s.
  • Sizes as Finder shows them, 1 GB = 1,000,000,000 bytes.
  • Live progress on stderr, with a joke or two, so piped output stays clean.
  • --json for scripts, NO_COLOR for plain text, dush update to stay current.

See what's taking up space.

What to do about it is up to you.