Purgeable space & APFS snapshots

How to Free Up Purgeable Space on Mac: 7 Methods That Actually Work (2026)

If you've opened About This Mac → Storage and seen a large gray "Purgeable" segment eating into your free space, you're not alone. Purgeable space on Mac is disk space that macOS could reclaim if it needed to, but hasn't yet—occupied by local Time Machine snapshots, iCloud-cached files, and other data macOS considers safe to remove on demand. The catch: macOS sometimes holds onto it longer than you'd like, and it can make your available storage look misleadingly small. Here are seven ways to learn how to free up purgeable space on Mac, ranked from the safest and easiest to the more aggressive, with honest notes on the tradeoffs of each.

What Is Purgeable Space, Exactly?

macOS APFS tracks two numbers: available space and purgeable space. Purgeable bytes are held by:

  • Local Time Machine snapshots — backups stored locally when an external drive isn't connected.
  • iCloud Drive cached files — local copies of files that also exist in the cloud and can be re-downloaded.
  • Optimized Storage items — mail attachments, Apple TV downloads, and similar media that macOS can offload.
  • General APFS purgeable pool — space reserved for CoW (copy-on-write) operations that macOS will reclaim automatically under disk pressure.

Most of the time macOS reclaims this space on its own. The methods below are for when you need it now.

Method 1: Let macOS Reclaim It Automatically (Safest)

Risk: None. Effectiveness: Moderate.

macOS automatically purges purgeable space whenever an app requests a large allocation. If you simply copy a big file, start a video export, or run a disk-hungry app, macOS will release purgeable storage in the background without any intervention. This is the intended behavior—if you can wait, do nothing.

When it falls short: macOS can be conservative. It may not release space until the disk is near-full, even if you have tens of gigabytes of purgeable data sitting idle.

Method 2: Enable or Trigger Optimized Storage (Safe)

Risk: Low (files remain in iCloud). Effectiveness: High for iCloud users.

  1. Open System Settings → General → Storage.
  2. Click Store in iCloud and enable Desktop & Documents, Photos, and Messages.
  3. Enable Optimize Mac Storage to allow macOS to remove local copies of iCloud files you haven't opened recently.

Files that get offloaded show a small cloud icon in Finder. They're never deleted—only the local cache is removed. You need sufficient iCloud storage for this to be meaningful.

Method 3: Empty Caches and Temporary Files (Safe with Care)

Risk: Low–Medium. Effectiveness: Low–Medium (purgeable specifically).

Caches in ~/Library/Caches and /Library/Caches aren't always counted as purgeable, but clearing them reduces overall disk consumption and can indirectly free purgeable budget. In Finder, press Cmd+Shift+G and navigate to ~/Library/Caches. You can safely delete the contents of most app-specific subfolders (not the folders themselves). Avoid deleting anything inside com.apple.bird or iCloud-related caches while a sync is in progress.

Doing this by hand is tedious and error-prone. Crumb identifies and removes user caches, system caches, logs, and temporary files in one pass—with a preview before anything is deleted, so you know exactly what's going.)

Method 4: Restart Your Mac (Safe, Often Overlooked)

Risk: None. Effectiveness: Low–Moderate.

A full restart flushes kernel caches, clears RAM-backed virtual-memory swap files in some configurations, and prompts macOS to re-evaluate its snapshot policy. Many users find that after a restart the purgeable figure drops noticeably in the Storage graph. This costs nothing and should always be tried before more invasive steps.

Method 5: Delete Local Time Machine Snapshots (Moderate)

Risk: Low (you lose rollback history). Effectiveness: High.

Local snapshots are typically the largest contributor to purgeable space. To list them:

tmutil listlocalsnapshots /

To delete a specific snapshot (replace the date string with one from your list):

tmutil deletelocalsnapshots 2026-05-28-123456

To delete all local snapshots at once:

for snap in $(tmutil listlocalsnapshots / | grep "com.apple"); do
  tmutil deletelocalsnapshots "${snap##*@}"
done

Tradeoff: Once deleted, you cannot roll back to those snapshots. If you have a recent external Time Machine backup you trust, the risk is low. If your last backup was weeks ago, think twice.

Method 6: Force Purgeable Space to Release via Disk Write (Effective but Slow)

