Mbps to MB/s Converter

Mbps and MB/s are not the same thing

Two units describe internet speed, they look almost identical, and they differ by a factor of eight. Getting them confused is the single most common reason people think a working connection is broken.

• Mbps, megabits per second. The lowercase b means bits. ISPs advertise in this unit and speed tests report it.
• MB/s, megabytes per second. The uppercase B means bytes. Browsers, Steam, Dropbox and your operating system use this unit for transfer rates.
• 1 byte = 8 bits. That is the entire conversion.

So a plan sold as 100 Mbps is 12.5 MB/s of actual data movement. A 300 Mbps plan is 37.5 MB/s. A 1 Gbps plan is 125 MB/s. When a game launcher shows 37.5 MB/s on a 300 Mbps connection, the connection is running perfectly, nothing is being throttled and nothing is wrong.

The distinction matters because the two numbers are used for different jobs. Connection capacity is a bit rate, because networks move bits. File size is a byte count, because storage holds bytes. Whenever you divide a file size by a speed, you are implicitly converting between the two, and the factor of eight has to appear somewhere. Doing it up front, in the converter above, is the cleanest way to keep it straight.

The one-step conversion: divide by 8

MB/s = Mbps ÷ 8, and Mbps = MB/s × 8. There is no other step, no rounding rule and no exception. The unit definitions do all the work.

It helps to have a few anchors memorised:

• 8 Mbps = 1 MB/s
• 25 Mbps = 3.125 MB/s
• 100 Mbps = 12.5 MB/s
• 500 Mbps = 62.5 MB/s
• 1,000 Mbps (1 Gbps) = 125 MB/s

The SI prefixes are the same on both sides, mega means a million in megabits and in megabytes alike, which is why the ratio stays exactly 8 no matter how large the number gets. The NIST guide to SI prefixes is the reference for that, and it is also the place to confirm the bit-versus-byte symbol convention: lowercase b for bits, uppercase B for bytes.

One caution on megabytes. Storage manufacturers use the decimal megabyte of 1,000,000 bytes, while Windows and macOS report the binary one of 1,048,576 bytes. That is a 4.9% difference and it is why a 1 TB drive shows as 931 GB. For speed conversion it does not matter, the 8-bit factor is the same either way, but when you divide a file size by a speed, decide which megabyte you mean and stay consistent.

Worked examples: 100 Mbps, 500 Mbps and 1 Gbps

Three conversions, each taken all the way through to a real download time for a 1 GB file (1,024 MB).

• 100 Mbps: 100 ÷ 8 = 12.5 MB/s. Time: 1,024 ÷ 12.5 = 81.9 seconds, about 1 minute 22 seconds.
• 500 Mbps: 500 ÷ 8 = 62.5 MB/s. Time: 1,024 ÷ 62.5 = 16.4 seconds.
• 1 Gbps (1,000 Mbps): 1,000 ÷ 8 = 125 MB/s. Time: 1,024 ÷ 125 = 8.2 seconds.

Notice how the arithmetic behaves. Going from 100 Mbps to 1 Gbps is a tenfold increase in speed, and the download time falls from 82 seconds to 8 seconds, also tenfold. Linear scaling, because there is only one operation involved.

Now the practical twist. Those are theoretical figures, and a 1 GB download at a claimed 1 Gbps will usually take 10 to 15 seconds rather than 8. The server on the other end has to be willing to serve at that rate, and most are not configured to feed a single client at 125 MB/s. Past about 200 Mbps, the bottleneck usually stops being your connection and starts being the other end. That is worth remembering before paying for a faster plan to fix slow downloads from one particular site.

What internet speed do you need?

Converted into MB/s and matched to common activities. Per-stream figures are the low end of what the service recommends.

Netflix's own published guidance is 5 Mbps for HD and 15 Mbps for Ultra HD per stream, which is the figure to trust for streaming. The pattern in the table is that most households are limited by the number of simultaneous streams rather than by any single activity. Four people each watching 4K at 15 Mbps need 60 Mbps of sustained throughput, which is why a 100 Mbps plan feels fine and a 25 Mbps plan does not.

Gaming deserves a note because it inverts the usual logic. Online games use little bandwidth, 1 to 3 Mbps, but they are sensitive to latency, measured in milliseconds. A 1 Gbps connection with 90 ms of latency plays worse than a 50 Mbps connection with 20 ms. When shopping for a gaming connection, look at ping, not megabytes. The FCC broadband speed guide covers the household-level recommendations in more detail.

Why your download never hits the advertised number

Four things sit between the advertised Mbps and the MB/s you see.

• Protocol overhead. TCP and IP headers, acknowledgements and retransmissions consume 3 to 10% of the raw capacity. A perfect speed test on a 100 Mbps line shows about 94 to 97 Mbps.
• Wi-Fi. Wireless typically delivers 50 to 70% of what ethernet does at the same distance, and less through walls or on the crowded 2.4 GHz band.
• The server on the other end. Most services cap per-client throughput well below a gigabit, so a fast connection does not help past a certain point.
• Shared connections. Cable internet is shared with your neighbourhood, so peak evening hours can be slower than 3 am.

Test properly before you conclude anything. Use an ethernet cable, run the test twice at different times of day, and compare against the plan you are paying for. If ethernet gives you 95% of the advertised speed, the connection is fine and the Wi-Fi is the problem, a much cheaper thing to fix than an upgrade. If ethernet is also far short, that is a conversation with your ISP.

For day-to-day decisions, remember that the numbers only need to be good enough. A 100 Mbps connection delivering 12.5 MB/s in theory and 11 MB/s in practice is not meaningfully worse than one delivering 12.5, because almost nothing you do uses the full pipe for long.

Mbps to MB/s conversion chart

The values people search for most, with the download time for a 1 GB file at each speed. Times are theoretical; add about 5% for overhead.

Reading down the MB/s column, the numbers double in step with the Mbps column, which is the whole point: the conversion is a constant division, not a lookup. If you ever forget the factor, remember that 8 Mbps is exactly 1 MB/s and scale from there, halve the Mbps and you halve the MB/s.

A final unit warning that catches people out on storage rather than speed: internet plans and disk sizes both use “mega” and “giga”, but ISPs use decimal and operating systems use binary, so a 1 TB drive holds about 931 GB of what your file manager counts. Speed conversions are unaffected, because the 8-bit relationship is exact and universal.