You try to copy a folder, download a file, or save a project — and macOS throws back: "There isn't enough space." The frustrating part? Your disk might show gigabytes free. The there isn't enough space Mac error isn't always about raw disk usage; it often comes from how macOS reserves, protects, and accounts for space in ways that aren't immediately visible. This guide explains every cause and gives you concrete steps to fix it.
Why macOS Says There Isn't Enough Space (Even When It Looks Fine)
macOS manages disk space through several layers that the Finder's simple "X GB available" bar doesn't fully reflect:
- APFS snapshots: Time Machine and system updates create local snapshots that consume real blocks on your drive. macOS will reclaim them under pressure, but not always fast enough for a large copy in progress.
- Purgeable space: iCloud-optimized files, caches marked safe-to-delete, and other data sit in a "purgeable" bucket. macOS counts this as available in Finder but may not release it in time for your write.
- System Data: The catch-all category in About This Mac includes caches, logs, Rosetta translations, and app support files that accumulate silently.
- Per-file reservation: When macOS copies a large file, it pre-allocates the full destination size before writing a single byte. If fragmented free space can't satisfy that reservation, the copy fails immediately.
Step 1 — Check What Is Actually Using Space
Open Apple menu → About This Mac → More Info → Storage (or General → Storage on Ventura+). Note the "System Data" figure. Anything above 20–30 GB is worth investigating.
For a precise command-line view of your free blocks versus purgeable:
df -H /The Available column here reflects non-purgeable free space only — this is the number that matters for writes.
To see how much space local Time Machine snapshots are holding:
tmutil listlocalsnapshots /Step 2 — Delete Local Time Machine Snapshots
Local snapshots are the most common hidden culprit behind the not enough space to copy file Mac error. macOS creates them automatically before updates and during Time Machine backups.
- Open Terminal (
/Applications/Utilities/Terminal.app). - List all snapshots:
tmutil listlocalsnapshots / - Delete a specific snapshot by its date string:
tmutil deletelocalsnapshots 2025-11-14-123456 - Or delete all local snapshots at once:
tmutil deletelocalsnapshots /
Is this safe? Yes. Local snapshots are copies of data already on your Mac. Deleting them does not affect your files or your remote Time Machine backup. macOS will create new ones at the next backup cycle.
Step 3 — Clear Caches and Logs
User and system caches regenerate automatically; deleting them is safe, though apps may launch slightly slower the first time afterward.
User caches (safe to delete)
rm -rf ~/Library/Caches/*System logs (safe to delete)
sudo rm -rf /private/var/log/*
sudo rm -rf /Library/Logs/*Temporary files (safe to delete)
sudo rm -rf /private/var/folders/*After running these, restart your Mac so macOS can rebuild any required temp directories.
If you'd rather not run Terminal commands, Crumb handles caches, logs, temp files, and purgeable space in one click — and shows you exactly how many gigabytes each category holds before you commit to deleting anything.
Step 4 — Force macOS to Release Purgeable Space
Purgeable space contains iCloud Drive local copies and cached data that macOS promised to release but hasn't yet. You can nudge it manually:
- Open Disk Utility (
/Applications/Utilities/Disk Utility.app). - Select your startup disk (usually "Macintosh HD").
- Click First Aid and let it run. This triggers a pass that reclaims unreferenced purgeable blocks.
Alternatively, creating and immediately deleting a large dummy file forces the kernel to flush purgeable allocations:
dd if=/dev/zero of=~/Desktop/flush.tmp bs=1m count=4096
rm ~/Desktop/flush.tmpUse this cautiously — if you are already very low on space the dd command itself may fail.
Step 5 — Find and Remove Large Files Manually
Sometimes the problem is straightforward: a few large files or folders have accumulated unnoticed.
# Top 20 largest items in your home folder
du -sh ~/* | sort -rh | head -20
# Dig deeper into a specific directory
du -sh ~/Downloads/* | sort -rh | head -20Common offenders:
~/Downloads— forgotten installers and archives, often several gigabytes~/Library/Application Support— old app data from uninstalled apps~/Library/Containers— sandboxed app caches that can grow very large/Library/Developer/Xcodeor~/Library/Developer/Xcode/DerivedData— if you have Xcode installed, derived data alone can exceed 20 GB
Be careful: deleting files inside ~/Library/Application Support can erase app settings and saved data. Move items to Trash and test your apps before emptying.
Step 6 — Uninstall Apps and Their Leftovers
Dragging an app to Trash leaves behind support files, preference plists, caches, and Launch Agents scattered across your Library. These orphaned files don't appear in Finder's storage bar but do consume real space.
A proper uninstaller finds and removes these leftovers. Download Crumb to use its Uninstall tab, which identifies leftover files for any app you remove and lets you review them before deletion.
Quick Reference: Causes and Fixes
| Cause | How to check | Fix | Risk |
|---|---|---|---|
| Local Time Machine snapshots | tmutil listlocalsnapshots / |
tmutil deletelocalsnapshots / |
None — files are untouched |
| Purgeable iCloud / cache blocks | About This Mac → Storage | Disk Utility First Aid or Crumb one-click clean | Very low — macOS controls what is purgeable |
| User & system caches | du -sh ~/Library/Caches |
Delete ~/Library/Caches/* |
Low — caches rebuild automatically |
| Large files in Downloads / Desktop | du -sh ~/Downloads/* | sort -rh |
Manually review and delete | Medium — review before deleting |
| Orphaned app support files | Check ~/Library/Application Support |
Use a dedicated uninstaller | Medium — verify app is truly uninstalled first |
| Xcode DerivedData | du -sh ~/Library/Developer/Xcode/DerivedData |
Delete DerivedData folder contents |
Low — Xcode rebuilds on next build |
Preventing the Error in the Future
- Keep at least 15–20 GB free at all times. APFS performance degrades and snapshot behavior becomes unpredictable below that threshold.
- If you use Time Machine over Wi-Fi, local snapshots accumulate faster. Back up over ethernet or prune snapshots monthly.
- Run a cache and purgeable clean before starting any large transfer (video exports, disk images, virtual machine creation).
- Use Finder's Compress option to zip large folders before copying them to external drives — it reduces both transfer size and the space reservation macOS requires.
Conclusion
The there isn't enough space Mac error when copying, downloading, or saving usually comes down to one of four things: local snapshots hoarding blocks, purgeable space that hasn't been flushed, accumulated caches and logs, or simply large files you've forgotten about. Work through Steps 1–4 in order and you will almost always resolve the error without spending a cent. If you want a faster path to reclaiming purgeable and cached space without Terminal, Crumb does it in one click — but the manual steps above work just as well and cost nothing.