Kbps to Mbps Converter

Kbps to Mbps — quick reference

The formula, worked line by line

One division by a thousand, and then usually one more by eight to get somewhere useful. Both are given below, because a rate expressed in bits rarely answers the question that prompted the conversion.

Once both are in the same unit the comparison is straightforward, and the remaining judgement is about margin rather than arithmetic. How much margin depends on how much else shares the line, which is a question about your household rather than about units.

megabits per second = kilobits per second / 1,000
kilobytes per second = kilobits per second / 8
1 Mbps = 1,000 Kbps = 125 KB/s
320 Kbps / 1,000 = 0.32 Mbps
56 Kbps / 8 = 7 KB/s

Why bitrates are quoted in kilobits

Audio and video encoders express quality as a rate of information per second, and the bit is the natural unit for that because encoding decisions are made bit by bit rather than byte by byte. The kilobit stayed in use for audio because the numbers land in a readable range: 128, 192, 256 and 320 are easier to compare than four decimal fractions of a megabit.

The rate ladder, in full

That predictability is worth appreciating after the storage pages. Where a megabyte has two readings and a page of history behind the disagreement, a megabit has one reading everywhere, and the only thing that can go wrong is confusing it with a megabyte.

How to use the kbps to mbps converter

A megabit per second is a thousand kilobits per second, and the prefixes are decimal without exception. The conversion matters because the two units belong to different halves of the same question: media is encoded at a bitrate quoted in kilobits, and connections are sold at a speed quoted in megabits. Comparing them requires putting both on one scale.

That comparison is the practical use of this page. A stereo audio stream at 320 Kbps is 0.32 Mbps, which any modern connection carries without noticing. A high-definition video stream is a different proposition, and whether it fits depends on the encoder settings, the resolution and how much else is sharing the line at the time.

The byte figure is worth carrying alongside. A megabit per second is 125 kilobytes per second, because a byte is eight bits. That is the number to use when working out how long a download takes, since file sizes are in bytes and connection speeds are in bits, and mixing them is the single commonest error in this area.

Published encoder guidance is a useful anchor because it comes from the platform rather than from folklore. YouTube, for instance, publishes recommended live ingestion bitrates by resolution and frame rate: 12 Mbps for 1080p at 60 frames per second, 10 Mbps for 1080p30, 6 Mbps for 720p60 and 4 Mbps for lower settings, with stereo audio at 128 Kbps.

The 56 Kbps ceiling, and why nobody reached it

Dial-up is the reason a lot of people first learned this unit, and the story behind its famous number is more interesting than it looks. The ITU-T Recommendation V.90, published in 1998, specified up to 56,000 bits per second downstream and 33,600 upstream. V.92 followed in 2000 and enhanced the standard while retaining that downstream family.

Almost nobody ever saw 56,000. In the United States the limiting factor was a power restriction rather than a rate restriction: rules then in force under Part 68 capped the encoded analogue signal power, and compliant products consequently topped out around 53,333 bits per second. The FCC did not write a 53.3 Kbps limit into its rules; the rate was a consequence of the power limit.

Working out whether a stream will fit

The arithmetic is simple and the assumptions are where it goes wrong. Convert the bitrate to Mbps, compare it against the connection speed, and then discount the connection for everything else using it. A household with several devices does not have its full line rate available to any one of them at any given moment.

The second point is the one most often confused. A platform's recommended encoder bitrate describes what a broadcaster should send upstream, not what a viewer must be able to receive. Playback is adaptive: the player picks a quality level that fits the connection it finds, which is why a stream degrades rather than stopping when bandwidth is tight.

Every Kbps value, worked out

65 common Kbps figures each get their own page, with the answer at full precision, the arithmetic, what rounding costs, and the nearest real-world reference point on the scale.

Questions people ask