If your 256GB MacBook is showing a storage full warning, you are not alone — and the fix is not to immediately start deleting files you might need. Before touching a single document or app, there are several categories of space that macOS is already holding on your behalf: purgeable data, local Time Machine snapshots, and Trash. Clearing these first is the highest-yield, lowest-risk move you can make. This guide walks through a targeted plan for cramped small-SSD Macs, with realistic recovery estimates at each step.
Why a 256GB MacBook Fills Up So Fast
Apple's base-tier MacBook Air and MacBook Pro models ship with 256GB SSDs. After macOS itself, the recovery partition, and a few apps, real usable space can be as little as 200GB. Add Xcode, Final Cut libraries, or a handful of large games and you hit the wall quickly. What makes small ssd mac storage management especially tricky is that a significant chunk of "used" space is not real data — it is space macOS reserves and can theoretically reclaim, but often does not reclaim unless you push it.
Step 1: Attack Purgeable Space First (0–30 GB)
Purgeable space is macOS's own category: data it has already decided is safe to delete but has not deleted yet. It shows up in System Settings → General → Storage as a lighter color in the bar. Common sources include iCloud-optimized files that have been downloaded locally, cached app data, and old iOS device backups.
The frustrating part: the Finder and most third-party tools count purgeable space as "used," making your drive look more full than it is. macOS clears purgeable space automatically when it runs low — but "low" to macOS can mean a few hundred megabytes, not the several gigabytes you need right now.
How to force macOS to clear purgeable space
- Open Terminal (Applications → Utilities → Terminal).
- Run the following command, which triggers the APFS purge mechanism by attempting to allocate a large file:
This tells diskutil to zero-fill all free space, which forces APFS to convert purgeable blocks into genuinely free space first. It is read-safe and will not erase your data. On a 256GB drive this can take 5–15 minutes.diskutil secureErase freespace 0 / - Alternatively, open System Settings → General → Storage and let the recommendations load — sometimes just opening this panel prompts a purge pass.
Realistic recovery: 2–20 GB, depending on how much iCloud-optimized content you have and how long since you last purged.
Step 2: Delete Local Time Machine Snapshots (2–15 GB)
If you use Time Machine — or even if you have ever used it and stopped — macOS takes hourly local snapshots stored on your internal SSD. These are counted as "System Data" and are meant to be self-managing, but they can accumulate to 10+ GB before macOS gets around to pruning them, especially on a drive that is almost full.
How to list and delete local snapshots
- In Terminal, list all local snapshots:
You will see output liketmutil listlocalsnapshots /com.apple.TimeMachine.2025-11-14-120033.local - Delete individual snapshots by date:
Replace the date-time string with each entry shown in the list.tmutil deletelocalsnapshots 2025-11-14-120033 - Or delete all local snapshots at once (safe if you have an external or network Time Machine backup already):
tmutil deletelocalsnapshots /
Is this safe? Yes, with a caveat. Local snapshots are a convenience copy — they allow Time Machine to restore files when your backup drive is not connected. If you have an up-to-date external Time Machine backup, deleting local snapshots loses nothing. If you have no other backup, you lose the ability to restore accidentally deleted files from those dates. Do not skip your next backup before running this.
Realistic recovery: 2–15 GB.
Step 3: Empty Trash (and Hidden Per-Volume Trashes)
This sounds obvious, but there are two Trash locations most people miss:
- Your main Trash:
~/.Trash/— emptied via Finder → Empty Trash. - External drive Trashes: Each mounted volume has its own hidden
.Trashes/folder at its root. Ejecting without emptying leaves data there indefinitely.
To check the size of your Trash before emptying:
du -sh ~/.TrashTo see all volume Trashes (requires admin):
sudo du -sh /Volumes/*/.Trashes 2>/dev/nullRealistic recovery: 0.5–10 GB (wildly variable, but zero effort).
Step 4: Clear System and User Caches
After the no-risk wins above, caches are the next target. These are genuinely safe to delete because macOS and apps rebuild them as needed — you may notice a slightly slower app launch on first open after clearing.
| Cache location | What it holds | Safe to delete? | Typical size |
|---|---|---|---|
~/Library/Caches/ |
Per-app user caches (Safari, Xcode, Slack, etc.) | Yes | 1–20 GB |
/Library/Caches/ |
System-level and shared caches | Yes | 0.5–5 GB |
~/Library/Logs/ |
App log files | Yes | 100 MB–2 GB |
/private/var/folders/ |
Temp and cache files for running processes | Mostly yes — skip files dated today | 0.5–3 GB |
To manually clear your user caches, quit all apps first, then:
rm -rf ~/Library/Caches/*Do not delete ~/Library/Application Support/ — this holds app data, preferences, and saved state that is not recoverable from the app itself.
If you would rather not run Terminal commands, Crumb handles this in one click — it clears system caches, user caches, logs, and temp files safely, and its one-click Clean also re-triggers the purgeable purge described in Step 1. It is built specifically for small-SSD Macs where every gigabyte counts.
Step 5: Find What Is Actually Taking Space (Before Deleting More)
After the quick wins above, if you still need space, you need a clear picture of what is left. Do not guess — use a disk map.
- Open System Settings → General → Storage and review the category breakdown (macOS Sequoia and later show this clearly).
- For a detailed per-folder breakdown in Terminal:
This shows your 20 largest Downloads items by size — often the single fastest win after caches.du -sh ~/Downloads/* | sort -rh | head -20 - Check for large Xcode data if you develop:
DerivedData is fully safe to delete (Xcode rebuilds it). iOS DeviceSupport files for old devices you no longer test on are also safe to remove.du -sh ~/Library/Developer/Xcode/DerivedData du -sh ~/Library/Developer/Xcode/iOS\ DeviceSupport
What NOT to Delete
On a cramped 256GB macbook, the temptation to delete aggressively is real. These locations are genuinely dangerous to touch:
/System/and/usr/— macOS system files. Deleting anything here can prevent booting.~/Library/Application Support/— App data, not cache. Deleting this is permanent data loss.~/Library/Keychains/— Your passwords and certificates.- Any file you cannot identify — Use Crumb's Is this safe to delete? AI feature: highlight a folder, ask Crumb, and it explains what the folder is and the risk of removing it before you touch anything. Much safer than Googling an unfamiliar path.
Realistic Space Recovery Summary
| Step | Action | Effort | Estimated recovery |
|---|---|---|---|
| 1 | Purge purgeable space | Low (1 command or automatic) | 2–20 GB |
| 2 | Delete local TM snapshots | Low (1–2 Terminal commands) | 2–15 GB |
| 3 | Empty Trash (all volumes) | Very low | 0.5–10 GB |
| 4 | Clear caches and logs | Low–medium | 2–25 GB |
| 5 | Audit Downloads and Xcode data | Medium (manual review) | Varies widely |
Keeping a Small SSD Healthy Long-Term
On a 256GB drive, a single large project or software installation can eat weeks of careful cleaning in minutes. A few habits make a real difference:
- Keep at least 15–20 GB free at all times. APFS performance degrades and macOS cannot write swap files comfortably below about 10 GB free.
- Set a monthly reminder to check
~/Downloads/— it is the fastest-growing folder for most users. - Use iCloud Drive's "Optimize Mac Storage" setting (System Settings → Apple ID → iCloud → iCloud Drive) — it moves cloud-backed files to purgeable status automatically.
- After a major app install or macOS update, run a cache clean — updates often leave behind gigabytes of installer files.
If you want to automate the recurring maintenance without memorizing Terminal commands, download Crumb — its one-click Clean handles purgeable purge, caches, logs, and temp files in one pass, and the Visualize tab gives you an instant treemap of what is actually using your disk so you know where to look next.
Conclusion
When your 256GB MacBook storage is full, start with the space macOS is already willing to give back — purgeable blocks, local Time Machine snapshots, and Trash. These three steps alone can recover 5–40 GB with minimal risk and no permanent data loss. Only after exhausting these should you start auditing real files. Work from lowest-risk to highest, verify before you delete, and use the Is this safe to delete? check for anything you do not recognize. A cramped SSD is manageable with the right sequence.