Time Machine & local backups

Delete Time Machine Local Snapshots on Mac: 3 Methods for 2026

If macOS is showing far less free space than you expect, local Time Machine snapshots are often the culprit. These APFS snapshots accumulate silently in the background and can easily consume tens of gigabytes on a laptop that has never seen an external backup drive. This guide walks through the three real methods to delete Time Machine local snapshots — Terminal commands, Disk Utility, and a one-click cleaner — so you can choose the approach that suits you and understand exactly when space is actually reclaimed.

What Are Local Time Machine Snapshots?

Since macOS High Sierra, Time Machine creates hourly APFS snapshots of your startup volume even when your backup drive is disconnected. These are stored on the same disk they protect, not on an external drive. macOS labels them as "Purgeable" space in Disk Utility and in About This Mac, which means the system can theoretically reclaim them under memory pressure — but in practice that does not always happen promptly, especially on machines with fast SSDs and ample RAM.

Local snapshots are generally safe to delete. They are not your primary Time Machine backup; that lives on your external or network drive. Removing local snapshots does not affect files on your disk — it only removes the ability to restore to a specific hourly checkpoint from the current drive. If you have an up-to-date external backup, deleting them carries essentially no risk.

Method 1: Terminal with tmutil (Most Control)

This is the most precise approach. tmutil is Apple's own command-line interface for Time Machine and works reliably on macOS Monterey (12) through macOS Sequoia (15) and beyond.

Step 1 — List all local snapshots

Open Terminal (Applications > Utilities > Terminal) and run:

tmutil listlocalsnapshots /

You will see output like:

com.apple.TimeMachine.2024-11-15-091234
com.apple.TimeMachine.2024-11-15-141512
com.apple.TimeMachine.2024-11-16-082001

Each line is one snapshot, identified by its timestamp.

Step 2 — Delete a specific snapshot

Use the date-string portion of the snapshot name (without the com.apple.TimeMachine. prefix):

tmutil deletelocalsnapshots 2024-11-15-091234

Repeat for each snapshot you want to remove.

Step 3 — Delete all local snapshots at once

To remove every local snapshot in a single command, combine tmutil listlocalsnapshots with a loop:

for snap in $(tmutil listlocalsnapshots / | grep -oE '[0-9]{4}-[0-9]{2}-[0-9]{2}-[0-9]{6}'); do
  tmutil deletelocalsnapshots "$snap"
done

No sudo is required on recent macOS versions. After running this, Disk Utility or About This Mac should show the recovered space within a minute or two.

Why space may not appear freed immediately

APFS defers certain metadata writes. If the free-space number does not update right away, run diskutil apfs listSnapshots disk3s1 (replace disk3s1 with your actual volume identifier from diskutil list) to confirm the snapshots are gone, then wait a moment for the Finder to refresh its storage summary.

Method 2: Disk Utility (GUI, No Terminal)

Disk Utility does not give you snapshot-by-snapshot control, but it can delete all snapshots on a volume through its snapshot browser — useful if you prefer a graphical tool.

  1. Open Disk Utility (Applications > Utilities > Disk Utility).
  2. From the menu bar choose View > Show All Devices if your volume is not visible.
  3. Select your APFS volume (typically named Macintosh HD) in the sidebar.
  4. In macOS Ventura and later, choose Edit > Delete APFS Snapshots. On Monterey, right-click the volume and look for the same option.
  5. A sheet lists all snapshots. Select the Time Machine entries and click Delete.

Disk Utility requires no Terminal knowledge, but it does not filter snapshot types — be careful not to delete snapshots that belong to other tools (e.g., Arq, Carbon Copy Cloner) unless you intend to.

Method 3: One-Click with Crumb

If you would rather not open Terminal or navigate Disk Utility, Crumb handles snapshot removal as part of its standard Clean sweep. Crumb is a native macOS menu-bar app that clears System Data — caches, logs, temp files, and local Time Machine snapshots — with a single click, and shows you exactly what was removed and how much space was recovered.

  1. Download and install Crumb.
  2. Click the Crumb icon in your menu bar.
  3. Click Clean. Crumb scans for purgeable space including local snapshots and presents a summary before removing anything.
  4. Confirm, and Crumb removes the snapshots along with other safe-to-clear System Data.

