| Zebioctets per second (Zio/s) | Kibioctets per second (Kio/s) |
|---|---|
| 1 Zebioctet per second | 1.15292150461 × 1018 Kio/s |
| 2 Zebioctets per second | 2.30584300921 × 1018 Kio/s |
| 3 Zebioctets per second | 3.45876451382 × 1018 Kio/s |
| 4 Zebioctets per second | 4.61168601843 × 1018 Kio/s |
| 5 Zebioctets per second | 5.76460752303 × 1018 Kio/s |
| 10 Zebioctets per second | 1.15292150461 × 1019 Kio/s |
| 20 Zebioctets per second | 2.30584300921 × 1019 Kio/s |
| 25 Zebioctets per second | 2.88230376152 × 1019 Kio/s |
| 50 Zebioctets per second | 5.76460752303 × 1019 Kio/s |
| 100 Zebioctets per second | 1.15292150461 × 1020 Kio/s |
| Reference | Zebioctets per second (Zio/s) | Kibioctets per second (Kio/s) |
|---|---|---|
| A dial-up modem | 5.92923 × 10-18 Zio/s | 6.83594 Kio/s |
| Typical home broadband | 1.05879 × 10-14 Zio/s | 12207 Kio/s |
| Gigabit Ethernet | 1.05879 × 10-13 Zio/s | 122070 Kio/s |
| Streaming a 4K film | 2.64698 × 10-15 Zio/s | 3051.76 Kio/s |
The zebioctet per second is a unit of data transfer rate equal to 1,024 exbioctets per second, or two to the seventieth power octets per second. Its symbol is Zio/s. It is the binary counterpart of the zettaoctet per second, and the two differ by 18.1 per cent.
A link running at this rate would transfer everything humanity has ever stored several times over in a single second. That is the plainest way to describe how far it lies beyond anything that exists, is planned, or has been seriously proposed. The unit is a name for a quantity, not a description of a thing.
It is worth being precise about why such names are still defined. A measurement system is a set of rules, and the value of a rule is that it applies without exception. The moment a system says that certain prefix-and-unit combinations are legal and others are not, every user must carry a table instead of a rule, and different users will carry different tables. Complete definition is cheaper and safer.
The physical obstacles are not merely large but qualitative. At a zebioctet per second, the energy needed to switch the required number of states, even at the thermodynamic minimum, becomes a substantial power; the practical figure for real electronics is many orders of magnitude above that; and the number of parallel channels required exceeds anything that could be built and cooled. These are not engineering targets.
The 18.1 per cent gap from the decimal unit continues the pattern that runs through the whole binary series. Each step multiplies the discrepancy by 1.024, so a convention that was harmless at the kibioctet has become, by this point, a difference no reader could overlook. Making that visible is the purpose the IEC prefixes serve.
In practice, a converter meets this unit only in a complete table or in a document exploring theoretical limits. Handling it correctly costs nothing and demonstrates that the tool applies its rules uniformly, which is the property that makes its ordinary answers trustworthy.
One zebioctet per second equals 1,024 exbioctets per second, 1,180,591,620,717,411,303,424 octets per second, or about 1.181 zettaoctets per second.
The kibioctet per second is a unit of data transfer rate equal to 1,024 octets per second, and therefore to 8,192 bits per second. Its symbol is Kio/s. Unlike most of the binary rate units it is genuinely common, because the command-line tools that copy, download and synchronise files have reported in it for decades.
The reason is straightforward. Those tools count what they have moved in blocks, and blocks are powers of two. A program that reads in four-kibioctet pieces and divides the total by elapsed time produces a rate in kibioctets per second, and reporting it in decimal kilooctets would require an extra multiplication for no benefit. The unit is what the arithmetic naturally produces.
Anyone who has watched a file copy on a Unix-like system has seen the figure. Download utilities, archive tools, disc-writing commands and network file transfer programs all report progress in kibioctets or mebioctets per second, and most of them label it correctly with the lowercase i. It is one of the few places where the IEC prefixes are used consistently in everyday software.
For scale, a kibioctet per second moves about a thousand characters of text each second: a short letter in a second, a novel in about ten minutes. It is a rate at which a modern web page will not load in any reasonable time, so seeing it in a progress display usually means something has gone wrong with the connection rather than that the transfer is nearly finished.
The difference from a kilooctet per second is 2.4 per cent, which nobody notices. The value of using the binary unit here is not accuracy but honesty: the number came from a binary computation, and writing it with a binary prefix says so. A reader who wants the decimal figure can convert; a reader given a decimal label for a binary number cannot recover anything.
Comparing the reading with an advertised connection speed requires two steps: multiply by eight to get bits, and adjust by 2.4 per cent for the base. In practice the second step is beneath the noise of any real measurement, and the first is the one that matters.
One kibioctet per second equals 1,024 octets per second, 8,192 bits per second, or 1.024 kilooctets per second.