HeartbeatHocusFocusFilesMacHyperTile
Guide

Storage on a Mac, from Apple's container maths to the folder the Finder hides

Apple's own definition of free versus available space, the volumes macOS never shows you, and where the space really went on a Mac that looks empty.

By Chethan Kumar S N · Updated

A Mac that reports it is nearly out of space is a specific kind of annoying, because the obvious check makes no sense. You open the Storage pane, add up the categories, and they do not come close to the used figure. You look in your home folder and it looks like a home folder. You clear a cache, free a couple of gigabytes, and a week later the number is back where it was.

There is a real explanation, and Apple publishes almost all of it, spread across one support article and four pages of the macOS 27 User Guide that rarely turn up in the advice search engines hand you. The short version is that the numbers people compare are measured in different ways, that the disk you think of as one item is a container holding several volumes, and that the folder holding most of the missing space is hidden from the Finder by default.

Everything below comes either from those Apple pages, read while writing this, or from measurements taken on the Mac this page was written on, an M1 Pro with 32 GB of memory and a 1 TB disk running macOS 27.0.1. Nothing was installed, no setting was changed, and every command shown only reads.

Apple defines the two numbers, in one sentence

Almost every “my disk is full but it isn’t” argument comes down to a distinction Apple draws once, in the middle of a page called Find and delete files on your Mac:

The remaining space is free storage space. Free storage space is physically open space on a disk. Available storage space includes free storage space and purgeable disk caches (disk space might be both available and used at the same time).

That last clause is the whole thing. Space on an APFS disk can be counted as both used and available at once, because some of it is held by data macOS can discard the moment it needs room, such as caches, and (on a Mac with Time Machine running) local snapshots. One tool shows you the physical figure, another shows you the figure with the reclaimable part added in, and both are correct.

The User Guide’s Storage pages deal in available space. Apple’s instruction there is to open System Settings, click General, click Storage, then click All Volumes, where hovering over a colour tells you how much each category uses and light grey marks the free space. Finder’s Get Info route, which Apple also documents, shows the available figure too. Anything that reads the file system directly, Disk Utility included, shows the physical one, and so does df:

$ df -h / /System/Volumes/Data
Filesystem      Size   Used  Avail Capacity  Mounted on
/dev/disk3s1s1  926Gi  13Gi  286Gi      5%    /
/dev/disk3s5    926Gi 609Gi  286Gi     69%    /System/Volumes/Data

Two rows, one disk, one pool of 286 GiB of room, and a used figure that differs by 596 GiB depending on which row you read. Neither row is broken. The first is the read-only system volume that your Mac actually booted from, the second is the volume everything you own lives on, and they share the same free space because they sit inside the same container.

Macintosh HD is a container with five volumes in it

This is the part Apple explains properly, on a page called See if your Mac shares space across APFS volumes, which is worth quoting in full because it answers the question directly:

macOS 10.14 or later uses a file system called Apple File System (APFS), which allows space to be shared between volumes on a disk. If a single APFS partition (or container) has multiple volumes, the container’s free space is shared and can be allocated to any of the volumes as needed. Each volume uses only part of the overall container, so the available space is the total size of the container, minus the size of all volumes in the container. This overall amount of used space, including other volumes in the container, is indicated by a cross-hatched area.

There is a one-step test attached to it. In the Storage settings, if you see more than one disk listed, your internal disk has multiple volumes. That is Apple’s own diagnostic, and on a modern Mac it is nearly always true.

Here is what that container looked like on this machine, read with diskutil apfs list, which prints the container and every volume inside it without needing an administrator password.

VolumeRoleWhat it holdsMeasured here
Macintosh HDSystemThe sealed, read-only snapshot your Mac boots from. Apple’s system files, not yours.13.7 GB
PrebootPrebootFirmware and startup support files for each installed version of macOS. You cannot browse it in the Finder.10.8 GB
RecoveryRecoveryThe local Recovery volume, used when you start up holding the power button.1.5 GB
VMVMVirtual memory: swap files, and a single 2 GiB sleep image that belongs to root.7.5 GB
DataDataEverything else. Your home folder, applications, everything you have ever saved.654.0 GB