This is the right choice if snapshots are just one part of a broader "my disk is full" problem — Crumb clears caches, logs, and temporary files in the same pass, so you see the full picture in one place rather than running half a dozen Terminal commands.

Comparison: Which Method Should You Use?

Method Control level Requires Terminal Removes other junk too Best for
tmutil (Terminal) Per-snapshot precision Yes No Developers, power users, scripting
Disk Utility All-or-nothing per volume No No Users who avoid Terminal but want GUI control
Crumb (one-click) Automatic safe selection No Yes Quick full clean when disk is generally full

Is It Safe to Delete Local Snapshots?

Yes, with one important caveat: confirm you have a working external or network Time Machine backup (or another backup strategy) before you delete local snapshots. Open Time Machine preferences and verify the "Latest Backup" date on your external drive is recent. If you rely solely on local snapshots as your only backup — which Apple discourages — you will lose that recovery option after deletion.

Assuming you have an external backup, removing local snapshots is permanent but harmless to your current files. Nothing on your disk changes; you are only removing historical checkpoints stored inside the APFS snapshot layer.

How Much Space Will You Recover?

This varies widely. On a MacBook that travels frequently and rarely connects to a backup drive, local snapshots can accumulate to 20–80 GB over several weeks. On a Mac that backs up nightly, macOS tends to prune older snapshots automatically, so you may recover only a few gigabytes. The tmutil listlocalsnapshots / output shows you the count; for sizes, run:

tmutil listlocalsnapshotdates / | tail -n +2 | while read d; do
  tmutil localsnapshot info "$d" 2>/dev/null
done

Note that because APFS snapshots use copy-on-write, the size of each snapshot is proportional to how much changed since the previous one — a snapshot from a quiet overnight period may be only a few hundred megabytes, while one taken just before a large file operation can be much larger.

Preventing Snapshot Buildup

If you never want local snapshots to accumulate, you can disable the feature entirely:

sudo tmutil disablelocal

This is a permanent change. Re-enable with sudo tmutil enablelocal. Disabling local snapshots means Time Machine will only protect your files when your external drive is connected — weigh that trade-off against the reclaimed space.

Conclusion

Local Time Machine snapshots are one of the most overlooked sources of "missing" disk space on modern Macs. All three methods covered here — tmutil deletelocalsnapshots for surgical control, Disk Utility for a GUI approach, and Crumb for a one-click full clean — work correctly on macOS Monterey through macOS 26. Pick whichever fits your comfort level, confirm your external backup is current first, and you will have your storage back in minutes.

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

Is it safe to delete Time Machine local snapshots?
Yes, as long as you have a working external or network Time Machine backup. Local snapshots are separate from your main backup; deleting them removes hourly recovery checkpoints stored on your internal drive but does not affect any files on your disk.
How do I delete all local Time Machine snapshots at once in Terminal?
Run this loop in Terminal: for snap in $(tmutil listlocalsnapshots / | grep -oE '[0-9]{4}-[0-9]{2}-[0-9]{2}-[0-9]{6}'); do tmutil deletelocalsnapshots "$snap"; done — no sudo required on macOS Monterey and later.
Why does Disk Utility still show Purgeable space after deleting snapshots?
APFS can take a minute or two to update its storage metadata after snapshot deletion. If the number persists, run 'diskutil apfs listSnapshots <volume>' in Terminal to confirm the snapshots are gone, then wait for Finder to refresh its storage summary.
Will deleting local snapshots speed up my Mac?
Indirectly. Recovering purgeable space reduces the likelihood of macOS throttling writes due to low storage. You may notice snappier app launches and fewer 'Disk Full' warnings, but snapshot deletion itself does not change CPU or RAM performance.
Can I stop Time Machine from creating local snapshots in the future?
Yes. Run 'sudo tmutil disablelocal' in Terminal to permanently stop local snapshot creation. Re-enable it with 'sudo tmutil enablelocal'. Note that disabling this means Time Machine will only back up when your external drive is connected.