Why Your 1 TB Hard Drive Doesn't Actually Have 1 TB of Space

You buy a shiny new 1 TB hard drive. You plug it in, your operating system mounts it, and then — wait — Windows shows 931 GB. Mac shows 1 TB. What's going on? Did the manufacturer steal 70 GB from you? Is your OS lying? The answer is neither, and once you understand what's really happening, you'll see that data size conversion is one of those areas where two completely valid answers can look wildly different.

It all comes down to a disagreement that's been simmering in the computing world for decades: what does "kilo" actually mean?

The Two Systems and Why Both Exist

In everyday life, "kilo" means 1,000. A kilogram is 1,000 grams, a kilometer is 1,000 meters. The metric system is clean and consistent. So when disk manufacturers started labeling drives, they naturally said 1 kilobyte = 1,000 bytes, 1 megabyte = 1,000,000 bytes, and so on up the chain. A 1 terabyte drive holds exactly 1,000,000,000,000 bytes. Nothing shady about that.

But here's where computers complicate everything. Memory addressing in binary works in powers of 2. RAM is organized in chunks of 2^10 = 1,024 bytes, not 1,000. Early programmers found that 1,024 was "close enough" to 1,000 that they just called 1,024 bytes a "kilobyte" — same word, different meaning. This convention spread everywhere. Operating systems adopted it. File systems used it. For decades, the word "kilobyte" meant two different things depending on context.

The International Electrotechnical Commission (IEC) finally stepped in during 1998 and created unambiguous names for the binary units: kibibyte (KiB), mebibyte (MiB), gibibyte (GiB), tebibyte (TiB), and so on. But the old informal usage never fully went away. Windows still reports drive capacity in what it calls "GB" but actually means GiB. macOS switched to SI units in macOS Lion 10.7, which is why it shows more storage space than Windows does for the exact same drive.

The Math Behind the Mismatch

The difference between decimal and binary looks small at the kilo level — 1,000 vs 1,024, about a 2.4% gap. That's not a big deal. But the gap compounds at every step up the prefix ladder:

• 1 KB vs 1 KiB: 1,000 vs 1,024 bytes — 2.4% difference
• 1 MB vs 1 MiB: 1,000,000 vs 1,048,576 bytes — 4.9% difference
• 1 GB vs 1 GiB: 1,000,000,000 vs 1,073,741,824 bytes — 7.4% difference
• 1 TB vs 1 TiB: 1,000,000,000,000 vs 1,099,511,627,776 bytes — 9.95% difference
• 1 PB vs 1 PiB: about 12.6% difference

That 931 GB your OS reports for a 1 TB drive? That's exactly right. 1,000,000,000,000 bytes divided by 1,073,741,824 (bytes per GiB) equals 931.32 GiB. The drive manufacturer and your OS are both being accurate — they're just counting differently.

Where It Actually Matters in Real Life

For most casual users checking whether a photo or video will fit, the distinction barely matters. But there are situations where the decimal-vs-binary difference genuinely bites you:

Storage provisioning: If you're a sysadmin allocating disk quotas, using the wrong scale means users hit their limits unexpectedly — or you waste significant capacity. On a petabyte-scale storage array, the 12.6% gap between PB and PiB can mean over 100 TB of capacity that's miscounted in planning documents.

Data transfer and billing: Cloud providers bill storage in decimal units (AWS S3, Google Cloud Storage, Azure Blob all use SI). Your local backup software might report transfer sizes in binary units. If you're trying to reconcile your cloud bill with your backup logs, you'll scratch your head unless you know which system each is using.

RAM vs storage: RAM is almost always measured in binary units in practice (because it's physically organized that way). A stick of 8 GB RAM actually contains 8 GiB = 8,589,934,592 bytes. Storage manufacturers use decimal. This is why RAM and storage feel like they're measured on different planets even though both say "GB".

Network speeds: Networking almost universally uses decimal. A 1 Gbps connection transfers 1,000,000,000 bits per second (or 125,000,000 bytes per second, since there are 8 bits per byte). But download managers sometimes display speeds in MiB/s. So a 125 MB/s connection is actually about 119.2 MiB/s — which sounds slower but is exactly the same throughput.

What PB and Beyond Actually Look Like

A petabyte is 1,000 terabytes in decimal — roughly the storage capacity needed for about 500 billion pages of standard text, or around 250,000 standard-definition movies. As of the mid-2020s, hyperscale data centers like those run by Google, Amazon, and Microsoft operate at the exabyte level (1,000 PB). Most of us will probably max out at the terabyte level personally for quite a while, but understanding petabytes matters if you're working with big data, scientific datasets (genomics, particle physics, astronomical surveys), or large-scale video archives.

The converter above handles up to petabytes on both scales, which covers essentially every real-world use case you'll encounter today.

A Practical Guide to Which System to Use When

Whenever you're dealing with storage hardware (SSDs, HDDs, USB drives, SD cards), stick with decimal if you want to match the manufacturer's label. If you're a developer or sysadmin working with memory allocation, file system block sizes, or OS-reported sizes, you're probably dealing with binary values even if they're labeled "GB" without the "i". For network throughput, use decimal — that's the universal convention in networking.

And if you're ever in an argument about whether your drive is "short-changing" you, just pull up this converter, punch in 1 TB, and show the other person that 1 TB = 931.32 GiB. The drive is full size. The labels are just speaking different dialects of the same language.

Understanding both systems isn't just academic trivia. It's the kind of foundational knowledge that prevents real mistakes — provisioning too little storage, misquoting cloud budgets, or shipping a product with the wrong capacity claims. The numbers look simple, but the meaning behind them has been confusing people for the better part of sixty years.