Mbps to MB/s
One megabit per second is 0.125 megabyte per second. Enter any value and the answer updates as you type.
Converter
Megabit per second to Megabyte per second at a glance
21 rows| Megabit per second | Megabyte per second |
|---|---|
| 1 Mbps | 0.125 MB/s |
| 2 Mbps | 0.25 MB/s |
| 3 Mbps | 0.375 MB/s |
| 4 Mbps | 0.5 MB/s |
| 5 Mbps | 0.625 MB/s |
| 6 Mbps | 0.75 MB/s |
| 7 Mbps | 0.875 MB/s |
| 8 Mbps | 1 MB/s |
| 9 Mbps | 1.125 MB/s |
| 10 Mbps | 1.25 MB/s |
| 15 Mbps | 1.875 MB/s |
| 20 Mbps | 2.5 MB/s |
| 25 Mbps | 3.125 MB/s |
| 30 Mbps | 3.75 MB/s |
| 40 Mbps | 5 MB/s |
| 50 Mbps | 6.25 MB/s |
| 75 Mbps | 9.375 MB/s |
| 100 Mbps | 12.5 MB/s |
| 250 Mbps | 31.25 MB/s |
| 500 Mbps | 62.5 MB/s |
| 1,000 Mbps | 125 MB/s |
Quick pairs
tap to loadWhy people convert mbps to mb/s
Internet speed tests report download speed in megabits per second, while a file transfer progress bar or a download manager reports in megabytes per second, and the two are separated by a factor of 8, since there are 8 bits in a byte. A connection advertised at 100 Mbps tops out at about 12.5 MB/s, not 100 MB/s, the single most common source of confusion about why a download feels slower than the advertised plan speed.
Estimating download time for a large game or software update runs the same conversion in reverse: a 50 GB game update showing an estimated download time assumes a transfer rate in MB/s, so a user whose ISP plan is sold as "300 Mbps" needs to convert that to roughly 37.5 MB/s first before the download manager's time estimate makes any sense.
How the megabit per second to megabyte per second conversion works
One byte is defined as eight bits, so the conversion factor between a bit-based rate and a byte-based rate is always exactly 0.125, or its inverse, 8.
MB/s = Mbps × 0.125
A basic 25 Mbps broadband plan converts to 25 × 0.125 = 3.125 MB/s of real transfer capacity. A common 100 Mbps plan converts to 100 × 0.125 = 12.5 MB/s. A gigabit connection advertised at 1,000 Mbps converts to 1,000 × 0.125 = 125 MB/s.
Going the other way, multiply megabytes per second by 8: a download manager reporting 15 MB/s is pulling data at 15 × 8 = 120 Mbps.
Unlike many conversions, this one is exact with no rounding needed at all, since 8 bits per byte is a fixed definition, not a measured constant; any imprecision in a real download comes from network overhead and congestion, not from the conversion itself.
The mistake specific to this pair is reading "Mb" as "MB" or vice versa: a lowercase b means bits and an uppercase B means bytes, and mixing them up makes a connection look exactly 8 times faster or slower than it really is, a very easy typo to make when skimming a plan brochure or a speed test result.
Questions
How many megabytes per second are in a 200 Mbps connection?
200 Mbps equals 200 × 0.125 = 25 megabytes per second.
How do I convert megabytes per second back to megabits per second?
Multiply by 8. A transfer running at 10 MB/s, for example, equals 10 × 8 = 80 Mbps.
Why do ISPs advertise in Mbps instead of MB/s?
Bits produce a bigger, more marketable number for the same connection, and bits per second has long been the networking industry's standard unit for describing raw link speed, separate from how file sizes are measured in bytes.
Is there a quick way to estimate MB/s from an advertised Mbps plan?
Divide the Mbps figure by 8. A 500 Mbps plan gives roughly 500 / 8 = 62.5 MB/s of theoretical maximum transfer speed, though real-world throughput is always somewhat lower due to network overhead.
What's the most common mistake when converting between Mbps and MB/s?
Confusing the lowercase "b" (bits) with the uppercase "B" (bytes) when reading a plan or a progress bar, which makes the actual speed look exactly 8 times faster or slower than it really is.
More on precision and what leaves your device: see About and Privacy policy.