Mac Storage Says 254GB Available: Where Local Snapshots Fit
Settings says 254GB available, while a disk tool shows only about 60GB unallocated. Which number tells you how much you can actually store?
- Available and unallocated storage can describe different amounts on the same Mac.
- Local snapshots preserve recent recovery points while the backup drive is disconnected.
- Inspect and recover needed files before clearing local history, then restore automatic backups.
The missing clue in a 254GB-versus-60GB report
A Mac can report hundreds of gigabytes available while a disk tool reports far less unallocated space. The available figure can include storage macOS expects to reclaim, including local snapshots. Removing those snapshots need not increase a total that already counted their space as available.
In one MacBook Pro owner's Reddit report, macOS Tahoe showed 254.44GB available in Settings while the APFS container had about 59.9GB unallocated. The owner reported only two Time Machine snapshots and no enormous snapshot entry that obviously explained the gap.
A later comment supplied a more useful clue: Finder's information window showed 254.26GB available, including 194.64GB purgeable. Subtracting the purgeable figure leaves 59.62GB, close to the earlier unallocated figure. The subtraction separates the amount reported as purgeable from the reported available total.
The Settings and Finder totals are different reported values, and their timing and exact measurement scope were not established. The comparison supports a distinction between available and unallocated space. It does not establish that every purgeable byte belonged to Time Machine.
The same report's 56Gi figure from df should not be read as 56GB. A gibibyte uses powers of two; a gigabyte uses powers of ten. About 56GiB is about 60GB, so units help reconcile those two readings. They cannot explain the much larger difference between roughly 60GB and 254GB.
Compare the same storage object and the same kind of number
Apple's Disk Utility guide defines available space broadly enough to include both free and purgeable storage. To inspect the target, open Disk Utility, choose View → Show All Devices, select a disk, container, or volume, and open Info. Record the selected name along with the field label.
That selection matters because APFS volumes within a container share its free space. Similar free-space readings on two volumes are not two independent allowances you can add together. A system and data volume group also makes a familiar name such as Macintosh HD insufficient to identify every measurement.
| Reading | What it describes | What it does not establish |
|---|---|---|
| Available | Space considered usable, potentially including reclaimable storage | That all of it is already unallocated |
| Container unallocated | Space not allocated within that container | The full amount another interface may call available |
| System Data | A broad storage category for files outside more specific categories | The size of Time Machine snapshots alone |
For a simplified example, suppose a screen already counts 30GB of reclaimable storage inside a 100GB available total. Turning some of that reclaimable storage into unused storage does not necessarily create an additional amount to add to the total. The space moves from the reclaimable part of the available total to the already-unused part.
Use the same target and field for a before-and-after comparison. If an installation or copy was blocked, also retry that operation after making room. A changed storage bar and a successfully completed task are different observations, and recording both is more useful than repeatedly trying to force one display to increase.
What local history can recover
Time Machine local snapshots provide recent recovery points when the backup disk is disconnected. Apple describes roughly hourly snapshots retained for 24 hours, an additional snapshot of the last successful backup until space is needed, and snapshots before macOS updates on High Sierra 10.13 and later. These are not all entries with one identical expiration rule.
Imagine overwriting a proposal during an afternoon trip while its external backup drive is at home. A remaining local recovery point may help retrieve the morning version. If the required file is from last month, that short local history is a poor substitute for the longer history on the backup drive.
The location also determines the protection it offers. Local history is useful while the Mac's internal storage remains accessible. Losing the Mac or losing access to that storage also removes access to snapshots stored there. This is why local recovery and an external backup address different failure situations.
macOS removes snapshots as they age or when their space is needed, and counts their storage as available. When normal work is proceeding and recent recovery points are useful, the mere presence of snapshots is not a reason to clear them.
Inspect dates, then browse the files in Time Machine
In Disk Utility, choose View → Show APFS Snapshots, then select an APFS volume. The table below belongs to that volume. An empty table for one selection does not establish that every volume on the Mac lacks snapshots.
Use the snapshot table's column controls to show Date Created and Kind together. These help identify Time Machine entries around the date you need on the selected volume.
Finding a snapshot near the right time is only the start. The desired document must have existed at the relevant path and version. Use the recovery interface to inspect the file rather than assuming its contents from a snapshot's date.
For file recovery, open the Finder folder where the item belonged, launch Time Machine with Spotlight, move through the timeline or arrows, select the item, and choose Restore. Restored items return to their original location. Opening Documents first, for example, gives you the appropriate place to look for a missing document.
If the current edit is also valuable, preserve a separately named copy before restoring an earlier version. That leaves something to compare with the recovered file. Inspecting the available history before clearing it avoids discovering afterward that the recovery point you needed was among the ones removed.
Clear local snapshots through the supported setting
When you need to clear local history, Apple's documented method is to turn automatic backups off temporarily. On macOS Ventura 13 or later:
- Open System Settings → General → Time Machine.
- Under Options, set Backup Frequency to Manually, and select Done.
- Wait a few minutes for local snapshots to be removed.
- Return to the setting and enable automatic backups again.
On Monterey and earlier, the corresponding control is the automatic-backup checkbox or switch in Time Machine preferences. The configured backup disk is remembered. There is no need to erase or register it again to perform this procedure.
This clears local recovery history; it does not delete the video project, downloaded installer, or other current files that may occupy the disk. Nor does it guarantee that a particular available-space display will rise by a specified number of gigabytes. The display may already have included the reclaimable space.
Deleting a volume in Disk Utility removes its current data as well. The Time Machine procedure above instead clears local recovery history while retaining the current volume and remembered backup destination. Re-enabling automatic backups then resumes the schedule.
If the working files still do not fit
When a copy or installation still lacks room, investigate current files. Apple describes System Data as a general category for files that do not fit a more specific category. A large System Data bar is not a diagnosis that Time Machine is responsible for all of it.
On Ventura and later, open System Settings → General → Storage and inspect categories with information buttons. Downloaded installers, unused applications, and media you no longer need are concrete places to investigate. Moving an item to Trash does not complete its removal; empty Trash when you have decided to discard it. Files you need to retain may instead belong on another storage device.
For example, keeping an active video project's original media on the internal disk still requires space for that media after recovery history has been cleared. If each new project recreates the shortage, decide where completed projects should live. Repeated snapshot removal cannot replace that storage decision.
Reconnect the backup disk and check the latest completed backup or current progress in the Time Machine menu. Back Up Now can start a fresh backup. Knowing when the files you still need reached the external backup gives you a usable recovery point after local history has been cleared.