Time Machine local snapshots using up all disk space

I’m having issues with hourly Time Machine local snapshots holding on to very large deleted video files (13g to 26g), resulting in the system running out of disk space. Although it will say I have about 15g free, I can’t even save a small document, and apps start crashing. I kept deleting more and more of these large video files, but the amount of memory free would not go up. I tried a reboot and it never completed. I eventually booted into target disk mode to recover files. At that point I also deleted all the Time Machine local snapshots. That seemed to fix the problem and I was able to reboot and have about 200g free, but then it happened again. I should have had nearly 200g free, but it was back down to 15g until I deleted the snapshots again.


My work flow is to edit the video files on the internal HD from within a folder that is excluded from Time Machine backups. I then copy these large video files one at a time to an iCloud Drive folder that is also excluded from Time Machine backups. Sometime after it is done uploading I do a “remove download” and I also delete the copy on my local hard drive. At this point all disk space associated with the large video file should be free, but apparently it is not. When Time Machine does an hourly local snapshot, it will still capture these large files in the snapshot if I have not deleted them yet, and the snapshots will hold onto them after deleting the files. This is true even if the files are excluded from Time Machine backups.


Due to my workflow and working on many of these large video files in a day, it really easy for me to end up with nearly 200g of deleted video files tied up in hourly Time Machine local snapshots. Is there any way to avoid this? Shouldn’t these snapshots be getting purged automatically when disk space runs low? And why, when I have 15g free, does macOS acts like I have no space available?

iMac 27″, macOS 12.7

Posted on Feb 26, 2025 4:15 PM

Reply
13 replies
Sort By: 

Feb 27, 2025 8:38 PM in response to cjp987

Time Machine local snapshots temporarily retain deleted files, even if they’re in excluded folders. macOS should automatically purge snapshots when space runs low, but in some cases—especially with large files like video—it doesn’t happen quickly enough, leading to the system running out of space. Since you’re constantly working with large video files and deleting them, these snapshots keep holding onto the space until manually removed. You can try disabling local snapshots altogether with sudo tmutil disablelocal in Terminal, or regularly purge them using tmutil deletelocalsnapshots <date>.


Another workaround is ensuring you have sufficient free space before starting a new project, as macOS treats low disk space differently than you’d expect, making even small tasks impossible when it thinks storage is critical

Reply

Feb 27, 2025 9:25 AM in response to cjp987

It seems you don't have enough internal storage for your workload since video editing does require a lot more Free storage space than most other workloads.


