Disclosure up front: Purplelink, which publishes this site, makes one app mentioned near the end, Legroom. On November 16, 2026 I ran tmutil listlocalsnapshots / and df -h / on my own Mac (macOS 27.0.1). It had no local snapshots, so I did not measure a snapshot size, a clone size or a Carbon Copy Cloner snapshot. Everything about those comes from Apple, Bombich Software (the maker of Carbon Copy Cloner) and Howard Oakley's Eclectic Light blog, and each source is linked where I use it.
The short answer
Files live in blocks (the fixed-size pieces of disk a file is stored in). Deleting a file releases its blocks only if no other item still points at them. A snapshot (a read-only copy of a volume as it was at one moment) points at the blocks of every file the volume held then. A clone (a copy that shares blocks with its original) points at the same blocks as the file you kept. Both leave the space in use after the deletion.
Work through the five checks below in order. The first two take a minute, and none of them deletes anything.
1. Empty the Trash
Moving a file to the Trash does not free its space. In Finder, choose Finder, Empty Trash. Apple's page on freeing storage also describes a setting that erases items that have been in the Trash for more than 30 days, which you can turn on in Finder settings.
To see whether the space came back, run df -h / in Terminal before and after. It prints one line for the startup volume and changes nothing. If the Avail column did not move after you emptied the Trash, continue to the next check.
2. Local snapshots on the startup disk
Time Machine keeps some backups on your Mac itself. Apple says it saves about one snapshot of the startup disk each hour and keeps each for 24 hours, and that your Mac counts the space used by snapshots as available storage. Howard Oakley explains why that matters after a deletion: a file's original blocks still have to be retained for the snapshot, so they stay until the snapshot itself is deleted.
Check. Run tmutil listlocalsnapshots / in Terminal. It lists the snapshots on the startup volume and changes nothing. On my Mac it printed the header "Snapshots for disk /:" and no snapshots, which is why I have no size to show you. For sizes, open Disk Utility, choose View, Show APFS Snapshots and select the volume in the sidebar. Apple's Disk Utility page says the table at the bottom of the window can show columns named Private Size and Cumulative Size. I could not test those columns for the same reason.
What to do. Usually nothing. Apple says Time Machine removes snapshots as they age or when other tasks need space. Apple's documented way to clear them by hand is to turn off automatic backups in Time Machine settings, wait a few minutes, and turn them back on. The tmutil man page also lists deletelocalsnapshots. I did not run it. The System Data guide covers snapshots as one cause of a large System Data figure, and this guide starts from the other end, with a deletion that freed nothing.
3. Snapshots on an external disk
A snapshot is a feature of the APFS file system (Apple's file system for Macs), so any APFS volume can hold them, including an external one. Carbon Copy Cloner (CCC) is a backup app that makes its own. Bombich's documentation for CCC 6 says a snapshot keeps references to files, so "space is not freed when you delete a file" until the snapshot is deleted. That page describes an older CCC version, and its menus may differ in the current one.
Check. Open Disk Utility, choose View, Show APFS Snapshots and select the external volume in the sidebar. Apple's page says the snapshots of the selected volume appear in a table at the bottom of the window. If you use CCC, open its Snapshots table for that volume.
What to do. Delete a snapshot in the app that made it. In CCC's Snapshots table, select the snapshot and press the Delete key. Bombich says CCC never deletes snapshots made by other applications during its automatic thinning, and that you can remove them by hand the same way. Disk Utility offers a Delete Snapshot button for a selected snapshot. Oakley warns there is no undo, so check what a snapshot belongs to before you delete it, and leave alone any snapshot that a backup you rely on needs.
4. APFS clones
When you copy or duplicate a file in Finder, macOS tries to clone it, which works when the original and the copy are on the same APFS volume. In Terminal, cp -c asks for a clone too (the cp man page says it uses clonefile(2) and falls back to a normal copy if the disk cannot clone). A clone shares its blocks with the original until you edit one of them.
This explains a deletion that frees nothing. Oakley writes in his post on duplicate files that clones never took space of their own, so you get none back when you remove one. Finder's Get Info still reports each clone as if it took its full size, which is why a folder can look large and free little when you empty it.
Check. Compare two numbers. Finder's Get Info shows the size of the folder you deleted or kept, and Disk Utility shows the volume's used space. Oakley reports that Disk Utility shows no increase in used space when clones are made, while Finder adds them up. I did not make clones on my Mac to test this.
What to do. Nothing needs fixing. The space was never used twice, so there is nothing to recover. Deleting both copies frees the shared blocks, if no snapshot or other clone still holds them.
5. Purgeable space
Purgeable space is space that macOS can reclaim when it needs room. Apple says macOS clears caches and logs that are safe to delete, such as temporary database files and interrupted downloads, when your Mac needs space. Oakley tested a nearly full boot volume and found that purgeability is a potential: the space is not freed until macOS identifies and reclaims it, and he advises not to count on it.
Check. Open Disk Utility and select the startup volume. It reports a purgeable figure beside the free figure. A freshly deleted file's space may sit in that figure for a while instead of in free space.
What to do. Wait, or keep working. macOS reclaims it when something needs the room. I found no Apple instruction for forcing it, so I do not offer one.
Where Legroom fits
Legroom is a menu-bar app that shows free space on the startup disk and cleans folders you choose. It is $9.99 once after a free 7-day trial, and I make it. Three of its features bear on this problem.
- Space Map. It draws where space goes on the disk as a sunburst chart (rings of folders sized by what they hold), so you can find the folder that is still large.
- Find Files. It lists large, old and duplicate files. For duplicates it always keeps one copy, and it moves files to the Trash only.
- What Grew. It shows that local Time Machine snapshots exist, with the dates of the oldest and newest when macOS reports them, and it never deletes a snapshot (Legroom's own README). It shows no size for them: its text says macOS does not report their size. Disk Utility's snapshot table, described above, is where to look for a figure.
This guide makes no claim about how Legroom treats clones, and Legroom cannot release space that a snapshot or a clone still holds. Every command above is free, and you do not need an app to run them. Legroom's page has the details, and the guide on disk space analyzers for Mac compares it with other tools.
Frequently asked
Why did deleting 35 GB free nothing on my Mac?
A deleted file frees its space only when nothing else still refers to it. Five things can keep a reference: files still in the Trash, a Time Machine local snapshot on the startup disk, a snapshot on an external disk, an APFS clone (a copy that shares its data with the original), and purgeable space that macOS has not yet reclaimed. Work through the checks in this guide in that order.
Is it safe to delete local snapshots?
Time Machine removes them as they age or when other tasks need the space, so you rarely need to. Apple's documented way to clear them is to turn off automatic backups in Time Machine settings and wait a few minutes. A snapshot deleted in Disk Utility cannot be restored (Eclectic Light says there is no undo), so delete only a snapshot whose maker you know.
Does deleting a duplicate file free space?
Often not. When you copy or duplicate a file in Finder on the same APFS volume, macOS tries to clone it, and the clone shares its data with the original. Howard Oakley of Eclectic Light writes that a clone never took space of its own, so you get none back when you remove it. Finder's Get Info still shows each clone at its full size.
Related guides
- Why is System Data so big on my Mac? What fills it and what is safe to remove: snapshots as one cause among several, and the other folders to check.
- Best disk space analyzer and cleaner for Mac (2026): the tools that show where the space went.
- Show free disk space in the Mac menu bar: the free number in view, and how the built-in views differ.
- Legroom, all products and all guides.