The Mac owners who never see "Your disk is almost full" aren't the ones with bigger drives — they're the ones who spend ten minutes a week on three specific things before they become a problem. Everyone else does a 30-minute or hour-long deep cleanup once every six months, in a panic, after Photos refuses to sync or Xcode won't compile. This is the routine for the first group: three checks, ten minutes, once a week, none of which requires thinking hard about what's safe to delete because the same three things are always safe.

Why weekly beats "when it's full"

Storage problems compound quietly. A Downloads folder that gains 200MB a week is invisible day to day, but eighteen months later it's 15GB of installers nobody will ever open again. The same is true of caches, Trash, and screen recordings — none of them are urgent on any given day, which is exactly why they never get addressed until the disk is at 95% and every option feels urgent at once.

A weekly routine breaks that pattern because it treats these as maintenance, not emergency response. Ten minutes spent regularly costs less total time than the same work done in a panic, and it never coincides with a deadline.

The three things worth checking every week

1. Empty the Trash (1 minute)

Finder's Trash holds everything you've deleted until you empty it, and on a Mac used daily this adds up faster than people expect — deleted Downloads, cleared-out project folders, discarded exports. Right-click the Trash icon and Empty Trash, or set Storage → Recommendations → Empty Trash Automatically to remove items older than 30 days on its own. Automatic emptying is reasonable for most people; skip it if you sometimes need to recover something a few weeks after deleting it.

2. Sort Downloads by size and clear what you recognise (5 minutes)

Open ~/Downloads, switch to list view, sort by size, and work down from the top. You're not doing a full audit — you're deleting the installers and duplicate files you clearly don't need anymore. A .dmg for an app you already installed weeks ago, a duplicate report (1).pdf you already filed elsewhere, a zip you extracted and never removed. This folder is where casual accumulation happens fastest because every browser download lands here by default.

3. Clear developer caches if you've been building anything (4 minutes)

If you write code, this is the step that actually matters most, because build tools generate disposable data continuously and none of them clean up after themselves on a schedule.

# Xcode build products
rm -rf ~/Library/Developer/Xcode/DerivedData/*

# npm cache verification and pruning
npm cache verify

# pnpm store — removes anything no project currently references
pnpm store prune

# Homebrew downloaded bottles
brew cleanup

You don't need to run all four every week — pick whichever tools you actually used that week. If you didn't touch Xcode, skip the DerivedData line. The point is matching the maintenance to what you actually generated, not running a fixed script regardless of relevance.

What this routine deliberately skips

This is not a deep cleanup, and it shouldn't try to be one in ten minutes. It skips:

  • Docker's disk image, which needs a deliberate docker system prune decision, not a weekly reflex
  • iOS device backups, which you should review individually, not batch-delete
  • Photos and Messages, which hold content you may want to keep
  • A full storage map, which is worth doing monthly rather than weekly

Trying to cram everything into a weekly routine is how people abandon the habit after two weeks. Keep it to the three items above, and reserve the bigger, more deliberate cleanup for a monthly pass.

Making it actually happen every week

A calendar reminder works better than intention alone. Tie it to something you already do weekly — Friday afternoon wind-down, Monday morning before starting the week's first task — rather than treating it as a floating to-do that competes with everything else. The routine only works if it's boring and automatic; the moment it requires a decision about whether to do it, it starts getting skipped.

When the weekly routine isn't enough

If you're still watching available space drop steadily despite doing this every week, that's a sign something larger is accumulating that a ten-minute routine can't catch — a Docker.raw file that's crept up over months, a forgotten node_modules in a project you haven't opened, an old virtual machine disk. That's the point to open a proper storage map and do a slower, more thorough pass rather than adding more steps to the weekly one.

Ten minutes is a ceiling, not a target

The point of keeping this routine to ten minutes isn't that ten minutes is some ideal duration — it's that a fixed, small ceiling is what makes a weekly habit survive contact with a busy week. If Downloads is already clean because last week's pass caught everything, the routine might take three minutes this time, and that's fine. The goal is never to find a fixed amount of clutter to justify the time spent; some weeks there's genuinely little to do, and that's the routine working as intended, not evidence it wasn't worth doing.

Resist the temptation to expand the routine because a given week goes quickly. If the three checks take two minutes because your Mac is already tidy, use the remaining eight minutes for something else — don't let a fast week become the excuse to start auditing Photos or reorganising Documents, which belongs in a monthly or quarterly pass, not this one.

What a typical month looks like combining both cadences

A practical rhythm most people settle into: the weekly ten-minute routine described here running every week without exception, plus a longer monthly session — perhaps thirty minutes — that covers developer caches more thoroughly, checks iOS backups, and opens a full storage map. The weekly pass prevents the slow accumulation that causes storage panics; the monthly pass catches the categories the weekly routine deliberately skips. Neither replaces the other, and running only one of the two tends to leave a gap: weekly alone misses Docker and forgotten projects, monthly alone lets Downloads and Trash creep for weeks between sessions.

Where VolumeLens comes in

Once a month, or whenever the weekly routine stops keeping pace, it's worth actually looking at the disk rather than guessing at what changed. VolumeLens draws every folder as a rectangle sized by real usage, so whatever has grown since your last look is also the most visible thing on the map. It runs locally with no network code and no telemetry, and its only action is Move to Trash after you've reviewed exactly what's included — which makes it a reasonable companion to a routine built on small, low-risk decisions rather than one big irreversible one.