| Megaoctets (Mo) | Kibibits (Kibit) |
|---|---|
| 1 Megaoctet | 7812.5 Kibit |
| 2 Megaoctets | 15625 Kibit |
| 3 Megaoctets | 23437.5 Kibit |
| 4 Megaoctets | 31250 Kibit |
| 5 Megaoctets | 39062.5 Kibit |
| 10 Megaoctets | 78125 Kibit |
| 20 Megaoctets | 156250 Kibit |
| 25 Megaoctets | 195312.5 Kibit |
| 50 Megaoctets | 390625 Kibit |
| 100 Megaoctets | 781250 Kibit |
| Reference | Megaoctets (Mo) | Kibibits (Kibit) |
|---|---|---|
| A plain text message (160 characters) | 0.00016 Mo | 1.25 Kibit |
| A three-minute MP3 | 3 Mo | 23437.5 Kibit |
| A smartphone photo | 4 Mo | 31250 Kibit |
| A high-definition film | 4000 Mo | 31250000 Kibit |
| A dual-layer Blu-ray disc | 50000 Mo | 390625000 Kibit |
The megaoctet is a unit of digital information equal to one million octets, or eight million bits. Its symbol is Mo. It is the unit of the individual file: a photograph, a song, a document, an application download are all sized in megaoctets, which makes it the most frequently read data unit in daily life.
The typical figures are worth carrying in the head. A photograph from a phone is 2 to 5 megaoctets, a raw photograph from a system camera 25 to 50. A compressed song is 3 to 10. A minute of high-definition video is around 100. A long text document is under one. An operating system update is several thousand, which is why it is quoted in gigaoctets instead.
The megaoctet also carries the most notorious unit error in computing history. The 1.44 MB floppy disc holds neither 1.44 million octets nor 1.44 times 1,048,576. Its capacity is 1,440 kibioctets, which is 1,474,560 octets — the manufacturers multiplied a binary kilo by a decimal thousand and produced a figure that is correct in no system at all. It remains the standard illustration of why the IEC prefixes were needed.
Compact discs are cleaner: a standard disc holds about 700 megaoctets of data, or 74 to 80 minutes of audio, and that capacity was the practical limit for distributing software for a decade. Before them, distributing a program meant a box of floppies, and after them a DVD held about 4.7 gigaoctets, nearly seven times as much.
Memory sizes reached megaoctets in the early 1990s and stayed there for a decade. Four megaoctets was a comfortable amount in 1993 and inadequate by 1998, which tracks the arrival of graphical interfaces and the web. Today a single browser tab routinely holds more memory than an entire computer of that era.
The decimal-binary gap matters at this scale. A megaoctet is a million octets, but a mebioctet is 1,048,576, and a file reported as 100 MB by one program may appear as 95.4 MB in another. The difference is 4.9 per cent, small enough to overlook and large enough to cause arguments about whether a download completed correctly.
One megaoctet equals 1,000,000 octets, 1,000 kilooctets, 8 megabits, or about 0.9537 mebioctets.
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.