Low Disk Space Warning Won't Go Away on Mac? 7 Reasons & Fixes

You delete a folder, empty the Trash, and breathe a sigh of relief — only for the low disk space warning to appear on your Mac again within hours or days. If the "disk almost full" notification keeps coming back no matter what you remove, you are not doing anything wrong. macOS has several independent mechanisms that quietly consume storage, and deleting ordinary files does not touch most of them. This guide explains the seven most common culprits and gives you a concrete, permanent fix for each one.

Why the "Mac Low Storage Warning Keeps Coming Back" After You Delete Files

The notification fires when free space drops below roughly 1–2 GB (the exact threshold is not published by Apple and can vary). The trouble is that macOS reserves, regenerates, or hides storage in ways that bypass a normal Finder cleanup. Here are the specific reasons your disk almost full notification keeps appearing.

Reason 1: Purgeable Space Is Not Being Released

macOS reports two numbers that often confuse people: available space and purgeable space. Purgeable space contains iCloud-optimised files, old Time Machine local snapshots, and caches that macOS promises to remove if you need the room — but "if you need the room" means when an app requests a large allocation, not simply when your free space is low. The alert can fire while gigabytes of purgeable space sit untouched.

To see the breakdown, open the Apple menu > System Information > Storage. You will see both numbers side by side.

Fix: Manually trigger a purge from Terminal:

sudo purge

This flushes inactive memory and some disk caches. For a deeper release, temporarily store a large file (a test ISO, for example) that forces macOS to convert purgeable space to free space, then delete the test file. Crumb's one-click Clean also handles purgeable space explicitly, which avoids the manual back-and-forth.

Reason 2: Time Machine Local Snapshots Are Filling the Drive

When your Time Machine backup disk is not connected, macOS silently creates local snapshots on your internal SSD. These are counted as "purgeable" in Disk Utility but still consume real APFS blocks. A laptop used for a week without plugging in an external drive can accumulate 10–30 GB of snapshots.

Fix: List and delete snapshots from Terminal.

1. List all local snapshots:

   tmutil listlocalsnapshots /

2. Delete a specific snapshot (replace the date string with one from the list above):

   tmutil deletelocalsnapshots 2026-05-28-123456

3. Or delete all snapshots at once:

   tmutil deletelocalsnapshots / --all

   Note: The --all flag requires macOS 12 Monterey or later.

If you rarely connect the backup disk, consider reducing the snapshot frequency in System Settings > General > Time Machine, or switching to a network-attached backup so snapshots are written remotely.

Reason 3: App Caches Regenerate Immediately

Caches in ~/Library/Caches are designed to be rebuilt. If you delete them and reopen the same apps, the caches grow back within minutes — sometimes larger than before, because the app re-downloads or re-indexes everything from scratch. Deleting caches once gives only temporary relief.

Fix: Identify which apps own the largest cache folders before deleting anything.

du -sh ~/Library/Caches/* | sort -rh | head -20

If a single app (Xcode DerivedData, Spotify, Chrome) dominates the list, address that app specifically:

• Xcode: Xcode menu > Settings > Locations > Derived Data — click the arrow and delete the folder, or run rm -rf ~/Library/Developer/Xcode/DerivedData.
• Browsers (Chrome, Firefox, Edge): Clear cache from within the browser's settings; the browser manages its own cache limit after that.
• Spotify, Slack, Teams: Look for a "Clear cache" option in each app's preferences.

For system-level caches (/Library/Caches and /var/folders) it is safer to use a tool that knows which files are owned by macOS versus third-party apps. The Is this safe to delete? feature in Crumb can explain any specific folder and flag whether removing it is low-risk or could affect system stability.

Reason 4: System Logs Growing Without Bound

macOS and third-party apps write diagnostic logs to /var/log, ~/Library/Logs, and /Library/Logs. On a machine with a crashing or chatty app, logs can grow to several gigabytes. Unlike caches, logs do not regenerate quickly, so deleting them gives lasting relief — but you should check whether you need them first.

Fix: Inspect sizes before deleting.

du -sh ~/Library/Logs/*
du -sh /Library/Logs/*

Crash logs in ~/Library/Logs/DiagnosticReports are safe to delete once you have filed or dismissed any related bug reports. System logs in /var/log should be left alone unless you are confident about what each file contains.

Reason 5: iOS Device Backups and Software Updates Cached on Mac

If you sync an iPhone or iPad via Finder, full device backups are stored in ~/Library/Application Support/MobileSync/Backup. A single iPhone backup can be 10–60 GB. Old macOS installer files (downloaded but not yet applied, or leftover after an upgrade) also sit in /Applications as files named "Install macOS …" and range from 12–14 GB each.

Fix:

• Manage iPhone backups: open Finder, connect your device, and delete outdated backups from the General tab.
• Delete stale macOS installers: drag "Install macOS …" out of /Applications to the Trash and empty it. These are safe to remove after a successful upgrade.

Reason 6: The Trash Is Not Actually Empty

Files deleted from an external drive, a network volume, or a sandboxed app may land in a hidden .Trash folder on that volume rather than the standard ~/.Trash. Finder's "Empty Trash" command sometimes misses these. The storage is consumed but invisible in your home Trash.

Fix: Empty trash on all volumes:

rm -rf ~/.Trash/*

For external drives, look for a hidden .Trashes folder at the root of each volume. You can reveal hidden files in Finder with Cmd + Shift + ..

Reason 7: "System Data" Is Unusually Large

In macOS Ventura and later, System Settings > General > Storage shows a "System Data" category. This bucket can include virtual machine images, Docker layers, developer tool caches, Rosetta 2 translation caches, and various other files that do not fit neatly into other categories. It is not all actual system files — much of it is third-party data that macOS does not know how to label.

Fix: Drill into what is inside. A disk treemap is the most practical approach. Open Crumb's Visualize tab to get a treemap of your entire drive sorted by size, so you can see exactly which folders are responsible and decide what to remove with full context.

Comparing the Approaches: Quick Reference

How to Stop the Low Disk Space Alert Permanently

A one-time cleanup stops the notification temporarily, but if the underlying cause is a process that regenerates storage (caches, snapshots, logs), the alert will return. The most effective long-term strategy combines three habits:

1. Connect your Time Machine drive regularly so macOS writes backups externally and does not accumulate local snapshots.
2. Set per-app cache limits in browsers and media apps (most have a "limit cache to X GB" option in their settings).
3. Run a cache and purgeable-space sweep monthly rather than reacting to the alert. The Terminal commands above work, or you can use a menu-bar tool that runs the sweep without requiring you to remember each path.

A Word on Safety

Cleaning is permanent. Before removing anything from /Library, /System, or /var, make sure you have a recent backup — a Time Machine backup or a bootable clone. The paths listed in this article under ~/Library/Caches, ~/Library/Logs, and iOS backups are broadly safe for the average user. Files under /System/Library, Keychain data, and Preferences folders should generally be left alone unless you know exactly what you are doing.

Conclusion

The reason your low disk space warning won't go away on Mac is almost always one of these seven causes — purgeable space, local snapshots, regenerating caches, accumulated logs, device backups, leftover installers, or opaque System Data. Each has a specific fix. Work through the list methodically, address the category that applies to your situation, and set up the habits above so the notification does not come back next week. A persistent alert is a symptom, not a problem in itself — once you understand what macOS is actually storing, you can deal with it on your own terms.