Mebibyte to Kilobyte

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.

In the SI decimal system (used by storage manufacturers), 1 kB = 1,000 bytes. In the older binary convention (used by operating systems and programrs), what was called a "kilobyte" was actually 1,024 bytes — now formally called a kibibyte (KiB). The IEC standardized the KiB prefix in 1998 to eliminate this ambiguity. Modern OS versions (Windows Vista+, macOS 10.6+) increasingly use the correct IEC binary prefixes for displayed values.

One kilobyte (1,000 bytes) can store approximately 1,000 ASCII characters, roughly half a page of plain text, or about 140–170 words. With UTF-8 encoding, common English text is still close to 1 byte per character. A full page of formatted text with some HTML markup is typically 3–6 kB.

Storage manufacturers measure 1 kB = 1,000 bytes (decimal). Operating systems traditionally reported 1 kB = 1,024 bytes (binary). A drive advertised as 1 TB (1,000,000,000,000 bytes by the manufacturer) shows as approximately 931 GiB in Windows — not a lie, but a different counting system. The IEC binary prefixes (KiB, MiB, GiB) were introduced in 1998 to clarify this, and most modern OSes now use them correctly.

Files under 1 MB are typically measured in kilobytes: text files (1–100 kB), favicons and tiny images (1–50 kB), simple HTML pages (10–200 kB), audio samples (under 1 second of compressed audio), configuration and log files. Once files exceed a few hundred kilobytes they are more conveniently expressed in megabytes.

Early email systems in the 1980s–90s imposed attachment limits of 50–100 kB due to tiny disk quotas and slow dial-up links. As infrastructure improved, limits rose: most modern email providers (Gmail, Outlook) cap attachments at 25 MB. The limits persist because email traverses multiple relay servers (MTAs), each with its own size constraint, and Base64 encoding inflates binary attachments by ~33%. Some corporate and government systems still enforce 5–10 MB limits for security scanning and archival compliance. For larger files, email providers redirect to cloud links (Google Drive, OneDrive) rather than raising the attachment ceiling.