Delete Time Machine Backups on Mac: Local Snapshots and Backup Disks
Updated: September 26, 2026
Before deleting a Time Machine backup, identify which disk is short of space. Local snapshots live on the Mac; backup history can live on an external or network destination. Clearing one does not necessarily free space on the other, and deleting an entire backup volume is very different from removing a single restore point.
For local snapshots, macOS normally manages the space automatically. For an external backup problem, start with the destination and the exact Time Machine error instead of copying a generic deletion command.
Identify the storage you want to reclaim
| What you see | Where to investigate | What deletion would affect |
|---|---|---|
| Low space on the Mac’s startup disk | Storage settings and local snapshots | Local file history, not necessarily external backups |
| Backup destination full | Time Machine settings and that destination’s capacity | Older external backup history |
| A large network backup image | The configured network destination and its quota | Potentially the Mac’s entire network backup set |
| An unused old backup disk | Disk Utility and the disk’s contents | Erasing it removes more than one dated backup |
Record the volume name, capacity and connection type. If two disks have similar names, disconnect the one you do not intend to manage before making a destructive choice. First confirm that important files exist somewhere other than the history you intend to remove.
Local snapshots are not ordinary duplicate folders
Time Machine local snapshots preserve earlier file states even when the backup destination is unavailable. Apple says their storage is counted as available space and snapshots are removed as they age or space is needed. A large snapshot listing therefore does not automatically mean your Mac cannot use that capacity. Apple’s local-snapshot explanation.
Do not expect the sizes displayed for individual restore points to add up to the exact space a deletion will recover. Shared storage and accounting make fixed “gigabytes per day” estimates unreliable. This article does not repeat the earlier unsupported 200 GB test result or storage-recovery table.
Temporarily pause automatic backups to clear local snapshots
Apple documents this approach when you specifically want to remove local snapshots:
- Open System Settings → General → Time Machine on macOS Ventura or later.
- Open Options and change Backup Frequency to Manually.
- Allow a few minutes for local-snapshot cleanup.
- Restore your preferred automatic backup schedule.
On older macOS versions, the corresponding control may be Back Up Automatically in Time Machine preferences. This process concerns local snapshots; it is not a way to delete an external backup archive. Apple’s instructions.
Inspect APFS snapshots in Disk Utility
Open Disk Utility, choose View → Show APFS Snapshots, and select the intended APFS volume. Review the snapshot list, dates and available size information. Apple documents selecting a snapshot row and using Delete Snapshot where deletion is available. Use that snapshot control, not Erase or Delete Volume. Disk Utility snapshot guide.
Not every snapshot is a disposable Time Machine restore point. Identify what it belongs to before deleting it, and do not force a protected or in-use snapshot to disappear. Removing a restore point also removes that recovery option; confirm another usable backup first.
The original screenshot is preserved for context. Controls differ by macOS release and backup format; a legacy menu is not a universal instruction for modern APFS backups.
When the external backup destination is full
Check the selected destination in Time Machine settings and read the exact failure message. Distinguish a genuinely full volume from an unavailable disk, network quota, permissions problem or interrupted backup. Those problems do not all call for deleting history.
If you need more long-term retention, consider a larger destination rather than removing restore points one by one. Keep the old backup available until a new backup has completed and you have checked that required files can be recovered.
The older Finder instructions assumed a Backups.backupdb folder layout. Modern backup formats do not all use that layout, and deleting arbitrary files inside a backup is not a general cleanup method. A network backup also needs its own destination-specific handling; do not treat its image file as an expendable download.
Terminal inspection before any advanced deletion
If you use Terminal, first consult the manual installed with your macOS version:
man tmutil
tmutil destinationinfo
tmutil listbackups
tmutil listlocalsnapshots /These commands provide documentation and inventory, not a deletion recipe. Read the installed manual’s requirements for the specific backup format and operation. The old article’s positional tmutil delete example should not be pasted into a different macOS version without confirming its supported syntax.
Do not prepend sudo to every command as a substitute for diagnosis. Permission errors can involve the chosen destination, privacy permissions or the operation itself. Preserve the exact error and stop if you cannot establish the target.
Local-snapshot thinning and deleting external backup history are separate tasks. The former article’s suggestion to run a local-snapshot thinning command against an external backup path did not establish that it would remove the intended backup set.
Retiring an entire backup volume
Only erase a backup volume when you intend to discard all of its contents and have another verified copy of anything you need. Check the disk and volume identity in Disk Utility and review the confirmation dialog carefully. A volume, a container and a physical disk are different targets.
Apple’s APFS volume-management guide explains the difference between erasing a volume and deleting it. This is not selective dated-backup cleanup, and it should not be the first response to an unexplained backup error.
Verify the result and resume protection
Recheck available space on the same volume you investigated at the start. Restore automatic backups if you paused them, reconnect the destination and confirm that a new backup completes. Browse the backup history and verify a non-sensitive sample file can be recovered to a separate location.
If free space does not change as expected, do not immediately delete more. Revisit which volume owns the snapshots or files and whether storage accounting has refreshed. The useful outcome is adequate working space and a functioning backup, not just a shorter list of restore points.