Add those up and you get the container: 994.7 GB of total space, 687.8 GB in use, 69.2 per cent, and 306.8 GB not allocated. Now look at the first four rows again. That is about 33 GB of a 1 TB disk used by volumes whose contents are never shown to you as files, before you have created a single document. On a 256 GB Mac the same 33 GB is a much larger share of the total, which is the honest reason small Macs feel full from the day they are set up.

The Storage bar is categories, not a file list

The other half of the confusion is that the Storage pane is not a listing of your disk. It is a set of categories, and Apple says plainly that the categories you see vary depending on the apps and files on your Mac. Apple’s page on deleting files names them: Applications, Documents, iCloud Drive, iOS files, TV, Music, Books and Podcasts, Mail, Messages, Music Creation, Photos, Bin, Other Users, macOS and System Data.

Two of those names do more work than the others. Bin is what you have deleted and not yet emptied. System Data, which older versions of macOS called Other, is the leftover bucket, and Apple’s description of it is that it measures the space used by all Apple and third-party files that do not belong to any more specific category, and that you cannot manage its contents because macOS manages them for you. If System Data is the large unexplained row on your Mac, the guide that goes through that category properly is a better read than this one, because this page is about the arithmetic rather than the bucket.

The important structural point is simpler than either. On this Mac, 654 GB sits on the Data volume while the Storage categories account for less than that, because the categories are about files and the volume also holds caches, logs, snapshots and databases that Apple classifies as System Data or does not classify at all. The categories add up to a good answer to “what is using my space” and a poor answer to “why is the total bigger than my files”.

The folder the Finder hides

If you have never found a lot of space on your Mac, start with the folder Apple keeps hidden. The company’s only published tip about it is on a page about going to folders directly: to go to your Library folder, press and hold the Option key, then choose Library. That is the practical route, and it exists because the Library folder inside your home folder is hidden by default, which is why most people who clean their Mac never see where the space actually is.

Here is the home folder of the Mac this page was written on, sorted by size with du. The last column is what matters.

$ du -xh -d1 ~ | sort -h | tail -12
182M    ./.iaasops
217M    ./Music
648M    ./.codex
948M    ./.cargo
1.4G    ./.rustup
2.3G    ./.claude
4.5G    ./.bun
4.5G    ./Downloads
5.8G    ./.npm
9.1G    ./.cache
22G     ./Desktop
113G    ./Library
323G    ./Documents

The Library folder is 113 GB of a 488 GB home directory. One level further in:

$ du -xh -d1 ~/Library | sort -h | tail -10
266M    ./WebKit
13G     ./Application Support
13G     ./Caches
86G     ./Developer

The Applications folder on the same machine, every app installed, is 23 GB. The hidden folder in the home directory is five times that. Almost all of it is the Developer folder, which is Xcode support files and iOS simulator runtimes, and it belongs to a toolchain that was installed deliberately. Caches held 13 GB and Application Support held another 13 GB, both belonging to apps that are installed and in use.

None of this is junk, and that is the honest point. The reason nobody finds it is not that it is hidden malware, it is that Apple hides the directory and no cleaner can tell the difference between a simulator runtime an iOS developer needs and a file worth deleting.

Space that is used and is not the files you made

Beyond the volumes and the Library folder, a handful of things occupy real space in ways that do not look like files:

There is a neat way to tell whether purgeable data is part of your problem. Compare the available figure in the Storage pane with the free figure from df. On this Mac the two came out within a gigabyte of each other, which is the answer that there was nothing purgeable waiting to be reclaimed. Where the two figures diverge by tens of gigabytes, the difference is largely reclaimable, and the System Data page covers what does and does not shrink it.

Measuring it yourself, in about five minutes

None of the third-party “space analyser” apps do anything you cannot do in a terminal with four commands, and one of them is already built into your Mac. This is the whole set, all read-only:

$ df -h / /System/Volumes/Data       # the two rows, and the shared free space
$ diskutil apfs list                 # the container, its volumes and their sizes
$ du -xh -d1 ~ | sort -h | tail -12  # where it went in your home folder
$ du -xh -d1 ~/Library | sort -h | tail -10
$ tmutil listlocalsnapshots /        # Time Machine local snapshots, if any