Risk: Low–Medium. Effectiveness: Very High.

macOS releases purgeable space when disk pressure is high. You can manufacture that pressure by writing a large dummy file that forces the OS to purge. The classic Terminal approach:

# Check current free+purgeable space first
df -h /

# Write a large file to trigger purging (adjust size to ~90% of reported free space)
dd if=/dev/zero of=~/Desktop/purge_trigger.tmp bs=1m count=50000

# Delete the file immediately after
rm ~/Desktop/purge_trigger.tmp

Caution: If you miscalculate the size and actually fill the disk, some apps may crash or fail to save. Use df -h / first to gauge how much space is genuinely free, and leave at least 5 GB of headroom. This is a blunt instrument—effective, but clumsy.

Method 7: Use a One-Click Tool to Handle All of the Above

Risk: Low (with preview). Effectiveness: High.

The methods above each target one part of the purgeable puzzle. A dedicated cleaner handles them together without guesswork. Download Crumb, click Clean from the menu bar, and it sweeps system data, user caches, logs, temporary files, and purgeable space in one pass—showing you exactly what it found before removing anything. For anything you're unsure about, the built-in AI can explain what a folder is and whether it's safe to delete.

Crumb also includes a Visualize tab with a full disk map so you can see where your space actually went, and an Uninstall feature that removes apps and their leftover support files that manual dragging to the Trash misses.

Comparison: Which Method Should You Use?

Method Risk Speed Space Recovered
Wait for macOS None Slow Low–High (unpredictable)
Optimized Storage Low Fast to enable High (iCloud users)
Clear caches manually Low–Med Slow Low–Med
Restart Mac None Fast Low–Med
Delete TM snapshots Low Fast High
Disk-fill trigger (dd) Med Moderate Very High
One-click cleaner Low (preview first) Fast High

A Note on Safety: What You Can and Cannot Undo

Deleting Time Machine snapshots is permanent—those rollback points are gone. Clearing caches is generally safe (apps rebuild them) but occasionally causes a slow app launch the first time after. The disk-fill trick is harmless if sized correctly but risky if you miscalculate. Optimized Storage is fully reversible (re-download from iCloud). Whatever method you use, having at least one external or cloud backup before an aggressive clean is always a good idea.

Conclusion

Purgeable space on macOS isn't wasted—it's intentional—but it can linger far longer than useful. For most users, the fastest path is: restart, then delete local Time Machine snapshots if the restart alone doesn't reclaim enough. If you want to clear purgeable space on your Mac without memorizing Terminal commands or hunting through ~/Library by hand, a tool like Crumb handles the whole stack in one shot, with a preview so nothing disappears without your say-so.

Reclaim your disk in one click

Crumb audits your whole Mac, tells you what's safe to delete, and frees the space in seconds — private, local, and Apple-notarized.

Download Crumb for macOS

Frequently asked questions

What is purgeable space on Mac and is it safe to remove?
Purgeable space is disk space macOS has reserved for local Time Machine snapshots, iCloud cached files, and other data it can reclaim on demand. It is generally safe to remove—macOS designed it to be releasable—but deleting Time Machine snapshots means losing those specific rollback points, so having a current backup is advisable first.
Why doesn't purgeable space go away on its own?
macOS only releases purgeable space when an app requests a large allocation and disk pressure is high. On a disk that still shows several gigabytes free, macOS may hold snapshots and caches indefinitely because it sees no urgent need to purge them.
Does restarting a Mac free purgeable space?
A restart can reduce purgeable space by flushing kernel caches and prompting macOS to re-evaluate its snapshot retention policy. It's not guaranteed to clear everything, but it's free, instant, and worth trying before more aggressive methods.
Is the 'fill the disk' trick to remove purgeable space safe?
It works by writing a large dummy file to force macOS to release purgeable space under disk pressure, then deleting the file immediately. The main risk is accidentally filling the disk if you miscalculate the size—always check actual free space with 'df -h /' first and leave at least 5 GB of headroom.
How do I delete local Time Machine snapshots to clear purgeable space?
Run 'tmutil listlocalsnapshots /' in Terminal to see all local snapshots, then use 'tmutil deletelocalsnapshots <date-string>' to delete specific ones. Deleting them is permanent, so ensure you have an up-to-date external or cloud backup before proceeding.