Internet plans are advertised in Mbps (megabits per second), but file sizes and transfer progress bars are almost always shown in MB or GB (megabytes/gigabytes). This converter bridges the two directly, so you can translate a plan’s advertised speed into the byte-based unit that actually predicts download and transfer times.
What the Result Means
Enter a speed in Mbps and the calculator converts it to MB/s (megabytes per second) — the unit that lines up with file sizes. The result represents the theoretical maximum transfer rate your connection can sustain expressed in the unit you actually need to estimate how long a download or file copy will take.
This conversion exists because bits and bytes are different units, and internet service providers have long advertised speed in bits (a convention that also happens to make the number look larger and more impressive than the equivalent byte figure would).
How This Calculator Works
The conversion is a single division, since there are 8 bits in a byte:
- MB/s = Mbps ÷ 8
Worked example: converting a common “500 Mbps” internet plan:
- 500 Mbps ÷ 8 = 62.5 MB/s (theoretical maximum)
So a 500 Mbps plan can theoretically move about 62.5 megabytes of data every second — useful for quickly sanity-checking how long a given file should take to download at that speed, before accounting for real-world overhead.
Here’s the same conversion applied to a few other common plan speeds, as a quick reference:
| Advertised Speed (Mbps) | Theoretical MB/s |
|---|---|
| 25 Mbps | 3.1 MB/s |
| 100 Mbps | 12.5 MB/s |
| 300 Mbps | 37.5 MB/s |
| 1,000 Mbps (1 Gbps) | 125 MB/s |
Notice how the MB/s figure is always well under a sixth of the Mbps figure. That gap is exactly why a “1 Gbps” plan sounds dramatically faster than it feels when you’re staring at a file copy progress bar reporting in MB/s — both numbers describe the same connection, just in different units.
Important Limitations
- This is a theoretical maximum, not a guaranteed rate. Actual throughput is affected by network overhead, server-side limits, Wi-Fi conditions, and general congestion, so real-world speeds usually land somewhat below the converted figure.
- Don’t confuse this with storage-unit conversions. This conversion (÷8) is specifically for bits-to-bytes at the same decimal scale — it’s unrelated to the separate decimal-vs-binary distinction used for drive capacity.
- ISPs generally use decimal Mbps. The conversion here assumes standard decimal megabits and megabytes, matching how internet speeds and file sizes are conventionally reported.
- Wired vs. wireless matters after the conversion. Even with the correct MB/s figure, your actual achievable speed on Wi-Fi may be lower than on a wired Ethernet connection.
Frequently Asked Questions
Why do ISPs advertise speed in Mbps instead of MB/s?
It’s the long-standing industry convention for networking speeds, and it also produces a larger, more marketable number than the equivalent MB/s figure would — the two units are simply different scales of the same underlying rate.
How many MB/s is a 1 Gbps connection?
1 Gbps = 1,000 Mbps, so dividing by 8 gives 125 MB/s as the theoretical maximum — actual achievable speeds are usually lower due to overhead and hardware limits.
Is this the same conversion used for storage units like GB and GiB?
No. This is a bits-to-bytes conversion (divide by 8) at the same decimal scale. The GB vs GiB distinction is a separate decimal-vs-binary difference used for storage capacity, and the two shouldn’t be combined in one step.
Why does my download manager show a speed lower than my converted MB/s figure?
The converted figure is a theoretical ceiling based on your advertised plan speed. Real download speed is typically lower due to server limits, network conditions, and other traffic on your connection.
Should I use this conversion to check my speed test results?
It can help as a sanity check, but most speed test tools already report results in Mbps to match ISP advertising — you’d typically use this converter to translate that Mbps result into MB/s for comparing against a file size instead.