Skip to content
Edith

Use case

Clean Up a Full Mac Disk With Edith

A routine for the day macOS says your startup disk is almost full, with every deletion going to the Trash first.

Updated by

Get Edith

The problem

A full disk rarely has one cause. On a Mac used for work it is usually a mix of build caches, package downloads, old project folders, a few huge files you forgot about, and apps you stopped using months ago, each with support files left in your Library folder. Storage settings show the categories but not which items are safe to remove, and deleting the wrong folder by hand can cost you real work.

This routine uses four Edith extensions in order, from the safest wins to the ones that need a decision, and everything it removes goes to the Trash first.

The setup

  1. 1

    Quit the heavy apps

    Caches in use cannot be cleared cleanly, and quitting frees memory and swap too. Running Apps lists every open app with its CPU and memory use. Apps with unsaved work ask before closing, and Finder and Edith always stay open.

  2. 2

    Trash the rebuildable caches

    Cleaner scans for build caches, package downloads and old Xcode data. Review each category, untick what you want to keep, and confirm. On a developer Mac this is often the biggest win, and the lowest risk.

  3. 3

    Sweep old projects

    Point Cleaner at your projects folder to find build output, node_modules, virtual environments and git worktrees you have not touched for a while.

  4. 4

    Find the big files

    Disk Map draws any folder as blocks sized by the space they use. Start with your home folder, click into the biggest blocks, reveal a file in Finder to check it, and move it to the Trash if you no longer need it.

  5. 5

    Remove apps you do not use

    App Updates removes an app together with the Library files named after its bundle identifier. It shows the exact list first, and you can untick anything to keep.

  6. 6

    Empty the Trash

    Nothing above frees space until the Trash is emptied. Check it once more, then empty it.

The whole thing as one script

Each command that removes something previews by default and acts only with --yes. Run the script once without the --yes lines to see the totals, then again to apply.

 ed apps ls
 ed apps quit Xcode --yes
 ed cleaner scan
 ed cleaner clean --category derivedData --yes
 ed cleaner clean --category npm --yes
 ed cleaner scan --root ~/code
 ed cleaner clean --root ~/code --category worktrees --older-than 2w --yes
 ed maintenance inventory --no-updates
 ed maintenance remove /Applications/Example.app --yes

ed maintenance inventory lists the apps in /Applications and ~/Applications, which helps you spot the ones to remove. ed cleaner categories lists every cache Cleaner knows and what it holds.

Pitfalls

  • ed cleaner clean --yes with no category takes everything. On the command line it moves every item the scan found, not the subset you would tick in the app. Pass --category, or use the app when you want to pick.
  • Xcode archives hold crash symbols. Keep archives for builds you still ship. Cleaner leaves them unticked by default in the app.
  • Dirty worktrees are skipped. Worktrees with uncommitted changes stay unless you pass --include-dirty. Removing one keeps its branch and commits.
  • Simulators are not caches. Cleaner clears simulator caches but leaves devices alone. Run xcrun simctl delete unavailable after an Xcode upgrade.
  • Free space can lag. macOS may take a moment to show the new free space after the Trash is emptied.

Go deeper

How to free disk space on a Mac for developers covers the built-in commands for each cache, including du, brew cleanup and xcrun simctl, and when each one is the better tool.