In the mean time you can have TM only back up automatically once a day. You can always force another manual TM backup at any time by clicking on the TM icon on the menu bar. With this option, I have only seen three TM snapshots at any one time (usually just two though if you don't force a manual backup). If you know the backups have successfully transferred to the external backup drive, then you can manually delete those snapshots....you could probably script that if needed at least to save a bit of time to open Disk Utility & click delete.


You can use third party backup software such as Carbon Copy Cloner (CCC) which may have more & better configuration options for you such as possibly configuring how long local snapshots are retained.


Most backup software will be using the APFS snapshotting capabilities. The snapshots can only take the complete volume.....there is no cherry picking which items are retained at this stage. The exclude from backup option is only excluding the transfer of those files/folders from the local snapshot to the actual TM backup drive.


FYI, @Luis Sequeira1 is correct that the Free storage space value is the only important storage value these days, but unfortunately Apple & macOS only show the extremely misleading "Available" storage value everywhere. The actual Free space is only shown in the System Profiler or in Disk Utility. With macOS Free and Available are not even close to being synonyms.


Free space = Available space - Purgeable space


Purgeable storage will be automatically deleted at some unknown time in the future. Local backup snapshots are part of that Purgeable storage. TM snapshots are usually automatically deleted every 24 hours or so.


You can always provide Apple with product feedback here:

Feedback - macOS - Apple



Reply

Feb 28, 2025 5:54 AM in response to cjp987

Are you editing whilst disconnected from your backups?


Connecting to the TM storage either locally or on NAS should avoid most snapshots.


Given the usage and hardware configuration, maybe use some other backup strategy (strategies), and turn off Time Machine:

About Time Machine local snapshots - Apple Support


Using a NAS (with Time Machine server support) might be your best lesson-bad option here, too. Options include TrueNAS and Synology.

Reply

Feb 28, 2025 8:24 AM in response to MrHoffman

MrHoffman wrote:

Are you editing whilst disconnected from your backups?

Connecting to the TM storage either locally or on NAS should avoid most snapshots.

Given the usage and hardware configuration, maybe use some other backup strategy (strategies), and turn off Time Machine:
About Time Machine local snapshots - Apple Support

Using a NAS (with Time Machine server support) might be your best lesson-bad option here, too. Options include TrueNAS and Synology.

I have 4 backup volumes (I like redundancy) and two of them are always remote (so not connected). I'm not sure why for a while I got all the local snapsots. I'm not getting them now, but the iCloud Drive issues are separate from Time Machine and perist. I think maybe the snapshots happened after I ran out of disk space due to iCloud Drive unintended downloads. This caused TM backup failures. TM was putting up messages saying it failed to backup because I was out of space (on the main disk, not the TM disk). Possibly this failure to backup caused local snapshots to be created instead. Then when I deleted all the iCloud Drive downloads, the snapshots were still around to hold onto the space they were occupying.

Reply

Feb 27, 2025 3:25 AM in response to Luis Sequeira1

Luis Sequeira1 wrote:

Open Disk Utility.
You should see all the local snapshots in there. Select and click the "-" button to delete.

My question was not how to delete the snapshots. In fact I think I made it clear that I had deleted them. My question is how to prevent snapshots from holding on to references to large files that have been deleted, and doing so even as my disk runs out of space. I'm getting app crashes and the inability to even save small files. Going into Disk Utility to delete the snapshots (which I have been doing) to fix this should not be something a user needs to do. I would disable local snapshots if I could. They serve me no purpose and cause too much grief.

Reply

Feb 27, 2025 3:39 AM in response to cjp987

Thank you, I admit I read your post a bit too quickly.


Before anything else: running your system with about 15GB free is dangerous. Any drive needs to have at least 15-20% free space, especially if it is the system drive. I would not want to save anything, or use the drive if it is that full.


That said, I am not convinced that snapshots are the problem here. Besides the matter with snapshots, it happens that macOS is very eager to keep disk space as "available" instead of "free", which is unfortunate.

I'd like to have an easy way to free disk space, but macOS prefers to do it on its own time, even if the free space is dangerously low (as is the case here).


Reply

Feb 27, 2025 4:08 AM in response to Luis Sequeira1

Luis Sequeira1 wrote:

Before anything else: running your system with about 15GB free is dangerous. Any drive needs to have at least 15-20% free space, especially if it is the system drive. I would not want to save anything, or use the drive if it is that full.

That said, I am not convinced that snapshots are the problem here. Besides the matter with snapshots, it happens that macOS is very eager to keep disk space as "available" instead of "free", which is unfortunate.

It's definitely the snapshots. I've gone in and looked at their contents and found the large files that have otherwise been deleted from the disk.


I'm not attempting to run with 15gb free. I try to keep a lot more than that free (100 to 200gb) by aggressively deleting these large files. But TZ snapshots prevent the space from actually getting freed.


It's odd that when both times I ran into this, I had 15gb free and at that point macOS basically decided I could no longer do disk writes. I couldn't even touch a file to create it. Although snapshots are holding onto a lot of disk space at this point, it seems that there is also something else going. The disk is in an an APFS container that also has two other volumes (they weren't mounted). Could that be resulting in some sort of 15gb reservation that prevents my main disk from accessing that free space.


It's also odd that macOS is not purging the purge-able disk usage when this situation arises.

Reply

Feb 27, 2025 12:08 PM in response to HWTech

The interaction with iCloud Dirve seems to also have a lot to do with some of my issues. I was up to 200gb free yesterday. Now I'm down to 110gb without having added new large files. TZ only has one local snapshot (which is oddly low) which is almost 24 hours old. It only uses about 10gb, and this is the same as the purgable amount in shown in Disk Utility. So were did I lose this nearly 90gb of memory to? I went searching and found it here:


/Users/<user>/Library/Caches/CloudKit/com.apple.bird/<hash>/MMCS/ClonedFiles


Based on the sizes of the large files I see in this directory, they are the large video files that I had copied to the iCloud Drive, and then did a "remove download" on once they were uploaded. I also see them in my wife's account. I had noticed a couple of days ago that even though from that account the iCloud Drive was never accessed, downloads happened anyway. I had removed all the downloads and then yesterday noticed a couple came back, so I turned off iCloud Drive since her account doesn't need it on. So iCloud Drive is now disabled, yet has 40gb in this cache still. I wonder if these are "orphaned" caches that iCloud Drive doesn't know it no longer needs.

Reply

Feb 27, 2025 1:27 PM in response to cjp987

In the past hour the amount of free and purgeable space increased by 40gb (I've done nothing to instigate this), which is the same size as the iCloud Drive cache files for the account that still has iCloud Drive enabled. The files are still in the cache. Seems some accounting was done to suddenly start including them in the free and purgeable sizes, but not to actually get rid of them. For the account that has disabled iCloud Drive, the files are also still present, but haven't been added back into the free and purgeable sizes yet.

Reply

Feb 27, 2025 11:07 PM in response to MacDataSaviour

Yeah, it seems this all takes a lot of proactive management. iCloud Drive is just compounding the problem. With it's persistent re-downloading of files that I don't want downloaded, accidental downloads, and sticky caches, I'm constantly playing wack-a-mole. And macOS seems to always being playing catchup trying to figure out how much "available" and "purgeable" space there really is. Available bounced up to about 250gb today during my cleanup attempts, which was clearly too high, then it went down to about 200gb, which I think was correct, and now 160gb, I think because iCloud Drive has created another 40gb cache on my wife's account. Time to go clean that up.

Reply

Feb 27, 2025 11:50 PM in response to cjp987

I think I'm done with keeping iCloud Drive enabled on my wife's account. I wanted to get it working, but just can't stop the repeated downloads. It always wants to load about 60gb of these large video files that are in a shared folder. I wait until it's done, "remove download" on them all, and it just starts up again. It's not all of the video files (that would be about 275gb), but it's always the same ones. I've tried turning iCloud Drive off and then back on numerous times, but it always eventually restarts the downloads. I've also tried the following, which seems to have helped a lot of people in a similar situation, but not me:


cd ~/Library/Application\ Support

killall bird && rm -rf CloudDocs


I did this with iCloud Drive off and when I started it up again it began doing the downloads. I have one more thing to try. I'm going to unsubscribe her from the shared folder and then subscribe again and see what happens. If that fails, then maybe unsubscribe and create a new shared folder to put the videos in.

Reply

Feb 28, 2025 11:26 PM in response to cjp987

Well I figured out why I wasn't getting snapshots anymore. It's because I had (temporarily) disabled time machine while attempting to get the disk space usage under control. Now that it is back on I'm getting snapshots. I do have two TM volumes attached, but I suspect that it is the two that I don't have attached that result in the snapshots being created and sticking around for 24 hours.

Reply

Time Machine local snapshots using up all disk space

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.