Mbps vs MB/s: Why Your Speed Test Doesn't Match Your Download Speed
Your speed test says 500. Your download says 60. Neither is wrong — they are measuring the same connection in two different units.
You run a speed test. It proudly reports 487 Mbps. Ten seconds later you start a download and your browser settles at 58 MB/s. One of those numbers is roughly eight times the other, and it is very tempting to conclude that someone is cheating you.
Nobody is. Both numbers are correct measurements of the same connection. They are simply expressed in two different units, and the gap between those units is exactly eight.
The short answer
A speed test reports megabits per second (Mbps). A download reports megabytes per second (MB/s). One byte is eight bits, so divide the speed-test number by 8 to get the download number.
MB/s = Mbps ÷ 8487 ÷ 8 = 60.9 MB/s. Your browser showing 58 MB/s is not a shortfall — it is your connection performing almost exactly as measured, minus a small amount of normal overhead. You can check any figure instantly with the Mbps to MB/s calculator.
Why the difference is exactly eight
A bit is the smallest unit of digital information: a single 1 or 0. A byte is a group of eight bits. That grouping is a decision made in the earliest days of computer design, and it has never changed.
Networks measure what they transmit — individual bits flying down a wire — so network speed is quoted in bits per second. Storage measures what it holds — files made of bytes — so file sizes and transfer progress are quoted in bytes.
The result is that every single connection in the world has two equally valid speed figures, and the marketing one is always the bigger of the two.
What that means for your plan
Here is what the common consumer tiers actually deliver, assuming the full advertised speed is available:
| Advertised | Real download speed | 1 GB file |
|---|---|---|
| 25 Mbps | 3.13 MB/s | 5 min 20 s |
| 100 Mbps | 12.5 MB/s | 1 min 20 s |
| 300 Mbps | 37.5 MB/s | 26 s |
| 500 Mbps | 62.5 MB/s | 16 s |
| 1000 Mbps | 125 MB/s | 8 s |
Notice how much less impressive the middle column looks. That is not an accident, and it is a large part of why the industry standardised on the first column — a subject we cover in why ISPs advertise in Mbps.
Where you will see each unit
Once you know the rule, the pattern is completely consistent. Anything describing the connection uses bits. Anything describing a file uses bytes.
- Megabits (Mbps) — your ISP's advertised plan, your bill, router admin pages, speed-test results, Xbox network statistics, Wi-Fi standard ratings.
- Megabytes (MB/s) — Windows and macOS file copy dialogs, browser downloads, Steam, the Epic Games Launcher, PlayStation downloads, torrent clients, cloud storage sync.
There is no setting anywhere in Steam or Windows to switch the display to Mbps. The convention is fixed, which is why the conversion has to happen in your head — or in a calculator.
Why even the converted number is slightly optimistic
Divide by eight and you get the theoretical maximum. Real transfers lose a further 10-20% to things nobody advertises:
- Protocol overhead. Every packet carries TCP/IP and TLS headers alongside your actual data. That metadata occupies real bandwidth.
- Server-side limits. You cannot download faster than the other end is willing to send. A busy or deliberately throttled server caps you regardless of your plan.
- Wi-Fi loss. Distance, walls, interference and older standards routinely cost 30-50% on a 2.4 GHz connection. See why Wi-Fi feels slower than your plan.
- Shared bandwidth. A console updating in another room is competing with you for the same pipe.
So for a 500 Mbps plan, 62.5 MB/s is the ceiling and anything from about 50 to 58 MB/s is a healthy real-world result.
Check your own connection in 60 seconds
- Run a speed test on a wired connection if you can, or standing next to the router if you cannot. Note the download figure in Mbps.
- Divide it by 8. That is your theoretical MB/s ceiling.
- Start a large download from a fast source — a game update or a Linux ISO works well — and watch the peak MB/s it reaches.
- Compare. Within about 20% of your ceiling means your connection is fine. Dramatically below means the bottleneck is Wi-Fi, the source server, or another device on your network.
The reverse conversion
The same rule runs backwards. If a download manager shows 12 MB/s and you want to know what line speed that implies, multiply by eight: 12 × 8 = 96 Mbps of your connection is in use.
Mbps = MB/s × 8This is genuinely useful when diagnosing a slow connection. If you are paying for 500 Mbps and your best sustained download is 6 MB/s, that is only 48 Mbps — a real problem worth calling your provider about, rather than a misunderstanding of units.
Convert your own speedType your plan's Mbps figure and see the MB/s your downloads should reach.Open the converterThe takeaway
Your speed test and your download manager have never disagreed. They report the same connection in units that differ by exactly eight, and dividing by 8 reconciles them every time.
If you also want to know how long a specific file will take rather than just how fast data arrives, that needs one more step — the file size. The download time calculator handles both at once, and how to calculate download time walks through the maths.