Reference path · conclusion first

Why Does a 1 TB Drive Show Only 931 GB?

1 TB = 931.3 GiB. The bytes are all there.

Precise claimA '1 TB' drive contains 10^12 bytes under the SI decimal definition manufacturers use. Counted in IEC binary units of 2^30 bytes, the same drive is about 931.3 GiB, which Windows displays as '931 GB'. The apparent loss is a unit-system mismatch, not missing bytes.

Applies

Applies to storage devices labeled with SI decimal prefixes and operating systems that count in binary multiples. The arithmetic 10^12 / 2^30 = 931.32... generalizes across scales: the binary prefix exceeds the decimal one by 2.4% at kilo, 4.9% at mega, 7.4% at giga, 10.0% at tera, and 12.6% at peta.

Does not prove

Does not cover actual filesystem and formatting overhead, which consumes space in addition to the unit effect; does not exonerate genuinely defective or fraudulently labeled devices; does not adjudicate every vendor's labeling practice.

Portable rule

If a reported capacity, speed, or quantity looks short, then check which unit system each side is using before suspecting loss or fraud.

Test yourself first Jump to evidence ↓

Evidence reviewed 2026-07-20. Corrections and review policy.

Use as a reference

Declare the discussion context, then copy a stable link. No account or personal data is attached.

quantity-frame

Why Does a 1 TB Drive Show Only 931 GB?

Commit to why a new 1 TB drive reports about 931 GB, then flip one variable — the unit prefix — on the same byte count and watch the missing gigabytes reappear.

New drive — properties

Retail label: 1 TB
Bytes on the device: 1,000,000,000,000
Reported capacity: 931 GB

The byte count above is the drive you actually bought. Every number below is computed from it live — nothing is looked up.

Before you touch anything: where did the other 69 GB go?

The manufacturer mislabeled the driveThe OS or filesystem ate the differenceThe two sides count in different units

The reveal

A '1 TB' drive contains 10^12 bytes under the SI decimal definition manufacturers use. Counted in IEC binary units of 2^30 bytes, the same drive is about 931.3 GiB, which Windows displays as '931 GB'. The apparent loss is a unit-system mismatch, not missing bytes.

You answered: —

SI decimal — the label1,000,000,000,000 ÷ 10⁹—

IEC binary — the counter1,000,000,000,000 ÷ 2³⁰—

Same bytes, two divisors. The shortfall you perceived — — — is what 931 looks like next to 1,000. It is not the same figure as the tera-scale prefix gap (—): different denominators, different questions.

No bytes are missing. The gigabyte changed meaning mid-conversation.

The rebuilt model

You assumed:: Giga means the same thing everywhere: a 1 TB drive holds 1,000 gigabytes as my operating system counts them, so a report of 931 means something is wrong.
The actual model:: Two legitimate prefix systems coexist: SI decimal (kB = 10^3, GB = 10^9, TB = 10^12) and IEC binary (KiB = 2^10, GiB = 2^30, TiB = 2^40). The same byte count reads as different numbers depending on which system divides it, and the divergence grows with scale.
The variable that failed you:: Unit prefix interpretation — whether 'giga' divides the byte count by 10^9 or by 2^30.

Change one variable

The drive is locked at 1,000,000,000,000 bytes — it cannot gain or lose a byte here. The only variable that flips is the unit system used to read it.

Same trillion bytes, counted in IEC binary units (1 GiB = 2³⁰ bytes). What does the drive display?

About 931 GiBAbout 1,000 GiBAbout 1,024 GiB

Test the rebuilt model — neighboring sizes

If the model is right, it must predict drives it has never seen. These are predictions, not new variables: the byte count and the prefix definitions still do all the work.

A 2 TB drive (2 × 10¹² bytes), counted in TiB:model predicts 1.819 TiB

A 500 GB drive (5 × 10¹¹ bytes), counted in GiB:model predicts 465.66 GiB

The prefix gap grows with scale — computed live as (2¹⁰ⁿ − 10³ⁿ) ÷ 10³ⁿ
Scale	Binary prefix larger by
kilo / kibi	—
mega / mebi	—
giga / gibi	—
tera / tebi	—
peta / pebi	—

Evidence

NIST, Prefixes for Binary Multiples
IEC binary prefixes (Ki, Mi, Gi, Ti as powers of 2^10), worked comparisons with SI prefixes (1 GB = 10^9 B vs 1 GiB = 2^30 B), and the historical note that storage manufacturers use decimal.
official-doc — checked 2026-07-20.
Seagate Support: Why does my hard drive report less capacity than indicated on the drive's label?
Manufacturer base-10 capacity labeling, the decimal-to-binary conversion formulas, and the explicit table row showing a 1 TB drive reported by Windows as 931 GB.
official-doc — checked 2026-07-20.
Apple Support: How storage capacity is measured on Apple devices (HT201402)
Decimal measurement ('1GB = 1 billion bytes, and 1TB = 1 trillion bytes'), the binary definition (1 GB = 1,073,741,824 bytes), and that some operating systems report capacity using the binary system.
official-doc — checked 2026-07-20.

Scope: Applies to storage devices labeled with SI decimal prefixes and operating systems that count in binary multiples. The arithmetic 10^12 / 2^30 = 931.32... generalizes across scales: the binary prefix exceeds the decimal one by 2.4% at kilo, 4.9% at mega, 7.4% at giga, 10.0% at tera, and 12.6% at peta.

Does not prove: Does not cover actual filesystem and formatting overhead, which consumes space in addition to the unit effect; does not exonerate genuinely defective or fraudulently labeled devices; does not adjudicate every vendor's labeling practice.

Evidence reviewed 2026-07-20. Corrections and review policy.

Take it with you

The portable rule: If a reported capacity, speed, or quantity looks short, then check which unit system each side is using before suspecting loss or fraud.

Hardware purchasing

Convert drive labels to bytes before comparing against what the OS reports; a 7 to 10 percent shortfall at TB scale is the prefix gap.

Engineering dashboards

Label axes GiB or GB explicitly; an unlabeled 'GB' invites defect reports that are unit artifacts.

Network plans

Convert Mbps to MB per second with both the 8-bit byte and the decimal/binary prefix before judging a speed test.

Take it into the discussion

Need the conclusion, boundary and sources without the challenge?

Open the same page in its conclusion-first reading state, then declare the work context before copying a stable reference.

Use as a reference →

1 TB = 931.3 GiB. The bytes are all there.

Use as a reference

Why Does a 1 TB Drive Show Only 931 GB?

Related puzzles

Need the conclusion, boundary and sources without the challenge?