Gibibit to Mebibyte

A gigabit (Gbit) = 10⁹ bits = 1,000,000,000 bits (SI). A gibibit (Gibit) = 2³⁰ bits = 1,073,741,824 bits (IEC binary). The difference is 7.37%. Consumer networking equipment and ISP speed ratings use decimal gigabits; memory and chip designers sometimes use gibibits when binary precision is required.

Virtually all networking equipment — routers, switches, NICs, ISP speed ratings — uses decimal gigabits (Gbit). A "1 Gbps" (gigabit per second) connection means exactly 1,000,000,000 bits per second, not 1,073,741,824 bits per second. Network standards (Ethernet IEEE 802.3) are defined in SI units.

DDR memory bandwidth is calculated from clock speed, bus width, and transfers per clock. A DDR5-4800 module on a 64-bit bus delivers 4,800 MT/s × 64 bits = 307,200 Mbit/s ≈ 292.97 Gibit/s. Engineers use gibibits when verifying that memory throughput matches binary-aligned cache line sizes (typically 512 bits = 64 bytes), ensuring no fractional transfers occur during burst reads.

GPU memory bandwidth is typically quoted in gigabytes per second (GB/s) using SI decimal values — not gibibits. For example, NVIDIA's RTX 4090 has 1,008 GB/s of memory bandwidth (decimal). Some academic papers and IEEE publications convert this to GiB/s or Gibit/s for precision, but consumer GPU marketing universally uses SI decimal units.

Gibibit appears in: IEEE standards documents specifying memory interface speeds, JEDEC memory specifications, some academic networking papers, and storage controller datasheets. Consumer-facing software, marketing materials, and OS interfaces virtually never display gibibits — they show gigabits (networking) or gigabytes (storage). It is primarily a precision engineering unit.

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.