| Kibibits (Kibit) | Kibioctets (Kio) |
|---|---|
| 1 Kibibit | 0.125 Kio |
| 2 Kibibits | 0.25 Kio |
| 3 Kibibits | 0.375 Kio |
| 4 Kibibits | 0.5 Kio |
| 5 Kibibits | 0.625 Kio |
| 10 Kibibits | 1.25 Kio |
| 20 Kibibits | 2.5 Kio |
| 25 Kibibits | 3.125 Kio |
| 50 Kibibits | 6.25 Kio |
| 100 Kibibits | 12.5 Kio |
| Reference | Kibibits (Kibit) | Kibioctets (Kio) |
|---|---|---|
| A plain text message (160 characters) | 1.25 Kibit | 0.15625 Kio |
| A three-minute MP3 | 23437.5 Kibit | 2929.69 Kio |
| A smartphone photo | 31250 Kibit | 3906.25 Kio |
| A high-definition film | 31250000 Kibit | 3906250 Kio |
| A dual-layer Blu-ray disc | 390625000 Kibit | 48828125 Kio |
The kibibit is a unit of digital information equal to 1,024 bits. Its symbol is Kibit. It is the first of the binary prefixes, a set of units defined by the International Electrotechnical Commission in 1998 to end a confusion that had run through computing since the 1960s.
The problem was straightforward. Computers address memory in powers of two, so memory came in chunks of 1,024 rather than 1,000. Engineers borrowed the metric prefix kilo for that quantity because 1,024 is close to 1,000, and for small numbers the approximation was harmless. But storage and transmission counted in true thousands, so the same prefix meant two different things depending on which part of the machine was being described.
The IEC's solution was to coin new names. Kibi is a contraction of kilo binary, and the pattern continues with mebi, gibi, tebi, pebi, exbi, zebi and yobi. Each is 1,024 times the one below, and each symbol takes the form of a capital letter followed by a lowercase i: Ki, Mi, Gi, Ti and so on. The kilobit then means one thousand bits and nothing else.
A kibibit is 128 octets, and the gap from a kilobit is 2.4 per cent. That small difference is why the two were confused for so long: at this scale nobody notices. The error compounds by 2.4 per cent at every step, reaching 5 per cent at the mebibit, 7 per cent at the gibibit and 21 per cent by the yobibit, which is where the ambiguity became genuinely expensive.
Adoption has been partial and uneven. Standards bodies, the Linux kernel and most technical documentation use the IEC prefixes correctly. Consumer software largely does not, and many programs still write KB while dividing by 1,024. The result is that a reader must often infer from context which convention a number follows, which is exactly what the standard was written to prevent.
In practice the kibibit itself appears mainly in the specifications of small memory chips, in serial memory used by embedded systems, and in protocol documents where an exact power of two matters. Anywhere the number 1,024 is meant rather than 1,000, this is the correct unit.
One kibibit equals 1,024 bits, 128 octets, or 1.024 kilobits.
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.