Inconsistencies in used and available storage space on MacBook Pro

Hi:


I am not technologically savvy, so I am sure I am using the phrase “leak” wrong.


But I have noticed some weird, inexplicable (to me) behaviour recently, and am hoping someone can help me out with an explanation.


Specifically, my Mac started running out of memory recently. Please see “Memory1” where there was only ~33GB of free space (it actually got much lower than that but I didn’t capture a screenshot). The Users folder only accounted for about 390 GB of the used memory. The System folder accounted for another 31GB, and the Applications and Library folders never calculated me a figure despite waiting 5 hours. “System Data” accounted for 653 GB!!!


Upon return to my computer the next day (“Memory 2”), all of a sudden I had 331 GB free space (an order of magnitude more) (at times I actually had closer to 400 GB free space, but again I didn’t think to snap a screenshot of that), and “System Data” had decreased to 398 GB.


No change in programs running between the two screenshots, just over night.


What is going on? Can someone explain this to me, or point me to a source that explains it in simple terms? I think a major system crash last week was due to a lack of memory. Is this a software thing, or should I be worried that there is a hardware issue with my RAM?


MacBook Pro, 14-Inch, 2021, Chip Apple M1 Max running MacOS 15.2.


Thank you very much!!!




[Re-Titled by Moderator]

MacBook Pro (2021)

Posted on Jan 27, 2025 11:07 AM

Reply
5 replies
Sort By: 

Jan 28, 2025 12:19 PM in response to CharPatton

In addition to @Camelot's excellent explanation, another possibility is that APFS backup snapshots are taking up that storage space. Depending on the app used for backups, these APFS snapshots may be automatically deleted about about a day or two, but some may stick around longer. Time Machine always leaves at least one APFS snapshot on the boot drive in order to allow the user to facilitate a quick restore the most recent version of files if needed especially if you don't have your backup drive at the time.


APFS snapshots can contain data you thought you already deleted as well. So if you tried to delete a large amount of data to make more Free storage space, then it won't make any difference until the APFS snapshot(s) that contain that data are deleted which will occur automatically usually about every day or so. You can see if you have any APFS snapshots by using the information in the following Apple article:

View APFS snapshots in Disk Utility on Mac - Apple Support


Storage on an APFS volume is complicated. There are other ways you could delete data, but not delete the data. If you made a copy of data onto the same APFS volume, then the data is not getting a second physical copy, but just a small link to the original physical data. In order to delete the physical data, you must delete all links to that physical data. This APFS feature was made to allow fast "copies" and to conserve the limited storage on SSDs and to help lessen the wear on an SSD.


Another tricky aspect of storage on macOS is the unfortunate use "Available" storage by Apple being shown nearly everywhere in macOS. The "Available" storage value is very misleading and should be avoided unless you take the time to do the math that @Camelot alluded to. The only critical and reliable storage value is the "Free" storage value which is only shown in Disk Utility and within the Apple System Profiler (silly Apple).


Free space = Available space - Purgeable space




Reply

Jan 27, 2025 12:34 PM in response to CharPatton

Things probably aren't as bad as you think.


The big question is what triggered your 'out of memory' warning, and whether that relates to storage space or RAM.


That's not to say there's no problem at all, just that what you're seeing may be perfectly normal.


I'm going to make some assumptions here, so bear with me, but I'll try to explain it in basic terms. First, I'll assume the 'out of memory' warning related to disk space and not RAM.


The second image you posted shows what I think is the 'normal' or 'true' state of your system - you have a ≈1TB drive and are using about 2/3rds of it (≈664GB). That's perfectly reasonable.


During normal usage, and when the OS does certain housekeeping activities, the OS automatically caches data - for example, if you recently searched for files, then the OS may cache, or 'remember' that search query in case you run it again... the subsequent query will use the cache and be much faster since the OS doesn't have to scan the entire disk again.

