Mbps vs MB/s: How to Convert Internet Speed

Mbps vs MB/s is a units conversion, not a performance contest. Mbps means megabits per second; MB/s means megabytes per second. One byte contains eight bits, so divide Mbps by 8 to estimate the same rate in MB/s: a 100 Mbps plan is 12.5 MB/s before overhead. If a download bar shows a smaller number, check the units first, then the network path.

What the units mean

Mbps is megabits per second. Internet providers, routers, and most speed tests use it to describe a connection's data rate. MB/s is megabytes per second. Browsers, game launchers, file-transfer tools, and storage utilities often use it when showing how quickly file data is moving. MBps is another way of writing MB/s; the capital B is the part that matters.

A lowercase b means bit and an uppercase B means byte. The Microsoft bit-and-byte style guide follows that distinction, while the IETF's byte definition specifies a byte as exactly eight bits. Neither unit is intrinsically faster: they describe the same rate with different-sized units.

Mbps vs MB/s: the conversion

Use one rule for the forward conversion:

MB/s = Mbps ÷ 8

To convert in the other direction:

Mbps = MB/s × 8

For a worked example, take a 300 Mbps connection. 300 ÷ 8 = 37.5, so its ideal equivalent is 37.5 MB/s. A 1,000 MB file would therefore take 1,000 ÷ 37.5 = 26.7 seconds at a perfectly sustained rate. That is a unit calculation, not a promise: the actual transfer can take longer.

The prefixes can create a second, smaller mismatch. NIST lists MB as 1,000,000 bytes and MiB as 1,048,576 bytes; IEC 80000-13:2025 covers information-science units and binary prefixes. If a program says MiB/s, do not treat it as exactly the same display as MB/s.

Common speed conversions

These values use decimal Mbps and MB/s and show the ideal byte rate before protocol, wireless, device, or server limits:

Use the same conversion for upload. An 80 Mbps upload service has an ideal equivalent of 10 MB/s, even though an upload tool may show a different number in practice.

Why a download is usually below the converted ceiling

Dividing by eight only makes the units comparable. It does not turn an advertised or tested line rate into a guaranteed application transfer. The FCC distinguishes advertised bandwidth from theoretical capacity, and a file download also depends on the rest of the path.

• Protocol overhead: headers, acknowledgements, encryption, and retransmissions use some of the transfer capacity.
• Wi-Fi and home traffic: distance, interference, router limits, and another device's stream or backup can reduce the rate reaching your device.
• Source limits: the website, game server, content-delivery route, or storage device may not send one file as quickly as your connection can receive it.
• Test design: a speed test measures a path to its own endpoint. Cloudflare's measurement documentation treats download and upload as only part of connection quality, alongside latency, packet loss, loaded latency, and jitter. M-Lab's ndt7 documentation also distinguishes application-level goodput from lower-level throughput.

So 100 Mbps on a test and 10 or 11 MB/s in a browser can be consistent. Convert the browser number back with MB/s × 8 before deciding that the connection is slow.

Run a fair Loqmi comparison

When the numbers still look wrong, compare like with like. Use the same device, the same connection, and a quiet test window before changing your plan.

1. Pause other downloads, cloud backups, video streams, and updates. Write down the unit beside every number you collect.
2. Open Loqmi's browser speed test from the location where the problem occurs. Record download and upload in Mbps, plus any latency or packet-loss results shown.
3. Convert the download result. For example, 240 Mbps gives an ideal ceiling of 30 MB/s. A fast source running near that figure is behaving as expected; a much lower result needs diagnosis.
4. Repeat on Ethernet or close to the router, then try a second large download source. Repeat at the busy time if the problem is intermittent.

Troubleshoot the mismatch

Choose the right fix

More Mbps helps when active household traffic is competing for capacity. It cannot repair a slow source, a weak Wi-Fi link, high latency, or packet loss. For planning simultaneous activities, use Loqmi's guide to a good internet speed; for a Wi-Fi-only gap, fix the local network first.

If repeated wired tests are well below the advertised service, save the date, device, connection type, server, and results before contacting the ISP. If wired results are healthy and only one room or device is slow, an upgrade may add no useful capacity there.