Free Up SSD Space on a 256GB MacBook: Reclaiming Gigabytes from Time Machine Local Backups

If your 256GB MacBook constantly reports a full or near-full drive despite deleting files, Time Machine local snapshots are often the hidden culprit. macOS silently stores rolling snapshots directly on your internal SSD, and on a small drive those snapshots can consume anywhere from 10GB to 60GB of space that looks, from Finder's perspective, like it belongs to "System Data." This article shows you exactly where that space goes, how to measure it, and how to reclaim it without losing real backups.

Why Small SSDs Get Hit the Hardest

Time Machine local snapshots (formally called APFS local snapshots) are a convenience feature. When your external Time Machine drive is not connected, macOS keeps hourly snapshots on your internal disk so you can still restore recent versions of files. On a 1TB or 2TB MacBook, this is largely invisible. On a 256GB or 512GB drive it becomes a space management problem in disguise.

macOS is supposed to purge old snapshots automatically when free space runs low, but in practice that threshold is conservative. You can have 5GB free on disk while macOS quietly holds onto 30GB of snapshots it considers "purgeable." Purgeable space is not free space. Finder shows it as used, many apps treat it as used, and you cannot write into it directly.

The small-SSD situation is worse for a few reasons:

• Snapshots are taken hourly. Even light use generates many snapshots per day.
• On a small drive, even a 5GB snapshot delta represents a meaningful percentage of total capacity.
• macOS does not aggressively expire snapshots until the drive is critically full, often under 1GB free.
• iCloud Desktop and Documents sync can cause large file churn, which inflates snapshot size further.

How to See Your Current Snapshots

Before deleting anything, measure the problem. Open Terminal (Applications > Utilities > Terminal) and run:

tmutil listlocalsnapshots /

You will get a list of snapshot identifiers like:

com.apple.TimeMachine.2026-06-09-081523
com.apple.TimeMachine.2026-06-09-091523
com.apple.TimeMachine.2026-06-09-101523

To see the total space they occupy, run:

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

That command is verbose. For a faster estimate, use df and compare it against what About This Mac reports:

df -h /

The Available column here reflects purgeable space as genuinely available. Compare it to Storage in Apple menu > System Settings > General > Storage. If those numbers differ by more than a few gigabytes, snapshots are part of the discrepancy.

For a per-snapshot size breakdown on macOS Sonoma or Sequoia (and Tahoe), the cleanest approach is:

tmutil listlocalsnapshots / -m

The -m flag shows sizes in machine-readable format. On Sonoma 14 and later this flag may output sizes inline. If it does not on your build, fall back to the diskutil approach below.

Reclaim SSD Space: Three Methods That Actually Work

Method 1: Delete All Local Snapshots at Once (Fastest)

If you have an external Time Machine backup that is current, you do not need local snapshots at all. Deleting them frees the space immediately and macOS will resume creating new ones the next time your backup drive is disconnected.

for snap in $(tmutil listlocalsnapshots / | grep "com.apple"); do
  sudo tmutil deletelocalsnapshots "$snap"
done

Run this in Terminal, enter your password when prompted, and wait. On a drive with many snapshots this can take a minute or two. When it finishes, open System Settings > General > Storage and refresh. The System Data bar typically shrinks noticeably.

If you want to delete a single snapshot instead, pass its full identifier:

sudo tmutil deletelocalsnapshots com.apple.TimeMachine.2026-06-09-081523

Method 2: Disable Local Snapshots Entirely

If you always keep your Time Machine drive connected, or you use a NAS for backups and snapshots provide no benefit to you, you can turn off local snapshot creation:

sudo tmutil disablelocal

Note: on macOS Monterey and later, disablelocal is no longer a standalone command in the same way. The recommended approach on Ventura, Sonoma, Sequoia, and Tahoe is to disable Time Machine entirely if you do not use it (System Settings > General > Time Machine, then remove all backup destinations and toggle Time Machine off). Snapshots stop being created when Time Machine has no active backup destination configured.

