Why Your 1TB Drive Only Shows 931GB (And It's Not a Scam)

Updated on January 1, 2026

The Moment Every New PC Owner Gets Suspicious

You buy a shiny new 1TB hard drive or SSD. You plug it in, open File Explorer or Finder, and stare at the number staring back at you: 931 GB. You paid for a terabyte. You got — apparently — something less. The receipt says 1TB. The box says 1TB. Your screen says something entirely different.

Before you start drafting an angry email to the manufacturer or filing a chargeback, here's what's actually happening — and why both numbers are, in a precise technical sense, correct.

Two Different Languages for Measuring the Same Thing

The entire confusion boils down to a units problem — the same kind of confusion you'd get if someone sold you "a pint" of beer in a country where a pint is 568ml but you're used to 473ml. Nobody's lying. They're just speaking different dialects of measurement.

Hard drive manufacturers measure storage using the decimal (SI) system:

  • 1 Kilobyte (KB) = 1,000 bytes
  • 1 Megabyte (MB) = 1,000,000 bytes
  • 1 Gigabyte (GB) = 1,000,000,000 bytes
  • 1 Terabyte (TB) = 1,000,000,000,000 bytes

Your operating system — Windows, macOS, Linux — traditionally measures storage using the binary system:

  • 1 Kibibyte (KiB) = 1,024 bytes
  • 1 Mebibyte (MiB) = 1,048,576 bytes
  • 1 Gibibyte (GiB) = 1,073,741,824 bytes
  • 1 Tebibyte (TiB) = 1,099,511,627,776 bytes

Here's the critical thing most articles gloss over: the drive contains exactly the number of bytes advertised. A "1TB" drive holds 1,000,000,000,000 bytes. Every single one of them is there. The operating system then divides that same byte count by 1,073,741,824 instead of 1,000,000,000, and reports a smaller number. No bytes were stolen. The math just changed.

The Actual Arithmetic (So You Can Verify It Yourself)

Let's do this properly. A drive marketed as 1TB contains exactly 1,000,000,000,000 bytes.

Divide that by the binary definition of a gigabyte (1,073,741,824 bytes):

1,000,000,000,000 ÷ 1,073,741,824 = 931.32 GiB

Round down to what Windows displays: 931 GB. There it is. The math checks out precisely. If you have a 2TB drive, you'll see roughly 1.81 TB. A 500GB drive shows up as about 465 GB. The gap scales proportionally — the bigger the drive, the bigger the apparent discrepancy in absolute terms.

Why Manufacturers Chose Decimal (And Why They're Not Wrong)

This isn't marketing trickery. Storage manufacturers adopted decimal prefixes for two solid reasons.

First, the SI prefix system — kilo, mega, giga, tera — has meant powers of ten in every other scientific and engineering context for over a century. A kilometer is 1,000 meters. A kilogram is 1,000 grams. A kilovolt is 1,000 volts. There was never a universal agreement that "kilo" should suddenly mean 1,024 in the context of digital storage — that was a computing convention that emerged organically because 2¹⁰ happens to be close to 1,000.

Second, NIST (the National Institute of Standards and Technology) and the IEC (International Electrotechnical Commission) both officially endorse the decimal interpretation for the standard prefixes. The IEC even introduced dedicated binary prefixes in 1998 — kibibyte, mebibyte, gibibyte, tebibyte — precisely to resolve this ambiguity. Drive manufacturers are technically on the correct side of the official standards.

Why Operating Systems Stuck with Binary

The binary convention in computing has deep roots. Early programmers and hardware designers worked with memory addressing in powers of two — it's how CPUs and memory controllers are architected at the silicon level. A memory address space of 2¹⁶ gives you 65,536 locations. Rounding that to "64,000" would have felt dishonest to engineers who knew the actual count.

So computing culture developed a shorthand: "1KB" meant 1,024 bytes. This propagated into operating systems, file systems, and programming tools. By the time the formal standards caught up, the habit was so deeply embedded that changing it would break decades of software, documentation, and user expectations.

Windows still uses binary math but labels the result "GB" — which is technically incorrect by modern standards. This is the actual culprit in your confusion. If Windows labeled its readout as "GiB" (gibibytes), the entire mystery would evaporate. macOS switched to decimal reporting in OS X Snow Leopard (10.6) back in 2009, which is why a 1TB drive shows up as "1 TB" in Finder — Apple aligned their display with the manufacturer's labeling. Linux tools vary: df -h uses binary by default, while df -H switches to decimal.

The Discrepancy at Every Drive Size

For reference, here's what you'll actually see reported in Windows for common advertised capacities:

  • 256 GB drive → shows ~238 GB
  • 500 GB drive → shows ~465 GB
  • 1 TB drive → shows ~931 GB
  • 2 TB drive → shows ~1,862 GB (or ~1.81 TB)
  • 4 TB drive → shows ~3,725 GB (or ~3.63 TB)
  • 8 TB drive → shows ~7,451 GB (or ~7.27 TB)

Notice that the percentage loss stays constant at about 6.8%, but the raw gigabyte gap gets larger as drives grow. An 8TB drive appears to "lose" over 500GB compared to advertised capacity. The fraction is identical; the psychological impact scales with price.

Is Any Storage Actually Lost?

From a usable-space perspective, there are two separate factors worth distinguishing.

The decimal-vs-binary gap? Not a single byte of usable storage is lost to this. Your drive has 1,000,000,000,000 bytes of capacity. The operating system uses every one of them. It just reports the count using a different divisor.

However, there are legitimate reasons your formatted drive shows slightly less free space than the raw capacity in either measurement system:

  1. File system overhead: NTFS, APFS, ext4, and every other file system reserves a small portion of space for its own internal structures — the master file table, journal, directory metadata. This typically amounts to 1–3% of total capacity.
  2. Manufacturer reserved sectors: SSDs especially set aside a percentage of NAND capacity as over-provisioning — spare cells used for wear leveling and bad block management. This extends drive lifespan but reduces visible capacity.
  3. Recovery/restore partitions: Many OEM drives ship with hidden partitions containing Windows recovery tools, eating anywhere from 500MB to several gigabytes.

These are real reductions in usable space. The decimal-to-binary conversion is not.

The Legal Angle — And Why Manufacturers Keep Winning

Western Digital faced a class action lawsuit in 2006 over exactly this issue. The court ultimately sided with WD, finding that their decimal-based advertising was not deceptive because the packaging disclosed how capacity was measured. Similar suits against Seagate reached similar conclusions. The FTC has never required manufacturers to change their labeling.

This doesn't mean the situation isn't confusing — it obviously is, and a better-labeled operating system readout would end the confusion permanently. But it does mean there's no legal fraud happening, and you're not getting cheated in any meaningful sense.

What You Should Actually Do With This Information

Practically speaking, here's how to apply this:

  • When comparing drives for purchase, compare like with like — all manufacturer specs use decimal, so comparing 1TB vs 2TB is always apples-to-apples.
  • When a Windows machine reports available space, remember you're looking at GiB, not GB. Mentally multiply by 1.074 to get the "true" decimal gigabytes if you want to verify against the advertised capacity.
  • When troubleshooting disk space issues, use your OS's built-in disk analyzer (WinDirStat on Windows, DiskDiag on macOS) rather than comparing the raw "available" figure to the box — the box uses different units.
  • If you're writing software that reports file sizes to end users, consider clearly labeling whether you're reporting GiB or GB. The IEC binary prefixes exist precisely for this purpose.

The Bottom Line

Your 1TB drive contains exactly 1 trillion bytes. That's what you paid for, that's what you got, and that's what your file system uses. The number "931" you see in Windows is the correct binary conversion of those exact bytes into gibibytes, displayed under the technically incorrect label "GB."

The manufacturer defined a terabyte using the international standard. Your operating system defined a gigabyte using a computing tradition. Neither is wrong in the context of its own system. They're just not speaking the same language — and until Microsoft decides to update its labels after several decades, this particular "problem" will keep generating confused Reddit posts and suspicious phone calls to tech support.

Now you know exactly what's happening, why both numbers are defensible, and how to convert between them. The drive isn't cheating you. It's just that nobody ever properly introduced decimal and binary to each other.