Make bits and bytes visible
For a transfer estimate, convert both rate and file size into bytes and seconds, divide, then state the estimate’s assumptions. Keep a measured performance result distinct from that theoretical limit.
The following inputs stay in megabits/second and the results use megabytes/second. They illustrate different magnitudes for this measurement. Retain the specific conditions described above when replacing an example with your own value.
This data transfer rate unit pair has a constant factor ratio. Changing the input changes the output by the same proportion. If a copied figure differs by an unexpected factor, review the full unit symbol before changing the source measurement. Keep the unit equivalent separate from observed transfer performance.
Calculate the no-overhead equivalent first, then use a measured sustained rate if the task needs a real-world transfer estimate.
Theoretical throughput comes before protocol overhead
A connection is advertised at 100 Mbit/s and a download display reports MB/s. The byte-versus-bit distinction explains a factor of eight before overhead enters the discussion. A theoretical rate equivalent is useful, but it is not a promise that a particular file will arrive at that speed.
A 1 GB decimal file contains 8,000,000,000 bits. At a constant 100 Mb/s, the ideal transfer time is eighty seconds. A 100 MB/s rate would give ten seconds for the same byte count. The uppercase B and lowercase b distinguish quantities whose factors differ by eight.
A network link rating is not necessarily application throughput. Headers, retransmissions, encryption, server limits and storage speed can reduce the useful data rate. A fixed percentage allowance may be useful for an explicitly hypothetical estimate, but it should not be presented as a measured property of every connection.
Short speed-test peaks can differ from sustained throughput during a large transfer. If you have a measured average for a comparable transfer, keep its conditions with the estimate. Several parallel transfers share resources and may not each receive the full link rate. Use an appropriate representative rate, identify decimal or binary file-size units, and report the theoretical calculation separately from any operational margin.
1 GB at 100 Mb/s takes 80 s in the constant-rate model.
100 Mbit/s in megabytes/second
100 Mbit/s = 12.5 MB/s
Output = input × source factor ÷ destination factor100 × 1,000,000 ÷ 8,000,000 = 12.5 MB/s. The two factors express the source and destination relative to the same internal reference unit. Their ratio is the multiplier.
Both unit factors refer to the same internal reference for data transfer rate. Multiplying by the source factor and dividing by the destination factor changes the numerical scale while retaining the quantity. The source definition still matters: Divide by eight to connect bits and bytes, then align the prefixes.
Reversing the unrounded 12.5 MB/s result returns 100 Mbit/s. Use this as a direction check. A consistent reverse calculation cannot resolve reading 100 mbit/s as 100 mb/s or improve the original observation.
Before using this data transfer rate result
- Confirm bits versus bytes and MB versus MiB in both rate and file size.
- Use measured sustained throughput rather than a link’s headline rate when estimating a real transfer.
- Retain whether a figure represents payload data or includes protocol overhead.
Keep the original data transfer rate value, its unit and the relevant conditions in the record. A copied answer of 12.5 MB/s is interpretable only when those details remain available. State which of the measurement checks above you verified before using the value in another calculation.
Link rate versus delivered payload
Data-transfer rate is a data quantity per unit time. This converter separates bits per second from bytes per second and supports explicit decimal and binary prefixes. It can translate a rated connection or measured throughput but cannot guarantee the speed of a file transfer.
Eight bits make one byte, so 100 Mbit/s equals 12.5 MB/s before protocol overhead. A MiB contains 1,048,576 bytes, while an MB contains 1,000,000. Transfer time is file size divided by rate only after both quantities use compatible data units. Network congestion, latency, server limits and overhead can change delivered throughput.
Transfer time equals file size divided by delivered payload rate after aligning the data units. Decimal MB and binary MiB differ as well. Protocol overhead, server limits and congestion can reduce delivered throughput; latency can affect some workloads differently from a large sustained transfer. Keep rated link speed, measured throughput and the assumed file size distinct.
Calculate the no-overhead equivalent first, then use a measured sustained rate if the task needs a real-world transfer estimate.
Questions about data transfer rate
How long should a 500 MB file take at 100 Mbit/s?
The theoretical time is 40 seconds with decimal units and no overhead. Actual transfer time can be longer because delivered payload throughput may be lower than the stated rate.
Are MB/s and MiB/s equivalent?
They share the byte-per-second dimension but use different prefix sizes. A megabyte is decimal; a mebibyte is binary. Select the exact label used by the application.
What this data transfer rate comparison can tell you
Useful capabilities
Calculate the no-overhead equivalent first, then use a measured sustained rate if the task needs a real-world transfer estimate.
The listed units express the same supplied data transfer rate quantity. The 100 Mbit/s → 12.5 MB/s example makes the selected convention visible before it is used in a longer calculation.
Important limits
Bits and bytes differ by a factor of eight. This is a unit conversion, not a prediction of download performance.
Divide by eight to connect bits and bytes, then align the prefixes. Keep the unit equivalent separate from observed transfer performance.
Reading 100 Mbit/s as 100 MB/s
Divide by eight to connect bits and bytes, then align the prefixes.
Treating the converted maximum as guaranteed throughput
Keep the unit equivalent separate from observed transfer performance.
The uppercase B and lowercase b change the factor by eight. A rated link speed is not necessarily sustained application throughput. Headers, congestion, retransmissions and storage limits can affect a real transfer. Use the measured payload rate from a comparable workload when it is available. Keep theoretical duration and any operational allowance separate instead of hiding overhead inside a unit factor.
As a controlled uncertainty example, suppose the original 100 Mbit/s record had a stated ±1% input interval. Its endpoints would be 99 Mbit/s and 101 Mbit/s. Converting those endpoints gives an output interval from 12.375 MB/s to 12.625 MB/s. The interval scales with the same fixed unit ratio as the central value. This chosen interval illustrates the arithmetic and is not an accuracy claim for your measurement.
Data Transfer Rate units, side by side
The values below all describe 100 Mbit/s. They provide a comparison of unit sizes for data transfer rate; they are not separate measurements. Read the complete symbol and convention before copying a number.
| Unit | Symbol | Equivalent |
|---|---|---|
| Bits/second | bit/s | 100,000,000 bit/s |
| Kilobits/second | kbit/s | 100,000 kbit/s |
| Megabits/second | Mbit/s | 100 Mbit/s |
| Gigabits/second | Gbit/s | 0.1 Gbit/s |
| Bytes/second | B/s | 12,500,000 B/s |
| Megabytes/second | MB/s | 12.5 MB/s |
| Mebibytes/second | MiB/s | 11.9209289551 MiB/s |
Keep the original megabits/second record alongside the converted megabytes/second display. The unit list uses up to twelve significant digits for arithmetic readability, while the measurement precision still comes from its source.