| Mebibits (Mibit) | Kibioctets (Kio) |
|---|---|
| 1 Mebibit | 128 Kio |
| 2 Mebibits | 256 Kio |
| 3 Mebibits | 384 Kio |
| 4 Mebibits | 512 Kio |
| 5 Mebibits | 640 Kio |
| 10 Mebibits | 1280 Kio |
| 20 Mebibits | 2560 Kio |
| 25 Mebibits | 3200 Kio |
| 50 Mebibits | 6400 Kio |
| 100 Mebibits | 12800 Kio |
| Reference | Mebibits (Mibit) | Kibioctets (Kio) |
|---|---|---|
| A plain text message (160 characters) | 0.0012207 Mibit | 0.15625 Kio |
| A three-minute MP3 | 22.8882 Mibit | 2929.69 Kio |
| A smartphone photo | 30.5176 Mibit | 3906.25 Kio |
| A high-definition film | 30517.6 Mibit | 3906250 Kio |
| A dual-layer Blu-ray disc | 381470 Mibit | 48828125 Kio |
The mebibit is a unit of digital information equal to 1,048,576 bits, which is 1,024 kibibits or two to the twentieth power. Its symbol is Mibit. It is the binary counterpart of the megabit, and the difference between the two has grown to 4.9 per cent — small enough to be ignored casually, large enough to matter in a specification.
Its natural home is semiconductor memory, where capacity is fixed by the address lines on the chip. A memory die with twenty address bits can reach exactly 1,048,576 locations, so densities land on powers of two rather than on round decimal numbers. A chip described as 512 megabits in a catalogue is very often 512 mebibits in reality, which is 537 megabits, and the datasheet is where the truth is written.
That habit is old and deliberate. Semiconductor manufacturers have always sized memory in binary because the wiring makes any other choice wasteful: an address bus is a fixed number of lines, and using only part of the range it can reach throws away silicon. Storage manufacturers had no such constraint, which is precisely why the two industries diverged.
For a sense of quantity, a mebibit is 131,072 octets, or about 128 kibioctets. That is roughly the contents of a long book as plain text, or a single low-resolution image. In network terms it is a hundredth of a second of a gigabit link.
The IEC prefixes were introduced in 1998 partly because at this level and above the approximation stops being safe. Buying a component described as one megabit and receiving one mebibit is a five per cent surprise; at the tebibit the same confusion is a ten per cent surprise, and in a contract for a data centre that is a real sum of money.
Correct usage is now common in standards documents, in hardware datasheets and in operating system internals, and rare in advertising and consumer software. The best rule when reading a figure is to ask which industry produced it: if it describes memory or a chip, assume binary; if it describes storage or a link, assume decimal.
One mebibit equals 1,048,576 bits, 1,024 kibibits, 131,072 octets, or about 1.049 megabits.
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.