Two honest caveats, both of which cost more time than they save if you do not know them. du runs with your permissions, so it silently skips anything it cannot read and always reports less than the Storage pane; a folder that does not appear in its output is usually a permissions question rather than an empty folder. And a Mac with Time Machine turned on can hold local snapshots that df counts as used, which is what tmutil listlocalsnapshots is for. On this Mac that command returned nothing, which is one more reason the two free figures agreed.

If you would rather not open Terminal, every part of this has a window. Storage settings has the All Volumes chart, and clicking it breaks the bar down per volume and container. Finder’s Get Info on Macintosh HD, opened by selecting the disk and choosing File then Get Info, shows the capacity and the available figure. Disk Utility shows the same container structure as diskutil, with each volume listed underneath the disk. That structure is also why its other button takes a while: First Aid has to be run against each of those volumes in turn rather than once against the disk, and the order Apple gives for that is the opposite of the order most people click in.

Why the number does not move after you delete something

Three explanations cover most of it. Apple gives the first directly in its free-up-space article: when you move a file to the Bin, its storage space does not become available until you empty the Bin. People read that sentence and assume it cannot be their problem, then find a Bin holding 40 GB of old downloads.

The second is snapshots and purgeable data. A deleted file’s blocks can stay allocated until a snapshot that references them ages out, and macOS only reclaims purgeable space when it needs the room, so a deletion can be real and invisible at the same time.

The third has nothing to do with macOS being strange. On a 1 TB disk, 20 GB is two per cent, and two per cent does not visibly move a bar. Size the problem before you work on it, because sorting by size and deleting one 60 GB file beats deleting three hundred small ones and feeling like nothing happened.

There is also a specific warning worth knowing if you use Time Machine. Apple’s own note on backups is that if your startup disk is nearly full, Time Machine might not be able to save the temporary data it needs to complete a backup. A disk that is 98 per cent full stops behaving like a disk with a bit less room and starts breaking things that used to work.

What actually helps, in the order Apple lists it

Apple’s free-up-space article has four sections, and following their order is genuinely better than the order most advice uses.

First, find out how much space is available, which is the two numbers above. Second, optimise storage space, which is Apple’s iCloud route: storing files in iCloud Drive, photos in iCloud Photos and messages in iCloud so that, in Apple’s words, the files do not take up space on your Mac and can be downloaded again when needed. Those files keep their names and their full sizes in the Finder while taking up nothing on the disk, and it is the iCloud Drive daemon that holds them as placeholders and fetches them again on demand, which the bird process page measures on a real folder. The placeholder half, turning a file into something that takes no space and back again, belongs to a daemon of its own, which the fileproviderd page watches through its own state dump. The photo half of the same promise is a separate daemon, which the cloudphotod page traces into its own database inside the library. Third, move or delete files: an external drive for media, delete what you can stream again, clear the Downloads folder, erase Mail’s junk and deleted items, remove old iOS backups, uninstall apps you no longer use, delete user accounts nobody signs into, compress what you want to keep, and empty the Bin. Fourth, temporarily free up more: Apple’s own trick is starting up in safe mode, which clears some system caches that are created again as needed, and which is honest about being temporary. It exists to give you room to install an update, not to fix a full disk.

One item on Apple’s list is worth pausing on, because it is the one people do least well: uninstall apps you no longer use. The app bundle is the part you can see, and it is often the smaller part. On this Mac, Slack is a 273 MB application holding about 1.8 GB in the Library, and Claude is a 626 MB app holding roughly 4 GB, which means removing the app from the Applications folder can look like nothing happened. The uninstall page measures both halves for seven installed apps and shows the two commands that find the rest.

Worth knowing is that macOS already does part of this itself. Apple’s note is that when space is needed on your Mac, macOS also clears caches and logs that are safe to delete, including temporary database files, interrupted downloads, staged macOS and app updates, Safari website data and more. That is why a full disk often becomes a less full disk after an update, and why the improvement does not last. The part macOS will not do is decide which of your files you no longer want, and that is the part that actually moves the number.

Where window managers fit

Nothing on this page is something a window manager can fix, and it would be strange to claim otherwise. Full disks slow Macs down in ways that have nothing to do with how windows are arranged, and the honest advice while you clean up is exactly Apple’s: read the numbers, sort by size, and delete the large things rather than the convenient ones.

