Conversion from 50 Megabits per second to Kibibits per second

=

Invert

Formula to convert Megabits per second (Mbit/s) to Kibibits per second (Kibit/s)

More information

Megabits per second to Kibibits per second conversion table

Megabits per second (Mbit/s)Kibibits per second (Kibit/s)
1 Megabit per second976.5625 Kibit/s
2 Megabits per second1953.125 Kibit/s
3 Megabits per second2929.6875 Kibit/s
4 Megabits per second3906.25 Kibit/s
5 Megabits per second4882.8125 Kibit/s
10 Megabits per second9765.625 Kibit/s
20 Megabits per second19531.25 Kibit/s
25 Megabits per second24414.0625 Kibit/s
50 Megabits per second48828.125 Kibit/s
100 Megabits per second97656.25 Kibit/s

Data-transfer rate reference points

ReferenceMegabits per second (Mbit/s)Kibibits per second (Kibit/s)
A dial-up modem0.056 Mbit/s54.6875 Kibit/s
Typical home broadband100 Mbit/s97656.2 Kibit/s
Gigabit Ethernet1000 Mbit/s976562 Kibit/s
Streaming a 4K film25 Mbit/s24414.1 Kibit/s

Try our other unit converters

LengthMassTemperatureEnergyVolumeSpeedTimeDataPressureFrequencyData-transfer rateVolumetric flow rateAngleArea

Information about the Megabit per second (Mbit/s)

The megabit per second is a unit of data transfer rate equal to one million bits per second. Its symbol is Mbit/s, often written Mbps. It is the unit in which internet connections are sold, which makes it the data unit most people encounter by name.

Because it is a decimal million and not 1,048,576, the conversion to octets is exact and easy: one megabit per second is 125 kilooctets per second, so a hundred-megabit connection delivers about 12.5 megaoctets per second at best. Anyone who watches a file transfer and does the division has understood the entire relationship between how connections are advertised and how transfers are reported.

What a household actually needs is far below what it usually buys. Standard-definition video streaming uses about 3 megabits per second, high definition about 5, and ultra-high definition about 25. A video call is around 3 to 8. A large family watching four separate high-definition streams while somebody downloads a game is using perhaps 60 megabits per second, which a hundred-megabit connection handles comfortably.

The reason to buy more capacity than that is not peak speed but behaviour under load. A link that is near its limit develops queues, and queues add delay, which shows up as stutter in video calls and lag in games. A connection with generous headroom keeps its latency low, and that is a more noticeable improvement than a higher number on a speed test.

Wired local networks pass through this range on the way up. The original Ethernet ran at 10 megabits per second, its successor at 100, and both were the standard office connection for a decade each before gigabit replaced them. Wireless standards followed the same path with a lag, and both are now measured in hundreds of megabits or in gigabits.

Real throughput is always below the nominal rate. Protocol overhead takes 5 to 10 per cent on a wired link; a shared wireless channel loses much more, because the medium is divided between all the devices using it and interference forces retransmission. A connection advertised at 100 megabits per second measured at 90 over cable and 50 over a busy wireless network is behaving normally.

One megabit per second equals 1,000,000 bits per second, 125 kilooctets per second, or about 0.9537 mebibits per second.


Information about the Kibibit per second (Kibit/s)

The kibibit per second is a unit of data transfer rate equal to 1,024 bits per second. Its symbol is Kibit/s. It is the binary counterpart of the kilobit per second, and it is the least used member of an already unusual family, because transfer rates are one of the few places in computing where the decimal convention has always been unambiguous.

Networking has counted in true thousands from the beginning. A modem rated at 56 kilobits per second meant fifty-six thousand, not fifty-seven thousand three hundred and forty-four. The reason is that a transmission rate is set by a clock, and clocks are specified in decimal frequencies: a link running at ten million symbols per second carries a decimal number of bits, not a power of two.

The binary prefixes exist for quantities, not for rates, because quantities of storage are organised in powers of two while time is not. There is no natural reason for a rate to be a power of two, and consequently no reason for a rate unit to need a binary prefix. Where one appears, it is almost always because a program divided a binary file size by a duration.

That is exactly where the kibibit per second does turn up. A tool that measures a transfer by counting kibioctets and dividing by seconds produces a rate in kibioctets per second, and multiplying by eight gives kibibits per second. The unit is a consequence of the arithmetic rather than a description of the channel.

For scale, a kibibit per second is 128 octets per second, and the difference from a kilobit per second is 2.4 per cent — smaller than the measurement error of almost any real throughput test. At this level the distinction is technically correct and practically invisible, which is a fair description of the whole binary prefix system at its lower end.

The unit is properly defined and a converter must handle it, because the IEC series applies to every unit without exception. Whether anyone writes it is a separate question from whether it means something definite, and it does.

One kibibit per second equals 1,024 bits per second, 128 octets per second, or 1.024 kilobits per second.