Apple's own Storage settings, third-party apps, and casual conversation all use "storage," "disk space," and "drive space" as if they mean exactly the same thing, and most of the time the difference does not matter enough to notice. It starts to matter the moment you buy a "256 GB" Mac and About This Mac reports something closer to 238 GB available before you have installed a single file. That gap is not a scam, a rounding error, or Apple quietly taking a cut — it is the predictable, well-documented result of two different definitions of "gigabyte" being used by two different parties, and it is worth understanding precisely rather than accepting vaguely.
What these terms mean in casual use
In everyday conversation, and often in marketing, "storage" tends to be used as the broader term — it can mean the total capacity of your device's storage ecosystem, sometimes including cloud services like iCloud that extend what feels like "your" available space beyond the physical drive. "Disk space" and "drive space" more often refer specifically to what is physically present on the local disk itself, independent of anything synced or stored remotely.
The three terms overlap heavily and get swapped freely because for most everyday purposes the distinction is not load-bearing — if your Mac is nagging you about running low, you are almost always talking about the local disk regardless of which word you reached for. But when the numbers genuinely disagree, as they do with advertised capacity, precision starts to matter.
The real, verifiable reason a 256 GB drive is not 256 GB in the OS
This part is not vague marketing-versus-reality hand-waving — it is arithmetic, and it is worth working through exactly rather than gesturing at it.
Storage manufacturers, including Apple, advertise capacity using decimal (base-10) units, where 1 kilobyte is 1,000 bytes, 1 megabyte is 1,000,000 bytes, and 1 gigabyte is 1,000,000,000 bytes. This is a standard, internationally recognised convention (the SI prefix system) and it is what "256 GB" printed on a spec sheet literally means: 256,000,000,000 bytes.
Historically, operating systems including macOS calculated and displayed storage using binary (base-2) units instead, where the same prefixes were repurposed to mean powers of 1,024 rather than powers of 1,000 — so a "gigabyte" in that older convention actually meant 1,073,741,824 bytes, about 7.4% more than the decimal definition of the same name. macOS has since moved toward reporting decimal units to match the labels manufacturers use, but the underlying binary structure of how storage is actually addressed by hardware and filesystems has not gone away, and operating system reporting can still reflect binary-influenced accounting depending on the layer being measured and the exact version of the tool doing the measuring.
The practical result of the mismatch between the two counting systems is the same regardless of exactly which layer you are looking at: 256,000,000,000 bytes of advertised decimal capacity, when expressed using the binary convention where a "gigabyte" of display actually means 1,073,741,824 bytes, comes out to roughly 238 of those binary-sized units. That is precisely the "256 GB drive shows as about 238 GB usable" gap that catches new Mac buyers off guard — it is not missing storage, hidden partitions, or bytes taken by the operating system. It is the same physical bytes, counted and labelled by two different, both internally consistent, numbering conventions.
Why this is not the same issue as "System Data" or overhead
It is worth being precise about what this gap is not. The decimal-versus-binary difference is a labelling and counting convention, present the moment a drive is manufactured, before you have written a single file to it. It is entirely separate from the genuinely real space consumed afterwards by the operating system itself, system caches, Time Machine snapshots, or the "System Data" category that grows as you use the machine. Both effects reduce your apparent free space relative to the number on the box, but only one of them is arithmetic; the other is actual data occupying actual space that you can, in principle, investigate and reduce.
Conflating the two leads to the common but mistaken belief that a large chunk of a new Mac's drive is "used by macOS" in some opaque, unrecoverable way. In reality, a meaningful share of that initial gap between the advertised and reported figures is simply the unit conversion described above, present regardless of what you install.
Why the distinction between storage and disk space still matters practically
When you are troubleshooting a genuinely full disk, the useful question is almost always about local disk space specifically — what physical bytes on this drive are accounted for and what can be reduced. Broader "storage" framing, including iCloud-related messaging that talks about your overall storage plan, is a different and less immediately actionable question, because files that exist only in iCloud are not occupying local disk space to begin with, only placeholders.
Being precise about which one you mean when you ask "why is my storage full" saves time: if the answer you need is about physical bytes on the internal drive, terms like disk space or drive space, and tools that measure the local filesystem directly, are the right frame — not your iCloud storage tier.
Conclusion
"Storage," "disk space," and "drive space" are close enough in everyday use that insisting on strict definitions would be pedantic, but the one place precision earns its keep is explaining why an advertised drive capacity and an operating system's reported capacity never quite match: decimal gigabytes as sold and binary-influenced gigabytes as measured are two consistent, correct, but different numbering systems describing the identical physical bytes.
Once that gap is accounted for, the remaining question — what is actually using the disk space you do have — is the one worth spending your attention on, and it is the question VolumeLens is built to answer, by walking the real filesystem and showing exactly which folders account for the bytes in front of you rather than leaving you to guess at a pie chart.