Why Does Steam Show Download Speed in MB/s Instead of Mbps?

You pay for a 500 Mbps connection. Steam says it is downloading at 58 MB/s. Somewhere in the back of your mind a voice says you are being short-changed by roughly 90%.

You are not. Steam is showing you exactly what you are paying for, in a different unit.

The short answer

Steam reports download speed in megabytes per second (MB/s) because that is the operating system convention for file transfers. There is no setting to change it to Mbps. Divide your plan's Mbps figure by 8 to get the MB/s Steam should be reaching.

So on a 500 Mbps plan, a Steam download peaking between roughly 50 and 60 MB/s is completely normal and healthy.

Why Steam picked bytes

Steam is not really measuring your internet connection. It is measuring the progress of a file — how much of a 50 GB game has arrived so far.

Files are measured in bytes. Showing progress in megabytes per second means the speed figure and the size figure use the same unit, so the arithmetic works in your head: a 50,000 MB game at 50 MB/s takes about 1,000 seconds. If Steam displayed Mbps you would have to convert every time you wanted to estimate the wait.

Windows does the same thing in its file copy dialog. So does macOS, so does Chrome, so does every torrent client ever written. Steam is following an operating system convention that predates it by decades, not making an idiosyncratic choice.

What speed should Steam actually reach?

Take your advertised plan speed, divide by eight, then take off 10-20% for real-world overhead. That range is what a healthy Steam download looks like:

If your figure sits inside that range, nothing is wrong. If it sits far below, the cause is almost always one of the four things below rather than your ISP.

When Steam genuinely is slow

1. The content server region is wrong or busy

Steam assigns you a download region, and a congested or distant one will throttle you badly. Open Steam → Settings → Downloads and check the region. Try a nearby alternative and restart the download; the difference can be several times over.

2. Your disk cannot keep up

Steam does not just download — it decompresses and writes the data as it goes. On a mechanical hard drive the disk often becomes the bottleneck well before the network does, which is why the speed graph plateaus at a suspiciously round number and the drive light stays solid.

3. Wi-Fi is eating the difference

A 2.4 GHz connection two rooms away from the router can lose half your throughput before Steam ever sees it. Test on Ethernet once, even temporarily, to establish what your connection is really capable of.

4. Something else is using the pipe

A console updating, a 4K stream, or a cloud backup running in the background all take a share. Steam's throttling settings can also cap it deliberately — check that no bandwidth limit is set and that 'Allow downloads during gameplay' has not left it deprioritised.

The mental shortcut

Rather than converting every time, remember one anchor point and scale from it:

• 100 Mbps = 12.5 MB/s. Everything else is a multiple of that.
• 200 Mbps is double it: 25 MB/s.
• 500 Mbps is five times it: 62.5 MB/s.
• 1 Gbps is ten times it: 125 MB/s.

That single anchor covers almost every consumer plan you will encounter. For anything unusual, the Mbps to MB/s calculator does it instantly.

One catch worth knowing

Steam reports game sizes in binary gigabytes — 1 GB there means 1,024 MB, not 1,000 MB — while your connection speed is measured in decimal units. A game listed as 50 GB is really about 53.7 decimal GB of data.

That mismatch makes every Steam download take roughly 7% longer than a naive calculation predicts, before any other overhead is counted.

It is a small thing, but it explains the last few minutes of a download that seemed like it should already have finished. How long does it really take to download a game works through a full example with the binary sizes included.