Kibibyte to Gibibit

KB (kilobyte, SI) = 1,000 bytes. KiB (kibibyte, IEC binary) = 1,024 bytes. The difference is 24 bytes (2.4%) — small individually but the source of the well-known discrepancy between storage manufacturer labels and OS-reported sizes. Storage manufacturers use KB = 1,000 bytes; operating systems traditionally used KB = 1,024 bytes (now correctly called KiB).

Linux memory management, filesystem block sizes, and page sizes are all powers of 2 (typically 4,096 bytes = 4 KiB). Using kibibytes aligns with the physical hardware structure. The GNU coreutils (df, du, ls -h) display sizes in KiB, MiB, GiB by default for consistency with how the kernel allocates memory and disk blocks — decimal kilobytes would produce fractional values for normal aligned allocations.

Most languages expose both conventions depending on the API. Java's Runtime.totalMemory() returns bytes aligned to KiB (binary), but Files.size() returns raw byte counts that file managers may display as decimal KB. Python's os.path.getsize() returns bytes — the developer chooses how to format. Go's humanize library defaults to IEC (KiB) while many JavaScript libraries default to SI (KB). This inconsistency means the same file can appear as different sizes across tools written in different languages.

A memory page is the smallest unit of memory the OS allocates from physical RAM. Most modern CPUs use 4 KiB (4,096 byte) pages; some support 2 MiB or 1 GiB "huge pages" for performance. Every memory allocation is rounded up to the nearest page boundary. This binary alignment is why computer memory sizes are always powers of 2 (4 GB, 8 GB, 16 GB RAM) rather than round decimal numbers (5 GB, 10 GB).

The 3.5-inch floppy's capacity was 1,474,560 bytes — which is neither 1.44 MB (1,440,000 bytes) nor 1.44 MiB (1,509,949 bytes). The label came from a hybrid calculation: 80 tracks × 2 sides × 18 sectors × 512 bytes = 1,474,560 bytes, then divided by 1,000 to get 1,474.56 KB, then divided by 1,024 to get "1.44 MB." This mix of decimal and binary division in the same label is one of the most famous unit blunders in computing history.

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.