Bit to Mebibyte

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.

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.