Skip to tool
ecech.
📏 Productivity & Units

Where the Missing Gigabytes Went, and Why Nobody Cheated You

A 1 TB drive really holds a trillion bytes. Windows divides by 1024 and still writes GB on the label, so it shows 931. The drive is fine; the units are not.

Actual bytes

exactly what you bought

Windows shows

before formatting

macOS / Linux show

decimal units

Usable after format

Where it goes

Advertisement

How the calculation works

Same drive. Same bytes. Two ways of counting. 1,000,000,000,000 bytes divide by 1000 1.00 TB what the box says, macOS, Linux divide by 1024 931.32 “GB” what Windows says — it means GiB The 9.05% gap is a label, not a loss. Nothing is missing from the drive.

How to Use This Tool

Enter the size printed on the box. You get the exact byte count, what each operating system will display, and the separate, much smaller amount that formatting really costs.

The whole answer in one line

A terabyte is a trillion bytes. Windows divides by 1024 three times, which gives 931.32, and then writes GB next to it — but 1024-based units are called GiB (gibibytes). The number is right and the label is wrong, and that mislabelling is the entire mystery.

The gap is always 9.05% at terabyte scale, whatever the size, because it is a fixed ratio between two counting systems rather than anything being consumed. A 4 TB drive loses the same 9.05% and shows 3,725 "GB".

Who is right

Both, in their own terms — but only one is consistent with everything else. Every other SI prefix is decimal: a kilometre is 1,000 metres, not 1,024. Drive manufacturers use the same convention, which is why they have won every lawsuit brought over this. The 1024-based prefixes were standardised as kibi, mebi, gibi in 1998 precisely to end the ambiguity.

macOS switched to decimal units in 2009 and Linux tools mostly followed, so both show a 1 TB drive as 1 TB. Windows still shows 931 and still calls it GB. If your drive "shrank" when you moved it between machines, nothing happened to it.

The gap grows with each step up 1 kB vs 1 KiB2.4% 1 MB vs 1 MiB4.9% 1 GB vs 1 GiB7.4% 1 TB vs 1 TiB9.1% Each step multiplies the discrepancy by 1.024, so bigger drives look like a bigger swindle.
Nothing changes about the drive; the two counting systems simply diverge faster.

Formatting really does cost something, but not much

This is the part that is genuinely consumed, and it is far smaller than people assume. A filesystem needs space for its own bookkeeping — the file table, journal, allocation bitmaps, and space reserved so the disk does not become unusable when full.

  • NTFS — roughly 0.5%, mostly the Master File Table and journal.
  • exFAT — roughly 0.3%, since it keeps less metadata.
  • ext4 — roughly 1%, including 5% reserved for root by default on older setups, which is often reduced.

So on a 1 TB drive formatting costs a few gigabytes, and the unit mismatch accounts for around sixty-nine. Blaming formatting for the whole gap is the common misdiagnosis; the chart above keeps them separate.

SSDs and over-provisioning

Solid-state drives set aside additional capacity you never see, used for wear levelling and to replace failed cells. On consumer drives this is usually already excluded from the advertised figure, so it does not add to the gap. It is why some enterprise SSDs are sold in odd sizes like 960 GB rather than 1 TB — that one is visible in the number on the box.

Advertisement

Frequently Asked Questions

Why does my 1TB drive only show 931GB?
Because the drive holds one trillion bytes, which is what a terabyte means, and Windows divides by 1024 three times to get 931.32 — then labels it GB when it actually means GiB. The number is correct and the unit label is wrong. Nothing is missing from the drive.
Are hard drive manufacturers lying about capacity?
No. They use decimal prefixes consistently with every other SI unit — a kilometre is 1,000 metres, not 1,024 — which is why they have won the lawsuits brought over this. Windows is the one using 1024-based maths while displaying decimal-style labels.
Why does macOS show a different size than Windows for the same drive?
macOS switched to decimal units in 2009, so it shows a 1 TB drive as 1 TB. Windows still divides by 1024 and shows 931 GB. The drive is identical; only the arithmetic and the labels differ.
How much space does formatting actually use?
Far less than the unit gap. NTFS takes roughly 0.5% for its file table and journal, exFAT about 0.3%, ext4 about 1%. On a 1 TB drive that is a few gigabytes, against roughly sixty-nine lost to the unit mismatch. Blaming formatting for the whole difference is the usual misdiagnosis.
What is the difference between GB and GiB?
A GB is 1,000,000,000 bytes and a GiB is 1,073,741,824 — a difference of about 7.4%. The binary prefixes kibi, mebi and gibi were standardised in 1998 specifically to remove this ambiguity, but Windows never adopted the labels while still using the maths.
Does the gap get worse on larger drives?
As a percentage it grows with each prefix step: 2.4% at kilobytes, 4.9% at megabytes, 7.4% at gigabytes and 9.1% at terabytes. So a larger drive appears to lose proportionally more, which is why the complaint became common as drives got bigger.

Related tools in Productivity & Units

Browse all Productivity & Units tools