Exbibyte to Mebibit

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.

A megabit (Mb) = 1,000,000 bits (SI decimal). A mebibit (Mibit) = 1,048,576 bits (IEC binary = 2²⁰ bits). The mebibit is 4.857% larger. Network speeds use megabits (Mb); embedded memory and flash storage specifications use mebibits when binary precision is required.

Mebibit appears primarily in microcontroller and microprocessor datasheets (e.g. "2 Mibit flash memory"), FPGA configuration file sizes, and some wireless protocol standards (802.11 frame size limits, Bluetooth payload specifications). It is rarely seen in consumer-facing applications but is common in embedded systems engineering documentation.

Yes. In 2007, a class-action settlement required Western Digital to pay $2.1 million because their hard drives advertised capacity in decimal megabits/gigabits while operating systems reported binary values — making drives appear ~7% smaller than labeled. Similar suits hit Seagate and Samsung. These lawsuits accelerated industry adoption of IEC prefixes and pushed Apple (2009) and later Windows (2021) to clarify their capacity labeling.

SPI flash chips are addressed at the bit level during serial communication — the programr shifts data in one bit at a time over the SPI bus. Datasheets specify capacity in mebibits (e.g. W25Q16 = 16 Mibit = 2 MiB) because the serial interface operates on bits, not bytes. Calculating transfer time requires bit-level math: reading a full 16 Mibit chip at 80 MHz SPI clock takes about 0.2 seconds.

Flash memory chips organise storage in binary-aligned blocks (sectors, pages) whose sizes are powers of 2. Specifying capacity in mebibits (1,048,576 bits per Mibit) maps precisely to the physical organisation of the memory array. Using decimal megabits would result in non-integer block counts, making datasheet specifications harder to verify against hardware design.