| Megabits (Mbit) | Kibioctets (Kio) |
|---|---|
| 1 Megabit | 122.0703125 Kio |
| 2 Megabits | 244.140625 Kio |
| 3 Megabits | 366.2109375 Kio |
| 4 Megabits | 488.28125 Kio |
| 5 Megabits | 610.3515625 Kio |
| 10 Megabits | 1220.703125 Kio |
| 20 Megabits | 2441.40625 Kio |
| 25 Megabits | 3051.7578125 Kio |
| 50 Megabits | 6103.515625 Kio |
| 100 Megabits | 12207.03125 Kio |
| Reference | Megabits (Mbit) | Kibioctets (Kio) |
|---|---|---|
| A plain text message (160 characters) | 0.00128 Mbit | 0.15625 Kio |
| A three-minute MP3 | 24 Mbit | 2929.69 Kio |
| A smartphone photo | 32 Mbit | 3906.25 Kio |
| A high-definition film | 32000 Mbit | 3906250 Kio |
| A dual-layer Blu-ray disc | 400000 Mbit | 48828125 Kio |
The megabit is a unit of digital information equal to one million bits. Its symbol is Mbit. It is the unit in which the speed of an internet connection is almost always advertised, which makes it one of the few data units that ordinary consumers encounter by name every time they choose a service.
A megabit is one million bits exactly, not 1,048,576. That distinction has practical consequences. A megabit holds 125,000 octets, which is 125 kilooctets, so a connection running at 100 megabits per second transfers about 12.5 megaoctets per second at best. A file listed as 500 megaoctets therefore takes a minimum of forty seconds, not the four the advertised number seems to promise.
That factor of eight is the reason so many people believe their connection is slower than they were sold. Nothing dishonest is happening: the industry quotes throughput in bits per second because that is what the physical layer actually carries, while file managers quote size in octets because that is how storage is organised. Both conventions are correct in their own domain, and the arithmetic between them is a division by eight.
Real throughput is lower still. Protocol headers, error correction and retransmission all consume capacity, and the usable share of a link is typically 90 to 95 per cent of its nominal rate. Wireless links lose more, because the medium is shared and interference forces retries. A connection advertised at 100 megabits per second commonly delivers 90 or so in practice, and less over a busy wireless network.
The numbers that define the eras are worth remembering. Early broadband offered 1 to 8 megabits per second, cable and fibre pushed that to 50 and 100, and gigabit services are now common in cities. High-definition video streaming needs roughly 5 megabits per second, ultra-high-definition roughly 25, and a video call between two 8, so a household's real requirement is usually far below what it buys.
In memory the megabit describes chip capacity. A 512-megabit memory chip holds 64 megaoctets, and several such chips make a module. Manufacturers count in bits because that is what the silicon holds; buyers count in octets because that is what the operating system reports.
One megabit equals 1,000,000 bits, 1,000 kilobits, 125 kilooctets, or about 0.9537 mebibits.
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.