Conversion · By · Jul 16, 2026 · 6 min read

Why Your 1 TB Drive Only Shows 931 GB

You buy a 1 TB drive, plug it in, and Windows reports 931 GB. Nothing is broken, nothing was stolen, and the drive is exactly the size it says on the box. Two different definitions of the word gigabyte are quietly disagreeing with each other.

Why Your 1 TB Drive Only Shows 931 GB — ListCalc

Two definitions of the same word

Drive manufacturers use the metric system, where prefixes mean what they mean everywhere else in science. A kilo is a thousand. So one terabyte is 1,000,000,000,000 bytes — a clean power of ten.

Computers address memory in binary, so it has always been convenient for software to round to powers of two. The nearest power of two to a thousand is 1,024, so a "kilobyte" became 1,024 bytes, a "megabyte" 1,024², and so on.

Both are internally consistent. The problem is that they use the same words. Divide the manufacturer's number by the operating system's definition and you get the shortfall:

1,000,000,000,000 ÷ 1,073,741,824 = 931.32
1 TB (decimal) displayed as 931 GB (binary). No bytes are missing — they are being counted in larger units.

The gap grows at every step

This is the part that surprises people. The discrepancy is not a fixed 7% — it compounds, because each level multiplies by 1,024 instead of 1,000.

UnitDecimal (maker)Binary (OS)Gap
Kilobyte1,0001,0242.4%
Megabyte10⁶1,048,5764.9%
Gigabyte10⁹1,073,741,8247.4%
Terabyte10¹²1,099,511,627,77610.0%
Petabyte10¹⁵1,125,899,906,842,62412.6%

At the kilobyte scale nobody noticed. At terabyte scale you are looking at 69 GB apparently unaccounted for, and at petabyte scale — the world of data centres — the 12.6% gap is a budget line.

What actually shows which

WhereCounts inLabels it
Drive packagingDecimalGB / TB
Windows File ExplorerBinaryGB / TB
macOS (since 10.6) and iOSDecimalGB / TB
Linux (varies by tool)EitherGB or GiB
RAM, everywhereBinaryGB

Windows is the main source of the confusion: it does binary arithmetic and then prints the decimal label. macOS switched to decimal years ago, which is why the same external drive can read 931 GB on a PC and 1 TB on a Mac without either being wrong.

RAM is the exception that never changed. Memory really is manufactured in powers of two because of how address lines work, so a 16 GB stick genuinely contains 17,179,869,184 bytes. Storage was never bound by that constraint.

The prefixes that were supposed to fix this

In 1998 the International Electrotechnical Commission introduced separate binary prefixes so the two systems could stop sharing vocabulary: kibibyte (KiB), mebibyte (MiB), gibibyte (GiB), tebibyte (TiB). Under that scheme your drive holds 1 TB, which equals 931 GiB, and both statements are precisely true.

Adoption has been partial. Linux tooling and storage engineers use them routinely; consumer software largely ignored them. Nearly three decades on, "GB" still means one thing on a box and another in a file manager.

The other missing space

Unit definitions explain most of the shortfall but not all of it. A brand-new drive also loses capacity to:

If the arithmetic above accounts for the gap you are seeing, the drive is fine. If a 1 TB drive is showing 800 GB, look for a hidden partition rather than a defect.

The same trap with internet speeds

A related unit collision catches people every time they download something. Connection speeds are quoted in bits per second; file sizes are in bytes. There are eight bits in a byte, so a 500 Mbps line tops out around 62.5 MB/s — before any real-world overhead. Watch the capitalisation: Mb is megabits, MB is megabytes.

Sources and method: binary prefix definitions follow IEC 80000-13, summarised by NIST in "Prefixes for binary multiples". Decimal SI prefixes are as defined in the SI Brochure. Gap percentages are computed as (binary − decimal) ÷ decimal at each scale. Last reviewed 16 July 2026.

Run your own numbers

FAQ

Why does my 1 TB hard drive show as 931 GB?
Because the manufacturer counts a terabyte as 1,000,000,000,000 bytes while Windows divides by 1,073,741,824 to get a gigabyte. The drive contains exactly the bytes advertised — 1,000,000,000,000 ÷ 1,073,741,824 works out at 931.32, so the same storage is simply displayed in larger units.
Is the drive manufacturer cheating me?
No. Using decimal prefixes is the standards-compliant reading — a kilo means a thousand throughout science and metrology. The mismatch comes from operating systems using powers of two internally while printing decimal labels. After a wave of US class-action suits in the 2000s, packaging now routinely carries a note explaining the difference.
What is the difference between GB and GiB?
A gigabyte (GB) is 10⁹ bytes, or one billion. A gibibyte (GiB) is 2³⁰ bytes, or 1,073,741,824 — about 7.4% larger. The IEC introduced GiB in 1998 precisely so the two could be distinguished. A 1 TB drive holds 931 GiB, and both figures describe exactly the same amount of storage.
Why does RAM not have this problem?
Memory is genuinely manufactured in powers of two because of how memory addressing works, so a 16 GB module really does contain 2³⁴ bytes. Both the manufacturer and the operating system count it the same way, so the numbers agree. Storage devices were never subject to that constraint.
Why is my new laptop showing less free space than the drive size?
Beyond the unit difference, a pre-built machine typically ships with a recovery partition and an EFI system partition that together can take 10–30 GB and never appear as usable space. The filesystem also reserves a small amount for metadata, and SSDs hold back spare blocks for wear levelling.

Sources

Primary references used for the figures and rules on this page.

  1. Prefixes for Binary Multiples — NIST
  2. International Standards — IEC 80000 series — International Electrotechnical Commission