The short answer: Eight bits make one byte. Decimal prefixes count powers of ten — 1 kB is 1,000 bytes, 1 GB is 10⁹ bytes, 1 TB is 10¹² bytes. Binary prefixes count powers of two — 1 KiB is 1,024 bytes and 1 GiB is 1,073,741,824 bytes. A 1 TB drive holds exactly 1,000,000,000,000 bytes, which is 931.3 GiB, displayed as “931 GB” by systems that use binary math with decimal labels. The capacity is not missing; the label is ambiguous.

Key takeaways

  • One byte is eight bits. Network speeds are quoted in bits per second; file sizes are quoted in bytes.
  • Decimal and binary prefixes differ by 2.34% per step and about 9% by the terabyte scale.
  • A 1 TB drive is 931 GiB. That is the single most common source of “missing space” complaints.
  • Formatted capacity is smaller again because file systems and firmware reserve space.
  • Transfer time = size in bits ÷ bit rate. Convert bytes to bits before dividing.

Bits, bytes, and the factor of eight

A bit is a single binary digit, 0 or 1. A byte is eight bits, historically the smallest addressable unit in most computers; a nibble is four bits, half a byte. Storage is sold in bytes, while network links are sold in bits per second, so every download estimate crosses the factor of eight. A 100 Mbps connection delivers 100 ÷ 8 = 12.5 MB/s under perfect conditions, and closer to 11–11.5 MB/s after protocol overhead. A 1 Gbps link is 125 MB/s ideal.

The capital letter matters. Mb/s means megabits per second; MB/s means megabytes per second. A file manager reporting 12 MB/s is showing roughly 96 Mb/s of throughput. Confusing the two makes a connection look eight times faster or slower than it is, which is why internet plans are advertised in bits and disk sizes in bytes.

To estimate a transfer, convert the file size to bits, then divide by the rate. A 10 GB file is 80 billion bits; at 50 Mbps that is 1,600 seconds, or 26.7 minutes, before overhead. A 25 GB Blu-ray image at 100 Mbps takes about 33 minutes. These are lower bounds: latency, contention, and protocol overhead add time, especially for many small files.

Decimal prefixes and binary prefixes

The International System of Units uses prefixes that step by powers of ten: kilo (10³), mega (10⁶), giga (10⁹), tera (10¹²), and peta (10¹⁵). These are the prefixes on the box. The International Electrotechnical Commission defined a parallel set for powers of two in IEC 80000-13: kibi (2¹⁰ = 1,024), mebi (2²⁰), gibi (2³⁰), tebi (2⁴⁰), and pebi (2⁵⁰), with the symbols KiB, MiB, GiB, TiB, and PiB. NIST publishes the same definitions and warns that the binary prefixes are not part of the SI.

The ambiguity is historical. Early memory was addressed in binary, so a “kilobyte” of RAM meant 1,024 bytes, and the habit spread to files and disks. Disk manufacturers used decimal definitions because they were selling raw media and because powers of ten made larger numbers. Both usages were widespread by the time the IEC standardized the binary prefixes in 1998, and the old habit never disappeared from operating systems.

Today the same 1 TB drive appears as 1.00 TB on macOS, which reports decimal units, and as 931 GB on Windows, which computes binary values but prints the decimal label. Linux tools vary by desktop and command. None of them is lying; they are using different definitions and, in Windows’ case, an old label.

The arithmetic behind a shrinking drive

Each binary step is 1,024 ÷ 1,000 = 1.024 times larger than the decimal step, so the reported number is 1000 ÷ 1024 = 0.9765625 of the marketed number per prefix. Four steps for a terabyte compound to 0.9095, which is why roughly 9% disappears at that scale. The table shows the pattern.

Marketed capacity Bytes Binary equivalent
256 GB 256,000,000,000 238.4 GiB
500 GB 500,000,000,000 465.7 GiB
1 TB 1,000,000,000,000 931.3 GiB
2 TB 2,000,000,000,000 1,862.6 GiB (1.82 TiB)
4 TB 4,000,000,000,000 3,725.3 GiB (3.64 TiB)
8 TB 8,000,000,000,000 7,450.6 GiB (7.28 TiB)

The conversion is exact in both directions. To turn a marketed terabyte figure into the gibibytes a tool may show, multiply by 1,000,000,000,000 ÷ 1,073,741,824, which is 931.3. For tebibytes, divide the byte count by 2⁴⁰ instead. To go back, multiply the GiB figure by 1.073741824 to recover decimal GB.

Formatted capacity: the second, smaller shrink

