| Kibioctets (Kio) | Zebibits (Zibit) |
|---|---|
| 1 Kibioctet | 6.93889390391 × 10-18 Zibit |
| 2 Kibioctets | 1.38777878078 × 10-17 Zibit |
| 3 Kibioctets | 2.08166817117 × 10-17 Zibit |
| 4 Kibioctets | 2.77555756156 × 10-17 Zibit |
| 5 Kibioctets | 3.46944695195 × 10-17 Zibit |
| 10 Kibioctets | 6.93889390391 × 10-17 Zibit |
| 20 Kibioctets | 1.38777878078 × 10-16 Zibit |
| 25 Kibioctets | 1.73472347598 × 10-16 Zibit |
| 50 Kibioctets | 3.46944695195 × 10-16 Zibit |
| 100 Kibioctets | 6.93889390391 × 10-16 Zibit |
| Reference | Kibioctets (Kio) | Zebibits (Zibit) |
|---|---|---|
| A plain text message (160 characters) | 0.15625 Kio | 1.0842 × 10-18 Zibit |
| A three-minute MP3 | 2929.69 Kio | 2.03288 × 10-14 Zibit |
| A smartphone photo | 3906.25 Kio | 2.71051 × 10-14 Zibit |
| A high-definition film | 3906250 Kio | 2.71051 × 10-11 Zibit |
| A dual-layer Blu-ray disc | 48828125 Kio | 3.38813 × 10-10 Zibit |
The kibioctet is a unit of digital information equal to 1,024 octets, and therefore to 8,192 bits. Its symbol is Kio. It is the binary counterpart of the kilooctet, and although the two differ by only 2.4 per cent, this is the unit in which a great deal of a computer's internal organisation is actually measured.
The most important example is the memory page. Processors do not manage memory octet by octet but in fixed-size blocks, and on almost every architecture in common use that block is 4 kibioctets. Every allocation a program makes is rounded up to a multiple of that, every entry in the page tables describes one of them, and the performance of a program often depends on how well its access pattern fits that four-kibioctet grid.
Disc sectors tell a similar story. Hard drives used 512-octet sectors for decades, and modern drives use 4 kibioctets, matching the memory page so that a page can be read or written in a single operation. Filesystems then allocate space in blocks that are themselves powers of two, usually 4 kibioctets, which is why a one-octet file consumes four kibioctets of disc.
Network protocols use the unit too. Buffer sizes, window sizes and the maximum size of many protocol structures are powers of two, and the 64-kibioctet limit appears repeatedly: it is the largest value a 16-bit length field can express, and it therefore caps the size of a UDP datagram, an IP packet and several older file formats.
That is the general pattern: wherever a limit comes from the width of a binary field, the limit is a power of two, and the honest way to write it is with a binary prefix. Writing 64 KB for the datagram limit is not wrong by much, but writing 64 KiB is exactly right and says where the number came from.
In everyday use the difference is invisible. A 200-kilooctet file and a 200-kibioctet file are 4.8 kibioctets apart, which nobody notices. The value of the distinction is that it makes the arithmetic behind a figure legible, which matters far more as the numbers grow.
One kibioctet equals 1,024 octets, 8,192 bits, 8 kibibits, or 1.024 kilooctets.
The zebibit is a unit of digital information equal to two to the seventieth power bits, which is 1,024 exbibits. Its symbol is Zibit. It is the binary counterpart of the zettabit, and the two now differ by 18.1 per cent — nearly a fifth.
That divergence is the reason the binary prefixes were needed at all. At the kibibit the two conventions differed by 2.4 per cent, a rounding error. Here the difference is large enough that a document using the wrong one is simply reporting a different quantity, and no amount of context can repair the ambiguity after the fact.
A zebibit is 147,573,952,589,676,412,928 octets, or 128 exbioctets. Nothing of this size exists. The total data held by humanity is somewhere in the low hundreds of zettaoctets, which is under a zebioctet, so the world's entire information stock does not yet reach one unit at this step of the binary ladder.
The unit exists because the IEC series was defined completely rather than as far as anyone then needed. That is the same principle the metric system follows: every prefix applies to every unit, whether or not the combination has yet been used. A system with holes in it requires a table of exceptions, and a system without holes requires only the rule.
Where the zebibit could genuinely appear is in address space arithmetic. Two to the seventieth is not a natural pointer width, but multiples and fractions of powers of two run through every discussion of addressing, and a scheme that reserved seventy bits for something would naturally be described in these terms. Such schemes are proposed occasionally and none has yet been needed.
Reading the symbol is the practical skill. Zibit is binary, Zbit is decimal, and at eighteen per cent apart the two are not interchangeable in any document where the number matters. Where a source writes ZB with no explanation, there is no way to know which was meant, and the honest response is to treat the figure as uncertain to a fifth.
One zebibit equals 1,024 exbibits, 147,573,952,589,676,412,928 octets, or about 1.181 zettabits.