Kibibyte to Bit

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 bit is a single binary value (0 or 1); a byte is a group of 8 bits. Bytes are the standard unit for file sizes, memory, and storage. Network speeds are typically quoted in bits per second (Mbps), while file sizes use bytes (MB) — so a 100 Mbps connection downloads 100 megabits, or about 12.5 megabytes, per second.

Networking hardware physically transmits one bit at a time over a wire or radio signal, so bits per second is the natural unit for measuring throughput. The convention predates widespread file-size awareness. When you see "100 Mbps broadband", your actual download speed in MB/s is about 1/8 of that — roughly 12.5 MB/s.

A classical bit is definitively 0 or 1. A qubit can exist in a superposition of both states simultaneously, described by two complex probability amplitudes. When measured, a qubit collapses to 0 or 1 — yielding one classical bit of information. The power of qubits lies in entanglement and interference during computation, not in storing more data per unit. A 100-qubit quantum computer does not store 100 bits more efficiently; it explores 2¹⁰⁰ computational paths in parallel for specific algorithm types like factoring and search.

Information theory, developed by Claude Shannon in 1948, quantifies how much information a message contains. One bit is the amount of information needed to resolve a choice between two equally likely outcomes. This abstraction underpins all digital compression, encryption, and error-correction — from MP3 audio to HTTPS security.

In practice, modern computers cannot address or store a single bit individually — the minimum addressable unit is one byte (8 bits). Trying to store a single bit requires a full byte, with 7 bits unused. Some specialised hardware and bit-packing algorithms can store multiple boolean values per byte, but standard memory hardware works at byte granularity.