Mbps vs MB/s: The Division Behind Every Download Time
An internet plan says "100 Mbps." A download bar says "12.5 MB/s." Neither number is wrong, and neither is a typo — one counts bits, the other counts bytes, and the whole gap between them is one division that anyone can do on paper.
The method: bits, bytes, and one factor of eight
A byte is 8 bits, always. ISPs, phone carriers and network hardware advertise speed in bits per second (bit/s, Kbit/s, Mbit/s, Gbit/s) because it's the older telecom convention and the number looks eight times bigger. Operating systems, browsers and file managers show transfer speed in bytes per second (Byte/s, KB/s, MB/s) because that's what a file's size is measured in. Converting between the two families is the same two-step multiplication and division as any other unit conversion: multiply your value by the source unit's bits-per-second count, divide by the target unit's bits-per-second count. Because a byte is exactly 8 bits, converting from a bit unit to the matching byte unit — Mbit/s to MB/s, Kbit/s to KB/s — is always just dividing by 8.
Worked example: what "100 Mbps" actually downloads at
100 Mbit/s ÷ 8 = 12.5 MB/s. That's the number a download manager will show for a well-behaved transfer on that connection, and it's a quarter of what the plan's headline number suggests if you misread bits as bytes.
Now put a file size against it. A 4,000 MB game update (using decimal megabytes, the same 1,000-per-step units the connection speed is measured in) at 12.5 MB/s: 4,000 ÷ 12.5 = 320 seconds, or 5 minutes 20 seconds. If your file manager instead reports the update's size in binary MiB — a slightly bigger number of bytes per unit, covered in the companion post on data-size units — the true download time would be a little longer than this estimate, not shorter, since the file would be honestly larger than its decimal-MB label suggests.
More worked conversions, same division
- 25 Mbit/s (a common budget plan) ÷ 8 = 3.125 MB/s.
- 1 Gbit/s = 1,000 Mbit/s, so 1,000 ÷ 8 = 125 MB/s.
- 50 Mbit/s converted to KB/s instead of MB/s: 50 Mbit/s = 50,000,000 bit/s; 1 KB/s = 8,000 bit/s; 50,000,000 ÷ 8,000 = 6,250 KB/s — the same division by 8, just carried out one unit column over.
- 500 Kbit/s (a slow upload cap) ÷ 8 = 62.5 KB/s, or 62,500 Byte/s written the long way.
Why the plan number and the download bar never match exactly
Even after doing the bits-to-bytes division correctly, real downloads run under the theoretical rate: some of every second's bits are protocol overhead (packet headers, error correction, retransmits), the server or your Wi-Fi can be the actual bottleneck, and several other devices on the connection compete for the same bits. The division by 8 tells you the ceiling — the best a "100 Mbps" line can do — not a guarantee of what any single download will hit.
What the tool adds
The rule above — multiply by the source unit's bits-per-second value, divide by the target's — is everything the method needs, and dividing by 8 covers the most common case by hand. The free Data Rate Converter tool runs the same arithmetic instantly across bit/s, Kbit/s, Mbit/s, Gbit/s, Byte/s, KB/s and MB/s, so you never have to count zeros by hand — entirely on your device.