Even after the prefix confusion is set aside, a formatted drive holds less than its raw capacity. File systems keep metadata: NTFS maintains a master file table, a journal, and allocation structures. Windows may reserve a recovery partition of several hundred megabytes to a gigabyte. SSDs reserve over-provisioning space, often around 7%, so that garbage collection and wear leveling have free blocks to work with; enterprise drives reserve more. Some drives also hide a small host-protected area.

Cluster size adds slack. A file system allocates in fixed blocks, so a folder of thousands of tiny files wastes part of each block. A 1 TB SSD may show 931 GiB unformatted and about 930 GiB formatted, then lose a little more to the operating system. A 128 GB phone, which markets decimal gigabytes, shows 119.2 GiB before the OS and often around 107 GiB free after system files and a recovery partition.

Cloud quotas follow the same decimal convention. A 15 GB free tier is 13.97 GiB, and a 2 TB plan is 1.82 TiB. When you are planning a backup, use the usable figure, not the marketed one, and leave headroom for snapshots and temporary files.

Transfer math and interface limits

Time equals size in bits divided by bit rate. A 2 GB upload at 20 Mbps is 16 billion bits ÷ 20 million bits per second = 800 seconds, or 13.3 minutes. A 1 TB backup at a sustained 100 MB/s takes 10,000 seconds, about 2.8 hours; at 250 MB/s it takes about 1.1 hours. Sustained rates matter more than burst rates for large transfers, and small files are limited by operations per second rather than raw bandwidth.

Interface names hide encoding overhead. USB 2.0’s 480 Mbps is 60 MB/s theoretical, but real devices often deliver 30–40 MB/s. USB 3.2 Gen 1’s 5 Gbps is 625 MB/s before line encoding, and about 500 MB/s after it. A drive that benchmarks at 500 MB/s on a fast port may fall to 400 MB/s or lower on a slower controller, and a SATA SSD tops out near the 6 Gbps SATA link rather than its own NAND speed.

Buying storage without surprises

Check four numbers before buying: raw capacity in decimal bytes, the interface, the sustained write speed after the cache is exhausted, and endurance in terabytes written for SSDs. For network-attached storage, check whether the drive uses shingled magnetic recording, which can stall on sustained writes. For a laptop, check whether the drive is soldered and whether the slot supports the length and keying of the upgrade you have in mind.

Plan for headroom. A drive that is 90% full slows down, especially an SSD, and a backup target should hold at least one full copy plus room for a second. RAID improves redundancy or speed but not capacity: RAID 1 halves usable space, and RAID 5 gives up one drive’s worth. RAID is not a backup, and sync is not a backup either, because deletions propagate.

Worked examples

4K video. 45 Mbps for two hours: 45,000,000 × 7,200 = 324 billion bits, or 40.5 GB.

Photo library. 500 raw files at 30 MB each is 15,000 MB, or 15 GB.

Phone capacity. 128 GB markets 119.2 GiB; after about 12 GiB of system files, roughly 107 GiB remains.

Backup target. 2 TB of data is 1.82 TiB. A 2 TB drive is 1.82 TiB raw, so it is effectively full before snapshots; a 4 TB drive leaves room.

1080p video. 8 Mbps for one hour: 8,000,000 × 3,600 ÷ 8 = 3.6 GB.

Frequently asked questions

Why does my 1 TB drive show 931 GB?

Because the drive holds 10¹² bytes and the system divides by 2³⁰, then labels the result GB. 10¹² ÷ 1,073,741,824 = 931.3.

Is a kilobyte 1,000 or 1,024 bytes?

A kilobyte (kB) is 1,000 bytes. A kibibyte (KiB) is 1,024 bytes. Older software often used “KB” for 1,024.

How many megabytes are in a gigabyte?

1,000 in decimal units and 1,024 in binary units. The difference grows with each prefix.

Why is my phone’s storage smaller than advertised?

The marketed number is decimal, the operating system and file system take space, and the reported number may be binary.

How long does it take to transfer 1 TB?

At a sustained 100 MB/s, about 2.8 hours; at 250 MB/s, about 1.1 hours. Small files and slow links take longer than the raw math suggests.

Does RAID increase capacity?

No. RAID 0 combines drives but risks all data; RAID 1 halves usable capacity; RAID 5 gives up one drive’s worth for parity.

Further reading

Keep exploring

Read next Hex to RGB: Color Codes, Channels, and Alpha A hex code is three base-16 channel values in one string. Learn how RR, GG, and BB become… Read next Density Conversion: kg/m³, g/cm³, and lb/ft³ Density is mass per volume, and the metric and imperial units are linked by exact factors. Learn the… Read next Base Conversion: Binary, Decimal, Hex, and Place Value Convert integers between binary, octal, decimal, and hexadecimal, with place-value arithmetic, direct bit grouping, exact limits, and the…

Decision path

Use this guide in a decision

Open Conversion Decision Center Open companion solver