What does help afterwards is needing fewer manual moves. If your Mac is under pressure and you are checking the three numbers that decide whether it is sluggish or merely busy, the last thing you want is another five minutes of resizing and repositioning windows. Ribbon keeps the windows you have open as a scrolling strip instead of a pile of overlapping rectangles, so nothing shrinks, nothing hides behind anything, and moving between them is a trackpad swipe. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. You can drive the strip in your browser before installing anything.

The short version

A Mac reporting a full disk is usually describing the whole container, not your files. Apple’s own explanation is that the container’s free space is shared across its volumes and that available space is the container total minus all the volumes in it, which on a 1 TB Mac means about 33 GB of system, preboot, recovery and virtual memory volumes before you add anything. On top of that, Apple distinguishes free space, which is physically open space, from available space, which also counts purgeable disk caches, so two tools can give two different answers and both be right. The biggest single hiding place is the Library folder in your own home directory, which the Finder hides until you hold Option and choose Library from the Go menu, and which held 113 GB on the machine this page was written on. Measure with df, diskutil apfs list and du before deleting anything, sort by size, empty the Bin, and let macOS handle the caches, because it already does.

Questions

Why does my Mac say storage is full when I have nothing on it?

Because the number macOS reports is the whole disk rather than the files you made. A Mac boots from one APFS container that holds several volumes, and Apple's own explanation of that is that the container's free space is shared and can be allocated to any of the volumes as needed, so the available space is the total size of the container minus the size of all volumes in it. On the Mac this page was written on, four volumes that are not yours account for about 33 GB before anything is opened: the sealed read-only system volume at 13.7 GB, Preboot at 10.8 GB, Recovery at 1.5 GB and the virtual memory volume at 7.5 GB. Add the home folder's hidden Library directory, which Apple keeps out of the Finder by default, and the arithmetic starts to look normal again.

Why do Finder and Disk Utility show different amounts of free space?

Because one of them is showing free space and the other is showing available space, and Apple defines them differently in a sentence most people have never read: free storage space is physically open space on a disk, while available storage space includes free storage space and purgeable disk caches, and disk space might be both available and used at the same time. The Storage pane and Finder's Get Info deal in available space, which counts caches and snapshots macOS can throw away when it needs the room. Tools that read the file system directly, such as df and Disk Utility, deal in the physical figure. Neither is lying. They are answering two different questions, and the gap between them is the space you are looking for.

Where is the hidden folder taking up space on my Mac?

It is your own Library folder, and it is hidden from the Finder by default. Apple's own tip is to press and hold the Option key in the Finder, then choose Library from the Go menu. On the Mac this page was written on it held 113 GB of a 488 GB home folder, more than the whole Applications folder at 23 GB, and the biggest single item inside it was the Developer folder at 86 GB, almost all of it iOS simulator runtimes and Xcode support files. Caches came to 13 GB and Application Support to another 13 GB. Every one of those folders belongs to something you installed, which is why no cleaner labels them as safe to delete.

Why is my Mac still full after deleting files?

Three honest reasons, in the order they usually apply. Apple's own line is that when you move a file to the Bin, its storage space does not become available until you empty the Bin, so an emptied Bin is the first thing to check. Second, APFS and Time Machine snapshots can hold on to blocks from a file you deleted for a while after it is gone. Third, and most common, the thing you deleted was small relative to the disk. On a 1 TB Mac, deleting 20 GB of downloads moves the number from full to nearly full, which reads as nothing happening. Sorting by size before deleting is the only way to avoid the feeling of doing work with no result.

Does macOS free up space by itself?

Yes, in ways Apple documents. Its own explanation is that when space is needed on your Mac, macOS also clears caches and logs that are safe to delete, including temporary database files, interrupted downloads, staged macOS and app updates, Safari website data and more. That is why the number often drops after an update or a restart and then climbs again over the following weeks. The Storage pane also offers to store files in iCloud and to remove Apple TV films and programmes you have already watched, and an Empty Bin automatically setting that clears anything older than 30 days. What macOS will not do is decide which of your own files you no longer need, which is why the largest single win is almost always somewhere you have not looked yet.

Ready? Buy Ribbon for $15, or read all the guides.