Exabyte to Nibble

One exabyte = 1,000,000 terabytes = 1,000 petabytes. If you filled 1 TB external hard drives and stacked them end to end, 1 EB worth would stretch roughly 200 km. In content terms: 1 EB can store about 250,000 years of HD video, or about 100 billion hours of music at 128 kbps. All the data produced by the Large Hadron Collider per year is about 15 petabytes — still 67× less than one exabyte.

Global data creation, capture, copy, and consumption is estimated at roughly 2.5 exabytes per day (IDC 2023 estimate), growing roughly 23% annually. This includes IoT sensor readings, financial transactions, social media posts, surveillance camera footage, scientific instrument output, and all other digital activity. Most of this data is transient and never stored long-term.

Amazon Web Services, Microsoft Azure, and Google Cloud each store estimated tens to hundreds of exabytes of customer data in their cloud platforms. Meta (Facebook/Instagram) stores an estimated 100+ exabytes across all data types. The NSA's Utah Data Center is estimated to hold yottabytes in capability, though actual stored volumes are classified. Collectively, global cloud storage is in the hundreds-of-exabytes range.

An exabyte (EB) = 10¹⁸ bytes (SI decimal). An exbibyte (EiB) = 2⁶⁰ bytes = 1,152,921,504,606,846,976 bytes — about 15.3% larger. This is the largest practically relevant gap between SI and IEC units in storage contexts. For a data center procuring 10 EB of storage, the SI vs IEC difference represents about 1.5 EB of capacity discrepancy in the contract.

Data archaeology is the practice of recovering information from obsolete storage media and formats — 9-track magnetic tapes, 8-inch floppy disks, MiniDiscs, Zip drives, and early optical formats. The challenge is threefold: hardware to read the media no longer exists or is failing, file formats and encoding schemes are undocumented, and magnetic media degrade over time (tape has a 10–30 year shelf life). At exabyte scale, organisations like national archives face the prospect of vast digital collections becoming unreadable within decades. Active migration strategies — periodically copying data to current formats and media — are the only reliable defense, but the cost scales linearly with data volume.

A nibble is 4 bits, or half a byte. It encodes one hexadecimal digit (values 0–15, represented as 0–9 and A–F). Nibbles are important in BCD (binary-coded decimal) encoding, where decimal digits are packed two per byte (each digit occupying one nibble). Packed BCD is used in financial systems and legacy databases to represent decimal numbers without floating-point rounding errors.

Hexadecimal (base 16) maps perfectly to nibbles because 4 bits can represent exactly 16 values (2⁴ = 16). One byte = two nibbles = two hex digits. A byte value of 0xFF (255 in decimal) is two nibbles: F (1111) and F (1111). This mapping makes hexadecimal the natural notation for expressing binary data — programrs use hex because one hex digit always represents a fixed number of bits.

Binary-Coded Decimal (BCD) encodes each decimal digit (0–9) as a 4-bit binary value (nibble). Two decimal digits fit in one byte using "packed BCD". For example, the decimal number 47 is stored as 0100 0111 in packed BCD — each nibble holds one digit. BCD avoids the rounding errors of binary floating-point, which is why it is used in financial software, calculators, and legacy banking systems.

A nibble = 4 bits (1 hex digit). A byte = 8 bits (2 hex digits, 2 nibbles). A word = typically 16, 32, or 64 bits depending on the processor architecture (see the "word" unit for details). These are the fundamental granularities of digital data: nibble for hex/BCD, byte for text and addressing, word for native processor arithmetic.

Nibbles are rarely referenced directly in modern high-level programming but remain fundamental at the hardware level. Embedded systems, FPGA design, network packet parsing, and hardware description languages (VHDL, Verilog) regularly manipulate nibbles. The nibble is also the key concept behind hexdump utilities — the canonical way to inspect raw binary files and network packets.