| Tebioctets (Tio) | Kibioctets (Kio) |
|---|---|
| 1 Tebioctet | 1073741824 Kio |
| 2 Tebioctets | 2147483648 Kio |
| 3 Tebioctets | 3221225472 Kio |
| 4 Tebioctets | 4294967296 Kio |
| 5 Tebioctets | 5368709120 Kio |
| 10 Tebioctets | 10737418240 Kio |
| 20 Tebioctets | 21474836480 Kio |
| 25 Tebioctets | 26843545600 Kio |
| 50 Tebioctets | 53687091200 Kio |
| 100 Tebioctets | 107374182400 Kio |
| Reference | Tebioctets (Tio) | Kibioctets (Kio) |
|---|---|---|
| A plain text message (160 characters) | 1.45519 × 10-10 Tio | 0.15625 Kio |
| A three-minute MP3 | 0.00000272848 Tio | 2929.69 Kio |
| A smartphone photo | 0.00000363798 Tio | 3906.25 Kio |
| A high-definition film | 0.00363798 Tio | 3906250 Kio |
| A dual-layer Blu-ray disc | 0.0454747 Tio | 48828125 Kio |
The tebioctet is a unit of digital information equal to 1,099,511,627,776 octets, which is 1,024 gibioctets. Its symbol is Tio. It is the binary counterpart of the teraoctet, and at this level the two differ by 10 per cent — the gap that produces the most familiar complaint in consumer computing.
That complaint runs as follows. A drive is sold as one teraoctet, holds exactly one million million octets, and the operating system reports 931 gigaoctets. What it is actually reporting is 0.909 tebioctets, expressed with the wrong label. Nothing is missing from the drive; the number has simply been divided by 1,024 three times and then written with a decimal prefix.
Storage administration lives in this unit. Volume sizes, RAID array capacities, snapshot reserves and quota limits are all quoted in tebioctets by the tools that manage them, because the underlying allocation units are powers of two. A filesystem asked to create a 10-teraoctet volume and one asked to create a 10-tebioctet volume will produce visibly different results.
The difference matters commercially as well as technically. Cloud storage priced per teraoctet and cloud storage priced per tebioctet differ by a tenth in the quantity delivered for the same price, and a contract that does not say which is being used is genuinely ambiguous. Careful procurement documents specify the unit explicitly for exactly this reason.
A tebioctet holds around a quarter of a million photographs, two hundred hours of high-definition video, or the complete text of every book in a large public library many times over. In a household it is more storage than a lifetime of ordinary files will use; in a video production company it is a few days of work.
The correct symbol Tio appears in filesystem tools, in storage array documentation and in standards, and it is worth using even when the audience is unlikely to notice. A figure written with a binary prefix can be converted correctly by anyone who reads it later; one written ambiguously cannot be repaired.
One tebioctet equals 1,099,511,627,776 octets, 1,024 gibioctets, 8 tebibits, or about 1.100 teraoctets.
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.