Mebibyte to Kibibit

MB (megabyte) = 1,000,000 bytes (SI decimal). MiB (mebibyte) = 1,048,576 bytes (IEC binary). MiB is 4.86% larger. This gap is why a file manager on Linux showing "512 MiB" of free RAM and a marketing sheet showing "512 MB" of RAM are technically different: the marketing sheet refers to fewer bytes.

The original CD-ROM standard defined capacity as 74 minutes of audio or 650,000,000 bytes. Technically this is 650 MB in SI terms, or approximately 620 MiB (since 650,000,000 ÷ 1,048,576 ≈ 620). However, the CD industry loosely used "MB" to mean 650 × 10⁶ bytes. Some media used 700 MB (≈ 668 MiB). This inconsistency is a classic example of the pre-IEC ambiguity.

Docker reports image sizes in decimal MB (e.g., "docker images" shows 150 MB), but the underlying layer storage on disk uses binary-aligned block sizes. A "150 MB" Docker image actually occupies roughly 143 MiB on disk before compression. Compressed layers further complicate things: a 150 MB uncompressed image might only transfer 50 MB over the network. Container registries like Docker Hub display compressed sizes, while "docker images" shows uncompressed — leading to frequent confusion in CI/CD pipeline size budgets.

One mebibyte (1,048,576 bytes) holds about: one minute of MP3 audio at 128 kbps (≈ 960 kB, so slightly under 1 MiB), a medium-resolution JPEG photo (0.5–2 MiB), about 200 pages of plain text, or the complete text of a short novel. A typical Linux kernel image at boot is 8–12 MiB compressed.

RAM chips are physically organized as binary address grids — each address line doubles the capacity, so sizes must be exact powers of 2 (4 GiB = 2³² bytes, 8 GiB = 2³³ bytes). USB flash drives use NAND flash that is also binary internally, but manufacturers reserve variable amounts for wear levelling, bad block management, and controller firmware. A "64 GB" USB drive might have 64 GiB of raw NAND but only expose 59.6 GiB (64 × 10⁹ ÷ 2³⁰) to the user — the label uses decimal marketing, unlike RAM which honestly reflects binary sizing.

A kilobit (kb) = 1,000 bits (SI decimal). A kibibit (Kibit) = 1,024 bits (IEC binary). The difference is 24 bits (2.4%) — small but matters in precise hardware specifications. The kibibit was introduced in 1998 to provide an unambiguous binary unit, since networking engineers had been using "kilobit" to mean both 1,000 and 1,024 bits in different contexts.

For decades, computer engineers used SI prefixes (kilo-, mega-, giga-) to mean powers of 1,024 in binary contexts and powers of 1,000 in SI/metric contexts. This caused real confusion: a "64 kilobyte" RAM chip had 65,536 bytes, while a "64 kilobyte" internet packet had 64,000 bytes. The IEC defined kibi- (1,024), mebi- (1,048,576), etc. in 1998 to give engineers unambiguous binary units.

Kibibits are rarely used directly in OS user interfaces — OSes work in bytes and their binary multiples (KiB, MiB, GiB). Kibibits appear in hardware documentation, FPGA bitstream sizes, and some network protocol headers where binary bit counts matter. Network speeds remain in decimal kilobits per second even in technical contexts.

Before IEC 80000-13 (1998), "kilobit" meant either 1,000 or 1,024 bits depending on context — RAM datasheets used 1,024 while telecom specs used 1,000. The IEC standard introduced kibibit (1,024 bits) as the unambiguous binary term, reserving kilobit strictly for 1,000 bits. Adoption took over a decade: Linux adopted IEC prefixes around 2010, and JEDEC still allows the old dual-meaning convention for memory marketing.

IEC binary prefixes have been slowly adopted: Linux tools (df, free) now use GiB and MiB; macOS used decimal GB since 2009; Windows switched to GiB labeling in Windows 10/11. However, kibibit specifically remains a niche technical term — consumer-facing software almost never uses it. Engineers working on embedded systems, FPGAs, and memory hardware are its primary audience.