| Tebibits (Tibit) | Kibioctets (Kio) |
|---|---|
| 1 Tebibit | 134217728 Kio |
| 2 Tebibits | 268435456 Kio |
| 3 Tebibits | 402653184 Kio |
| 4 Tebibits | 536870912 Kio |
| 5 Tebibits | 671088640 Kio |
| 10 Tebibits | 1342177280 Kio |
| 20 Tebibits | 2684354560 Kio |
| 25 Tebibits | 3355443200 Kio |
| 50 Tebibits | 6710886400 Kio |
| 100 Tebibits | 13421772800 Kio |
| Reference | Tebibits (Tibit) | Kibioctets (Kio) |
|---|---|---|
| A plain text message (160 characters) | 0.00000000116415 Tibit | 0.15625 Kio |
| A three-minute MP3 | 0.0000218279 Tibit | 2929.69 Kio |
| A smartphone photo | 0.0000291038 Tibit | 3906.25 Kio |
| A high-definition film | 0.0291038 Tibit | 3906250 Kio |
| A dual-layer Blu-ray disc | 0.363798 Tibit | 48828125 Kio |
The tebibit is a unit of digital information equal to 1,099,511,627,776 bits, which is 1,024 gibibits or two to the fortieth power. Its symbol is Tibit. It is the binary counterpart of the terabit, and the two now differ by 10 per cent, the point at which the distinction stops being pedantic and starts being financial.
That ten per cent is the reason the IEC prefixes exist. At the kibibit the discrepancy was 2.4 per cent and could be waved away; here it is a tenth of the quantity. In a contract for storage hardware, in a service agreement that guarantees capacity, or in a specification that a supplier must meet, a tenth is the difference between compliance and breach.
The unit's real home is flash memory, where dies are now made with capacities of one tebibit and above by stacking cell layers vertically. A modern flash die may hold a tebibit or two, and a package containing eight of them holds a teraoctet of raw capacity, from which spare blocks and management overhead are subtracted before anything reaches the user.
A tebibit is 137,438,953,472 octets, or 128 gibioctets. In practical terms it is the storage of a mid-range phone, or a couple of hours of uncompressed high-resolution video. The unit describes the raw material of storage devices rather than anything a person handles directly.
Filesystems also count in binary at this scale. A volume reported as 16 tebibytes by one tool and 17.6 terabytes by another is the same volume, and the difference is entirely in the base of the arithmetic. Anyone administering storage learns to check which convention a tool uses before comparing two numbers from different sources.
Correct notation is Tibit, with the capital T and lowercase i. It appears in flash memory datasheets, in filesystem documentation and in standards, and almost nowhere else. The presence of that lowercase i is the only reliable signal that a figure is binary, which is why careful technical writing uses it even when the difference seems small.
One tebibit equals 1,099,511,627,776 bits, 1,024 gibibits, 137,438,953,472 octets, or about 1.100 terabits.
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.