Exbibyte to Mebibyte

EB (exabyte) = 10¹⁸ bytes (SI decimal). EiB (exbibyte) = 2⁶⁰ bytes = 1,152,921,504,606,846,976 bytes (IEC binary). EiB is 15.29% larger. This is the largest practically significant SI vs IEC discrepancy: per exbibyte, the binary value exceeds the decimal value by approximately 152,921,504,606,846,976 bytes — about 152.9 petabytes.

One exbibyte (EiB) ≈ 1.153 × 10¹⁸ bytes = 1,073,741,824 GiB = 1,048,576 TiB. In practical terms: enough to store approximately 230 billion JPEG photos at 5 MB each, or 288,230,376 copies of a 4 GB HD movie, or the entire text content of the English internet many thousands of times over.

In theory, yes — and with astonishing density. DNA can encode about 215 PiB per gram of material, meaning a single EiB could fit in roughly 4.7 grams of synthetic DNA. Researchers at Microsoft and the University of Washington have demonstrated writing and reading megabytes of data in DNA strands. The challenges are speed and cost: current DNA synthesis writes about 400 bytes per second and costs around $3,500 per megabyte. At that rate, writing 1 EiB would take billions of years and cost more than global GDP. However, enzymatic synthesis breakthroughs could reduce costs by 6–8 orders of magnitude within decades.

Storing 1 EiB on modern HDDs would require roughly 57,000 drives of 20 TB each, consuming about 400–500 kW of power just for the drives — plus 200–300 kW for cooling, networking, and overhead. That totals roughly 6 GWh per year, equivalent to powering about 550 US homes. At typical US grid carbon intensity, this produces around 2,500 tonnes of CO₂ annually. Hyperscale operators reduce this via renewable energy and immersion cooling, but the fundamental physics of spinning magnetic platters or maintaining NAND charge states sets a floor on energy consumption that no software optimisation can eliminate.

After exbibyte (EiB, 2⁶⁰ bytes) come: zebibyte (ZiB, 2⁷⁰ bytes) and yobibyte (YiB, 2⁸⁰ bytes), as defined in IEC 80000-13. These are recognized standard units but have no current practical applications. The entire global internet's estimated stored data (hundreds of EB) is still in the low hundreds of EiB range — well short of one ZiB.

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.