Mebibyte to Gibibyte

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.

GB (gigabyte) = 10⁹ bytes = 1,000,000,000 bytes (SI decimal). GiB (gibibyte) = 2³⁰ bytes = 1,073,741,824 bytes (IEC binary). GiB is 7.37% larger. This is why a 1 TB hard drive labelled by the manufacturer (using 10¹² bytes) appears as approximately 931 GiB in Windows or Linux (which divide by 1,073,741,824). Neither value is wrong; they use different counting systems.

Early PC games (1990s) fit on a few floppy disks — under 10 MiB. CD-era games (late 1990s) reached 650 MiB. DVD-era titles hit 4–8 GiB. Modern AAA games like Call of Duty or Flight Simulator now exceed 100–200 GiB due to uncompressed 4K textures, high-fidelity audio in multiple languages, and pre-rendered cinematics. The growth rate has outpaced Moore's Law: storage needs roughly double every 2–3 years for top-tier games, driven primarily by texture resolution increases that scale quadratically with pixel count.

A module sold as "16 GB" RAM by manufacturers means 16 × 10⁹ = 16,000,000,000 bytes? No — RAM is actually built in binary powers. A "16 GB" RAM module contains exactly 2³⁴ = 17,179,869,184 bytes = 16 GiB. In this case, the manufacturer is using "GB" to mean GiB — unlike hard drives, where manufacturers genuinely use decimal GB. RAM capacities are always powers of 2 in gibibytes.

A 512 GB SSD (decimal, as labelled by the manufacturer) holds 512,000,000,000 bytes. Divide by 1,073,741,824 to get GiB: 512,000,000,000 ÷ 1,073,741,824 ≈ 476.8 GiB. After OS overhead and firmware reserved space, the usable capacity shown in the OS is typically 450–465 GiB for a nominally 512 GB drive.

Yes — GiB is the technically correct unit for binary memory. RAM, CPU cache, and GPU memory are all physically organized in powers of 2, making GiB the natural unit. The JEDEC memory standard (the body that defines RAM specifications) officially uses the IEC GiB notation, even though product packaging often says "GB" for commercial reasons. In engineering and OS development contexts, GiB is the preferred term.