Mbps measures megabits per second. MB/s measures megabytes per second. Since one byte contains eight bits, divide Mbps by eight to get the matching decimal MB/s rate. A 100 Mbps connection therefore corresponds to 12.5 MB/s as a unit conversion, not a guaranteed file-transfer result.
In Mbps vs MB/s labels, capitalization matters: lowercase b means bits, while uppercase B means bytes. That single letter explains why an internet plan advertised at 100 Mbps may produce a file-transfer display near 12.5 MB/s rather than 100 MB/s.
Mbps vs MB/s: the direct answer
Mbps vs MB/s is a comparison between two data-rate units. The first counts millions of bits each second. The second counts millions of bytes each second. NIST defines one byte as eight bits, one megabyte as 1,000,000 bytes, and one mebibyte as 1,048,576 bytes.
For decimal units, the conversion is exact:
- Mbps ÷ 8 = MB/s
- MB/s × 8 = Mbps
These formulas compare units. They do not predict how much of a connection’s nominal capacity an application will sustain. The FCC distinguishes typical upload and download speeds from advertised speeds, and it notes that connected devices can affect the rate available to one device.
| Network rate | Decimal byte rate | Binary byte rate |
|---|---|---|
| 10 Mbps | 1.25 MB/s | about 1.19 MiB/s |
| 25 Mbps | 3.125 MB/s | about 2.98 MiB/s |
| 50 Mbps | 6.25 MB/s | about 5.96 MiB/s |
| 100 Mbps | 12.5 MB/s | about 11.92 MiB/s |
| 500 Mbps | 62.5 MB/s | about 59.60 MiB/s |
| 1 Gbps | 125 MB/s | about 119.21 MiB/s |
This Mbps vs MB/s table describes equivalent units before protocol work, competing traffic, device limits, and other conditions are considered. It is a reference for interpreting labels, not a performance promise.
What Mbps means
Mbps is short for megabits per second. In standardized decimal notation, one megabit is 1,000,000 bits. Internet providers and network speed tests commonly use Mbps because communications systems have traditionally described rates in bits per second. This is the network side of the Mbps vs MB/s comparison.
The FCC’s consumer broadband glossary says broadband speed is typically measured in Mbps. It also requires broadband labels to list typical download and upload speeds separately. That distinction matters for file work. Download speed applies when data travels to your device. Upload speed applies when your device sends a file to a service.
A plan can have different upstream and downstream rates. If a label lists 500 Mbps download and 50 Mbps upload, use 50 Mbps to estimate an upload. The larger download number does not speed up the outgoing file.
Gbps follows the same Mbps vs MB/s pattern at a larger scale. One decimal gigabit per second is 1,000 Mbps. Dividing by eight gives 125 MB/s. It does not equal one gigabyte per second, which would require 8 Gbps before considering real transfer conditions.
What MB/s means
MB/s is short for megabytes per second. A browser, file manager, download client, or storage application may show a byte rate because file sizes are commonly expressed in bytes. If the application reports 25 MB/s, the equivalent bit rate is 200 Mbps. This is the file-display side of Mbps vs MB/s.
Some interfaces write MBps instead of MB/s. Both are intended to mean megabytes per second, but MB/s is easier to distinguish from Mbps at a glance. Do not rely on pronunciation alone. Read the capitalization and the slash.
The Mbps vs MB/s difference is easiest to see with 100 Mbps. Dividing by eight gives 12.5 MB/s. Seeing a number around 12.5 in a file-transfer window is therefore compatible with a number around 100 in a network-rate display. The two screens may be reporting the same flow with different units.
That does not mean every 100 Mbps connection will sustain 12.5 MB/s. It means 12.5 MB/s is the decimal byte-rate equivalent of 100 Mbps. The measured application result can be lower, and occasionally a short display sample can fluctuate above a long-term average.
How to convert Mbps to MB/s
The Mbps vs MB/s calculation needs only one step when both units use decimal prefixes: divide by eight. Keep enough decimal places for the decision you are making, then round the displayed result rather than the inputs.
Example 1: convert 25 Mbps
For this Mbps vs MB/s example, 25 ÷ 8 = 3.125. The matching decimal rate is 3.125 MB/s. If a transfer application displays two decimal places, it may show 3.13 MB/s.
Example 2: convert 300 Mbps
For a second Mbps vs MB/s example, 300 ÷ 8 = 37.5. The matching decimal rate is 37.5 MB/s. This remains a unit-equivalent rate, not a guarantee that a remote service, Wi-Fi link, or device can sustain it.
Example 3: convert MB/s back to Mbps
To reverse the Mbps vs MB/s calculation, suppose a completed transfer averaged 40 MB/s. Multiply by eight: 40 × 8 = 320 Mbps. This lets you compare an application’s observed byte rate with a network result written in bits per second.
Once the units match, use Filekub’s file transfer time calculator to combine a file size with an upload or download rate. The calculator keeps bits, bytes, decimal prefixes, and binary prefixes separate.
MB/s versus MiB/s is a second conversion
The Mbps vs MB/s distinction is only the first unit issue. Some software reports MiB/s, or mebibytes per second, even if the interface loosely labels the value as MB/s. NIST lists one MB as 1,000,000 bytes and one MiB as 1,048,576 bytes.
Mbps vs MB/s uses decimal units, but MiB/s adds a binary conversion. Because one MiB contains more bytes than one MB, the same underlying flow produces a smaller numeric value in MiB/s. A decimal rate of 12.5 MB/s is 12,500,000 bytes per second. Divide that by 1,048,576 to get about 11.92 MiB/s.
| Quantity | Exact byte count |
|---|---|
| 1 MB | 1,000,000 bytes |
| 1 MiB | 1,048,576 bytes |
| 1 GB | 1,000,000,000 bytes |
| 1 GiB | 1,073,741,824 bytes |
This difference can appear in both file sizes and transfer rates. A 500 MB file is about 476.84 MiB. A 500 MiB file is 524.288 MB. The article on why downloaded file sizes differ covers other reasons that two displays may disagree.
Use the unit named by the application. Do not silently treat MB and MiB as interchangeable, especially when you are checking a deadline or comparing an exact byte count.
Why the actual file rate may be lower
Bandwidth and throughput are related but different. Cloudflare describes bandwidth as the maximum amount of data that can pass through a network at a given time, while throughput is the amount that actually passes over a period. Latency and other conditions can keep throughput below bandwidth.
A file transfer also shares the path with protocol traffic. Connections exchange headers and acknowledgements, establish encrypted sessions, and may retransmit lost data. Wi-Fi interference, another household upload, a slow local drive, CPU load, the route across networks, or the receiving service can become the limiting part.
Microsoft’s large-transfer guidance says upload and download time can depend on internet speed, server proximity, ISP conditions, and computer speed. It recommends a wired connection, avoiding competing activity, and keeping the computer awake during a long transfer.
There is no honest universal percentage for this gap. A fixed claim such as “every transfer runs at 80%” would hide the real uncertainty. Measure the actual route when timing matters. A recent sustained result is more useful than treating the plan’s headline rate as reserved capacity.
Even after resolving Mbps vs MB/s units, short sampling windows can mislead. An application may calculate its displayed MB/s from a brief interval, while a speed test reports a different interval or server. Compare longer averages and make sure both readings refer to the same direction.
Choose the correct speed for an estimate
Start an Mbps vs MB/s estimate by deciding whether the file is moving away from or toward your device. For an upload, use measured upload throughput. For a download, use measured download throughput. Then confirm whether the number is written in Mbps, MB/s, or MiB/s before entering it into a calculator.
- Check direction. Use upstream speed for uploads and downstream speed for downloads.
- Read the unit. Lowercase b is bits; uppercase B is bytes.
- Convert once. Divide decimal Mbps by eight to obtain MB/s, or multiply MB/s by eight to obtain Mbps.
- Keep binary units explicit. Convert separately if the application shows MiB/s or GiB.
- Use measured throughput when available. Do not assume the advertised maximum will hold for the whole transfer.
- Add deadline margin. Leave time for setup, fluctuating rates, and confirmation after the bytes finish moving.
For a worked duration table, see how long it takes to upload 10GB. The broader guide to sending large files online covers the delivery workflow when email attachments are too small. The cloud storage versus file transfer guide helps when the question is which type of service fits the job.
Frequently asked questions
Is 100 Mbps equal to 100 MB/s?
No. 100 Mbps equals 12.5 MB/s as a decimal unit conversion. Reaching 100 MB/s would correspond to 800 Mbps before real transfer conditions are considered.
Is MB/s faster than Mbps?
One MB/s represents eight times as many bits per second as one Mbps. The unit is larger, but the number and unit must be read together. A rate of 10 MB/s equals 80 Mbps.
Why does an application show MiB/s?
MiB/s uses binary mebibytes. One MiB is 1,048,576 bytes, while one decimal MB is 1,000,000 bytes. The same byte flow therefore has a slightly smaller numeric value in MiB/s.
Should I multiply or divide by eight?
Divide Mbps by eight to get MB/s. Multiply MB/s by eight to get Mbps. This rule assumes decimal mega on both sides.
Does 1 Gbps equal 125 MB/s?
Yes as a decimal unit conversion: 1 Gbps is 1,000 Mbps, and 1,000 ÷ 8 = 125 MB/s. Actual file throughput may be lower.
Why do a speed test and file transfer show different numbers?
First check the Mbps vs MB/s labels: the speed test may use Mbps while the transfer uses MB/s or MiB/s. If the units already match, differences can come from test duration, Wi-Fi, competing traffic, protocol work, device performance, network route, or the receiving service.
