Kilobyte to Exabit

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.

One exabit = 10¹⁸ bits = 125,000 terabytes = 125 petabytes. If every person on Earth (8 billion people) each stored 15 GB of data — roughly a modern smartphone's photos and messages — the total would be about 120 exabytes, or about 960 exabits. The entire human genome is about 1.5 GB; sequencing every person on Earth would produce about 12 exabytes of data.

Cisco's annual internet traffic reports estimated global IP traffic at roughly 4.8 exabytes per day in 2022, rising about 20% per year. Expressed in bits, that's about 38 exabits per day or roughly 440 petabits per second continuously. Video streaming accounts for over 60% of total internet traffic volume.

Data gravity is the principle that massive datasets attract applications, services, and additional data toward them — rather than being moved to where processing occurs. At exabit scale, physically transferring data becomes impractical: moving 1 exabit over a 100 Gbps link takes 116 days. Instead, companies deploy compute resources alongside the data. This effect drives cloud concentration — once an organisation stores exabits in AWS or Azure, the cost and latency of moving that data elsewhere creates powerful vendor lock-in, shaping the economics of the entire cloud industry.

The Square Kilometer Array (SKA), under construction in Australia and South Africa, will be the world's largest radio telescope. Its thousands of antennas will collectively produce roughly 1 exabit of raw sensor data per day — more than the entire global internet traffic of the early 2000s. This data cannot be stored in full; instead, on-site supercomputers reduce it by a factor of ~10,000 in real time, keeping only scientifically relevant signals. The SKA illustrates how radio astronomy pushes data processing to extreme scales that rival commercial internet infrastructure.

At 1 Gbps (a fast home connection), downloading 1 exabit would take 1 billion seconds — about 31.7 years. At 1 Tbps (a high-end data center link), it would take 1 million seconds, or about 11.6 days. This illustrates why exabit-scale data movements require massively parallel infrastructure — no single link or device handles exabit transfers directly.