Home  â€º  Articles

Time Machine vs APFS Snapshots

Updated 2026-07-26  Â·  3 min read

Plenty of people believe they have no backup because no external drive is connected. Their Mac has been quietly taking hourly snapshots the whole time. Those snapshots are useful, they aren't a backup, and the difference matters.

Since APFS arrived, Time Machine has done two separate things that get confused with each other.

The two mechanisms

Time Machine backups

Copies of your data written to a different physical device: an external drive, a network volume, a Time Capsule. Survives disk failure, theft and liquid damage, because the copy is somewhere else.

APFS local snapshots

Point-in-time references stored on the same internal drive, taken roughly hourly whenever Time Machine is enabled, whether or not a backup destination is connected. Retained for about 24 hours and thinned automatically when space runs short.

A snapshot isn't a copy. It is a record of what blocks looked like at a moment in time. Unchanged data is shared with the live file system rather than duplicated, which is why snapshots start cheap and grow as files change.

The critical distinction A local snapshot lives on the disk it protects. If that drive dies, the snapshots die with it. They are excellent for undoing a mistake you made an hour ago. They are worthless against hardware failure.

What snapshots are good at

That last one surprises people. Open Time Machine with no drive attached and you can often still restore from earlier the same day.

The storage cost

This is where snapshots collide with the storage confusion covered in purgeable space. Snapshots can hold many gigabytes, macOS counts that as available because it can reclaim it, and third-party tools count it as used.

See what you've:

tmutil listlocalsnapshots /

Ask macOS to free roughly 10 GB of it:

sudo tmutil thinlocalsnapshots / 10000000000 4

The final number is urgency, where 4 is the most aggressive. Usually you shouldn't need this. Worth knowing when an installer insists there's no space while Finder claims there's plenty.

Turning them off, and why you probably shouldn't

Local snapshots stop if you disable Time Machine entirely, which also stops real backups. That trade is rarely worth it. macOS already thins snapshots under pressure, and the protection they provide against your own mistakes is valuable.

If you're chronically short of space, the fix is a bigger drive or fewer files, not disabling a safety net.

See what your snapshots are holding

CleanMachine lists APFS snapshots with real sizes and creation times, so you can tell the difference between snapshots and files when storage gets tight. Free to scan.

↓ Download Free & Scan

What a real backup strategy looks like

  1. Time Machine to an external drive. Cheap, automatic, and it survives your internal disk failing.
  2. An offsite or cloud copy for anything you can't recreate. Fire and theft take the Mac and the backup drive sitting next to it.
  3. Local snapshots as a same-day undo, which you already have.

Snapshots are layer three. Treating them as layer one is the mistake, and it is an easy one to make because macOS never explains that they exist.

Common questions

Are APFS local snapshots the same as Time Machine backups?
No. Snapshots are stored on the same internal drive and protect against accidental changes. Time Machine backups are copies on a separate device and protect against drive failure, theft and damage.
Why does my Mac take snapshots without a backup drive?
Time Machine takes hourly local APFS snapshots whenever it is enabled, regardless of whether a destination is connected. They are kept about 24 hours and thinned automatically when space is needed.
Do snapshots use disk space?
Yes, often several gigabytes. macOS reports it as purgeable and reclaims it when space runs low, which is why Finder and command line tools can disagree about free space.
Should I delete local snapshots?
Usually not. macOS manages them automatically. Thin them manually with tmutil only when a large operation is failing for lack of space.

Keep reading