| Mebioctets (Mio) | Kibibits (Kibit) |
|---|---|
| 1 Mebioctet | 8192 Kibit |
| 2 Mebioctets | 16384 Kibit |
| 3 Mebioctets | 24576 Kibit |
| 4 Mebioctets | 32768 Kibit |
| 5 Mebioctets | 40960 Kibit |
| 10 Mebioctets | 81920 Kibit |
| 20 Mebioctets | 163840 Kibit |
| 25 Mebioctets | 204800 Kibit |
| 50 Mebioctets | 409600 Kibit |
| 100 Mebioctets | 819200 Kibit |
| Reference | Mebioctets (Mio) | Kibibits (Kibit) |
|---|---|---|
| A plain text message (160 characters) | 0.000152588 Mio | 1.25 Kibit |
| A three-minute MP3 | 2.86102 Mio | 23437.5 Kibit |
| A smartphone photo | 3.8147 Mio | 31250 Kibit |
| A high-definition film | 3814.7 Mio | 31250000 Kibit |
| A dual-layer Blu-ray disc | 47683.7 Mio | 390625000 Kibit |
The mebioctet is a unit of digital information equal to 1,048,576 octets, which is 1,024 kibioctets. Its symbol is Mio. It is the binary counterpart of the megaoctet, and the two differ by 4.9 per cent — the point at which a careful writer starts distinguishing them.
The unit's most visible home is the processor cache. The fast memory built into a processor to hold recently used data is sized in binary, and modern chips carry caches measured in mebioctets: a few hundred kibioctets at the second level and tens of mebioctets at the third. Those figures are exact powers of two because the cache is addressed by dividing an address into fixed bit fields.
Block sizes and buffers follow the same logic. Filesystems allocate in blocks, database engines read in pages, compression tools work in windows, and all of these are powers of two, most often a few mebioctets. A tool that offers a buffer of 16 megaoctets almost always means 16 mebioctets, because the underlying allocation is a shift rather than a multiplication.
The distinction has become visible to ordinary users through the discrepancy between what a download claims and what a file manager reports. A file described as 100 megaoctets on a website is often 100 mebioctets on disc, or the reverse, and the resulting 4.9 per cent difference is enough to make a progress bar look wrong without anything actually being wrong.
For scale, a mebioctet holds a million characters of unaccented text — roughly a long novel, or five hundred pages. It is also a single photograph from a modest camera, or eight seconds of high-definition video. The same unit therefore describes both a very large amount of text and a very small amount of video, which says a good deal about the relative cost of representing the two.
The IEC notation Mio is used in technical documentation, in the Linux kernel, in filesystem tools and in standards. It remains rare in consumer software, where MB is written for both quantities. When a figure matters, the safest habit is to compute in octets and convert once at the end.
One mebioctet equals 1,048,576 octets, 1,024 kibioctets, 8 mebibits, or about 1.049 megaoctets.
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.