Your Mac fills up again a week after you cleared it
· 7 min read
If you cleared 40 GB last Saturday and the Mac is full again by Friday, almost nothing has gone wrong. Most of what you deleted was working data that macOS rebuilds on demand, so it came straight back. The useful question is not how to delete it again, but which part of the returning space is normal and which part is a leak you can actually close.
Work through the categories below in order. The first four regenerate by design and are not worth fighting. The last three are where recurring space is usually being lost.
The things that come back on purpose
Caches. Browsers, Mail, Photos, Spotlight, music and video apps all keep local copies so they do not fetch the same thing twice. Delete them and they refill as you use the Mac. Clearing a browser cache buys a few gigabytes and costs you slower page loads for a day. Which caches are safe to delete on a Mac covers which are worth touching at all.
Local Time Machine snapshots. macOS keeps hourly snapshots of the internal drive so you can go back even when the backup drive is not connected. They expand into free space and shrink when the Mac needs room, which is why they look alarming and usually are not. If they are pinning the drive, Time Machine local snapshots taking space on the internal drive explains how to see and thin them.
Purgeable space. Finder counts space that macOS will release automatically under pressure. It can make a drive read as full while genuinely having room, and no amount of deleting changes the number. Purgeable space on a Mac unpacks it.
Swap. When RAM runs short, macOS writes pages to disk. Swap grows during heavy days and shrinks after a restart. Treat it as a symptom of how much you are running, not a cleanup target. Swap files on a Mac has the detail.
If the returning space is all in these four, the honest answer is that the Mac is doing its job and the drive is simply smaller than your workload. That is not a cleaning problem.
The leaks that actually refill a drive
Downloads. This is the most common one by a distance. Installers, exports, email attachments opened once, zips expanded and never deleted. A week of ordinary work adds several gigabytes without any single file feeling large.
Development leftovers. If you build software, this dwarfs everything else. Xcode DerivedData, simulator runtimes and archives rebuild every time you compile; node_modules folders sit in every project you have ever cloned; package caches for the usual package managers grow forever because nothing ever prunes them. See Xcode is eating the disk, find and delete old node_modules folders and package caches on a Mac. A Docker disk image is its own case: it rarely shrinks on its own after you delete things inside it, as Docker.raw is huge on a Mac explains.
Photos and iCloud settings. If Optimize Mac Storage is off, every full-resolution original syncs down, including ones added from a phone this week. That is a steady inbound stream, not a one-off. Optimize Mac storage in iCloud covers what the setting actually removes.
Mail. Attachments download as you read messages, and the index grows with the mailbox. Clearing it once means it downloads again next time you open the same threads. Mail is taking up storage on a Mac goes through it.
Old device backups. An iPhone backed up to the Mac leaves a copy per device, and older ones are not removed automatically. This one is pure dead weight: see find and delete old iPhone backups.
Measure the refill instead of guessing
One number tells you far more than a week of deleting: how much the drive lost between two points in time, broken down by folder.
Open Terminal and run this on a folder you suspect, for example your home folder:
du -sh ~/Library/Caches ~/Downloads ~/Library/Developer 2>/dev/null
Note the numbers. Run the same command in a week. Whatever grew is where your space is going, and you no longer have to speculate.
For a whole-drive view, System Settings, General, Storage gives Apple’s own breakdown, though System Data lumps a lot together. What System Data is on a Mac explains what is inside that bar.
Two habits prevent most of the cycle. Empty the Trash as a step in the cleanup rather than an afterthought, since deleted files hold space until you do. And set Downloads to sort by size, not date, so the one 6 GB installer is visible above the noise.
Clearing the same thing every month is the wrong workflow
If you find yourself doing this cleanup repeatedly, the problem to solve is the repetition, not the gigabytes.
Crumb is a menu bar disk cleaner built around that. Its audit is read-only and covers the whole Mac rather than just the home folder: System Data broken into caches, logs, swap, temporary files and leftovers, local snapshots, a Docker disk image’s real versus apparent size, iOS backups, and a cross-user view showing which account on a shared Mac is using the space. That last one answers the question no manual method answers easily, and it is covered in a shared Mac: which user account is using all the space.
The part that matters for this article is Ask Crumb: describe a goal in plain English or point at a file, and it explains what the item is, whether it regenerates and what breaks if it is gone, then proposes a plan. Nothing is deleted until you approve it, and reclaimable removals can be reviewed and undone afterward. Knowing that a folder will simply rebuild is the difference between a cleanup that lasts and one you repeat next month.
The whole-Mac audit, the System Data breakdown and one full cleanup are free forever. $9 once unlocks the rest on up to two Macs. Everything above can be done by hand with Finder and Terminal, so start there if you prefer.
Questions
Does restarting the Mac free up space? Often a few gigabytes, yes. A restart clears swap and some temporary files, and it lets macOS purge caches it was holding. It is the cheapest thing to try before any cleaning.
Should I delete the Library folder caches every week? No. Weekly cache deletion buys space the Mac takes straight back while making apps slower each time they rebuild. Delete a specific cache when a specific app is misbehaving or has grown unreasonably, not on a schedule.
Finder says the drive is full but the folder sizes do not add up. Why? Usually snapshots, purgeable space or files owned by another user account that Finder will not size for you. The Mac says storage is full but the folders do not add up walks through the gap.
Is there a point at which the answer is just a bigger drive? Yes. If the recurring space is all caches, snapshots and swap, and you have already thinned the real leaks, the Mac is telling you the working set does not fit. An external SSD for archives or projects is a better use of an afternoon than another cleanup.