The full IEC ladder
- kB = 1,000 B · KiB = 1,024 B
- MB = 10⁶ B · MiB = 1024² B = 1,048,576 B
- GB = 10⁹ B · GiB = 1024³ B = 1,073,741,824 B
- TB = 10¹² B · TiB = 1024⁴ B = 1,099,511,627,776 B
- PB = 10¹⁵ B · PiB = 1024⁵ B = 1,125,899,906,842,624 B
How much the gap grows
Each step adds 2.4% on top of the decimal figure, and the effects compound: one step is 2.4%, three steps (bytes to gibibytes) is 7.4%, five steps (petabytes) is 12.6%. That is why the discrepancy is invisible for small files and unmissable at drive sizes — and why comparing a 4 PB cloud bill against local binary tooling can look like an 11% accounting error.
Why the IEC bothered to define MiB
In the 1990s, disk manufacturers and software vendors argued about who was misleading consumers — the same drive was “1 GB” to one and “0.95 GB” to the other. The IEC resolved it by naming both quantities: the SI family keeps decimal powers, and a new binary family carries the -i- syllable. Adoption stayed partial: Linux and technical standards use MiB, while Windows and most consumer software still write “MB” for the binary value.
Practical rules
- Buying storage: trust the decimal label, expect the binary display.
- Networking: everything is decimal (Mbps, Gbps, and GB of data plans).
- Memory and caches: RAM is binary, so a “16 GB” DIMM is 16 GiB.
- Backups and quotas: check whether the tool counts decimal (billing) or binary (local display).
- When precision matters, state bytes — no unit naming can distort a byte count.