If you still want Time Machine running but want to limit snapshot frequency, there is no built-in GUI slider for snapshot interval. Third-party tools can modify the schedule via launchd plist edits, but that is beyond most users' comfort level and not necessary for reclaiming current space.

Method 3: Use Disk Utility to Confirm APFS Purgeable Space

Open Disk Utility (Applications > Utilities > Disk Utility), select your internal volume (usually "Macintosh HD"), and look at the bar at the bottom of the window. In Sonoma and Sequoia, it breaks down Used, Purgeable, and Available space. If the Purgeable block is large (more than 5GB to 10GB on a 256GB drive), you can trigger an OS-level purge without deleting snapshots manually by running:

sudo purge

This flushes disk cache and signals macOS to convert purgeable space to free space. It does not always reclaim snapshot space fully, but it is safe to run and often frees several gigabytes of cache on top of whatever snapshots get expired.

Other System Data Culprits on a Small SSD

Snapshots are the single biggest surprise in System Data, but they are not the only one. On a 256GB MacBook full scenario, also check these locations:

• iOS device backups: Stored at ~/Library/Application Support/MobileSync/Backup/. Each iPhone backup can be 10GB to 60GB. Delete old backups in System Settings > General > Storage > (scroll to Backups) or via Finder.
• System caches: Located at /Library/Caches/ and ~/Library/Caches/. Most are safe to clear, though macOS and apps will rebuild them. Do not delete individual app cache folders while the app is running.
• Log files: Found at /var/log/ and ~/Library/Logs/. Diagnostic reports in ~/Library/Logs/DiagnosticReports/ can accumulate into the gigabytes on older machines.
• Xcode derived data: If you use Xcode, ~/Library/Developer/Xcode/DerivedData/ is notorious for growing to 20GB or more. Delete the contents of that folder freely; Xcode rebuilds it on the next build.
• Mail downloads: ~/Library/Mail/V10/ (version number varies) stores all message bodies and attachments locally. If you use iCloud Mail or IMAP with "Keep all messages" turned on, this can grow large.

Building a Routine for 256GB MacBook Space Management

Reclaiming space is only half the job on a small SSD. The other half is keeping it from filling back up. A simple monthly routine:

1. Connect your Time Machine drive and let a full backup complete before touching anything.
2. Run tmutil listlocalsnapshots / to see how many local snapshots have accumulated.
3. Delete snapshots older than 48 hours using the loop command above, or delete all of them if you are confident in your external backup.
4. Open System Settings > General > Storage and review the Recommendations section. macOS will flag large files, old iOS backups, and unused apps.
5. Check ~/Library/Developer/Xcode/DerivedData/ if you code. Clear it monthly.
6. Empty the Trash if you have not recently. Files in Trash still count against your quota.

If you want a faster view of what is actually large on your drive, a whole-disk space map is the quickest way to spot outliers. Crumb includes a disk map built specifically for this workflow: it shows your full volume broken down by folder size, flags caches and snapshots as reviewable items, and lets you confirm what is safe to remove before anything is deleted. It runs entirely on-device and does not need an account, which matters when you are handing it access to your full file tree.

Frequently Missed Setting: iCloud Optimized Storage

If you use iCloud Drive with Optimize Mac Storage turned on (System Settings > Apple ID > iCloud > iCloud Drive > Optimize Mac Storage), macOS will evict files to iCloud to free local space. This is helpful in theory. In practice, it interacts awkwardly with Time Machine: snapshots may capture stubs of evicted files rather than their full content, and iCloud syncing creates additional file churn that inflates snapshot deltas.

On a 256GB MacBook, the recommended setup is:

• Enable Optimize Mac Storage so large files move to iCloud when space is tight.
• Keep Time Machine connected regularly so snapshots stay small and fresh rather than accumulating a week of deltas.
• Set a reminder to purge local snapshots monthly, especially after you have been traveling without your backup drive.

The reclaim ssd space local snapshots workflow above, combined with a clear picture of what is actually large on your drive, usually recovers 15GB to 40GB on a 256GB MacBook that has been running for a year or more without manual cleanup. That is often enough to go from "disk almost full" warnings back to comfortable headroom without buying more storage or deleting anything you care about.