Similarly, individual applications may cache data for future re-use. The most common example people know is a web browser that saves recently downloaded content (especially images) in a cache, so the next time you visit the page it can display the image from cache/disk rather than have to download it again.

In short, caches are good, and a key part of good OS performance.


Now, the downside of these caches is that they take space on disk. However, the OS knows which files are caches, vs. your actual documents, and it knows that caches can be deleted with impunity - they'll just be rebuilt if they need to be. That's why, in your screenshot, it shows 'Available: 330.55 GB (287.64 GB purgeable)' showing that some 287GB of space is being used temporarily, but can be reclaimed and reused if needed.


The difference between the two screenshots indicates that the purgeable space couldn't be deleted at that point in time, likely because it was actually in use. Now, 287GB is a lot of space, and it's really hard to tell what it's actually being used for, but it likely relates to some application(s) you were running at the time.

For example, if you're running a video editing program such as Final Cut Pro, it will use a large amount of cache and temporary file storage for the footage, transitions, etc.. Similarly with image editing programs and the like - PhotoShop, for example, will retain an undo buffer, so you can undo multiple levels of image manipulation - each of the edits needs a certain amount of space.

The temporary files are typically deleted when the file is saved, or when the application is closed.


Many other programs also use caches and temporary files. While few may use that much themselves, if you have a dozen applications open, each with multiple documents that you haven't saved in a while (so the app is storing temp versions of the file with edits since the last save) it can add up.


So without knowing which applications were running at the time, it's impossible to be more specific, other than I think this is likely part of the normal workflow for your applications. Clearly it's transient, since the amount of purgeable space varies, and even drops to zero. The key is just working out which applications are contributing to it. Saving documents and closing apps that you're not using can help clue the OS into which files can be cleared out.

Reply

Jan 27, 2025 12:10 PM in response to CharPatton

CharPatton wrote:

Hi:

I am not technologically savvy, so I am sure I am using the phrase “leak” wrong.

But I have noticed some weird, inexplicable (to me) behaviour recently, and am hoping someone can help me out with an explanation.

Specifically, my Mac started running out of memory recently. Please see “Memory1” where there was only ~33GB of free space (it actually got much lower than that but I didn’t capture a screenshot). The Users folder only accounted for about 390 GB of the used memory. The System folder accounted for another 31GB, and the Applications and Library folders never calculated me a figure despite waiting 5 hours. “System Data” accounted for 653 GB!!!

Upon return to my computer the next day (“Memory 2”), all of a sudden I had 331 GB free space (an order of magnitude more) (at times I actually had closer to 400 GB free space, but again I didn’t think to snap a screenshot of that), and “System Data” had decreased to 398 GB.

No change in programs running between the two screenshots, just over night.

What is going on? Can someone explain this to me, or point me to a source that explains it in simple terms? I think a major system crash last week was due to a lack of memory. Is this a software thing, or should I be worried that there is a hardware issue with my RAM?

MacBook Pro, 14-Inch, 2021, Chip Apple M1 Max running MacOS 15.2.

Thank you very much!!!


[Re-Titled by Moderator]


SSD like to have 15-20% free disk space at all times—


Do some major house cleaning


How to free up storage space on your Mac - Apple Support

Free up storage space on Mac - Apple Support



RAM is memory

SSD is your Storage

Reply

Jan 28, 2025 9:49 AM in response to Camelot

Thank you, thank you, thank you, for your long, detailed, and very informative post!!!


I generally run with a lot of apps open, so I'll try: "Saving documents and closing apps that you're not using can help clue the OS into which files can be cleared out."


Many thanks for sharing your expertise!

Reply

Jan 28, 2025 12:59 PM in response to HWTech

Oh, good point, HWTech - I should have added snapshots (and Time Machine backups) to the list of transient storage use. Both of these will consume space until it's offloaded/reclaimed.


I do think it would be nice if Apple provided some kind of insight to this kind of thing. Lots of people ask about it, and it can be concerning when you don't know the cause.

Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Inconsistencies in used and available storage space on MacBook Pro

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