Petabit to Byte

One petabit = 10¹⁵ bits = 125 terabytes. To put it in perspective: the entire text content of all English Wikipedia articles is roughly 4 GB — so a petabit could hold about 31,000 copies of it. A petabit per second link could transfer all of Wikipedia's text content in about 32 microseconds.

As of 2024, no single commercial link carries 1 Pbps, but laboratory experiments have demonstrated fiber optic transmission exceeding 1 Pbps using dense wavelength-division multiplexing on a single fiber strand. Commercial submarine cables aggregate hundreds of terabits per second across many fibers and wavelengths, collectively reaching petabit-scale capacity per cable system.

A petabit (Pb) = 10¹⁵ bits. A petabyte (PB) = 10¹⁵ bytes = 8 petabits. Storage systems (data centers, archival systems) use petabytes for capacity; aggregate network throughput uses petabits per second. An exabyte-scale data center stores 1,000 petabytes; its internal network may carry multiple petabits per second of traffic.

Qubits and classical bits solve fundamentally different problems — qubits will not simply replace petabit-scale classical storage or networking. A quantum computer with 1,000 logical qubits can explore 2¹⁰⁰⁰ states simultaneously, but measuring those qubits collapses them to classical bits. Quantum networks will likely handle key distribution and entanglement sharing at kilobit-to-megabit rates, while classical infrastructure continues to move petabits of bulk data. The two technologies are complementary, not substitutional.

Submarine fiber optic cables are built by a handful of companies (SubCom, NEC, Alcatel Submarine Networks) and typically cost $200–500 million per system. A modern cable contains 12–24 fiber pairs, each carrying hundreds of wavelengths via dense wavelength-division multiplexing, reaching 400+ Tbps aggregate capacity per cable. Cables are designed to last 25 years on the ocean floor. When faults occur, specialised cable repair ships (fewer than 60 exist worldwide) locate breaks using optical time-domain reflectometry and splice repairs at sea — a process that can take days to weeks depending on depth and weather.

A byte contains exactly 8 bits. This is the universal modern standard, though early computing used variable byte sizes (5, 6, or 7 bits). The 8-bit byte became universal with the IBM System/360 in 1964. Eight bits allow 256 possible values (0–255), sufficient to encode all ASCII characters with room for control codes.

Eight bits became standard because it is the smallest power of two that can encode all 128 ASCII characters (7 bits) with a spare bit for parity checking or extended character sets. It also maps cleanly to two hexadecimal digits (0x00–0xFF), making it convenient for low-level programming and hardware design. Earlier systems used 6-bit or 7-bit bytes; 8-bit won due to IBM's dominance in the 1960s–70s.

A nibble (also spelled nybble) is 4 bits — half a byte. A nibble represents exactly one hexadecimal digit (0–F). The term is used in low-level programming, embedded systems, and BCD (binary-coded decimal) encoding. It is not an SI unit and rarely appears in general computing contexts outside of hardware and systems programming.

It depends on the character and encoding. In UTF-8 (the dominant web encoding): ASCII characters (A–Z, 0–9) use 1 byte; common European accented characters use 2 bytes; most Asian scripts (Chinese, Japanese, Korean) use 3 bytes; emoji and rare characters use 4 bytes. A plain English text file is efficiently encoded as 1 byte per character in UTF-8.

In most modern usage, byte and octet are synonymous — both mean 8 bits. "Octet" is preferred in networking standards (RFC documents, ITU specifications) to avoid ambiguity from early computing where byte sizes varied. Internet protocol headers are specified in octets; operating systems and storage devices use bytes. In practice you will encounter "octet" mainly in formal networking documentation.