Mbps vs MB/s: how long will a download take?

Read both the letter case and the unit

One byte is eight bits. A decimal megabyte is 1,000,000 bytes, while a mebibyte (MiB) is 1,048,576 bytes. A decimal gigabyte (GB) is 1,000,000,000 bytes and a gibibyte (GiB) is 1,073,741,824 bytes. The same file does not change when an app chooses a different unit. See NIST’s binary-prefix reference.

Use the units the application actually reports. A value shown as MiB/s is not identical to MB/s, and “100 MB” describes an amount rather than a transfer rate. Avoid assuming every operating system or game launcher labels these consistently.

Use two formulas with consistent units

• Mbps ÷ 8 = decimal MB/s. For example, 100 Mbps corresponds to 12.5 MB/s and 1 Gbps corresponds to 125 MB/s.
• Seconds = decimal GB × 8,000 ÷ sustained Mbps. For example, 50 GB at 100 Mbps gives 4,000 seconds, or 1 hour 6 minutes 40 seconds.
• Seconds = decimal MB ÷ decimal MB/s. A 500 MB file at a sustained 10 MB/s takes 50 seconds in the simple model.

For a 50 GiB file, first convert its 53,687,091,200 bytes. At 100 Mbps, its ideal time is about 4,295 seconds, or 1 hour 11 minutes 35 seconds. Entering 50 in a field labelled GB represents a different quantity.

Compare ideal times with a clearly stated baseline

The rate here is sustained capacity available to the transfer. A package’s advertised headline is not a measurement of that rate. For uploads, use upload throughput; a high download speed cannot be substituted for it.

What this page’s calculator actually computes

The interactive calculator uses decimal units: 1 GB = 1,000 MB and 1 TB = 1,000 GB. Its “at full speed” result is the direct file-size/rate calculation. The existing result labelled “realistic” divides the ideal time by 0.9, equivalent to assuming 90% useful throughput—about 11.1% more time, not exactly 10%.

That is a fixed illustration, not a measurement or a universal protocol-overhead rate. A server cap, weak wireless connection, loss or competing transfer can make the difference much larger. Conversely, if you enter measured application throughput, that rate may already reflect overhead; do not interpret the added allowance as another unavoidable loss.

Find which part of the transfer is limiting it

Repeat measurements under documented conditions rather than assigning every shortfall to a fixed percentage of overhead. Ofcom recommends a wired test where possible to reduce Wi-Fi’s influence on the comparison.

Plan around a deadline or a real waiting cost

To send 10 GB within 20 minutes, the transfer needs an average 80,000 ÷ 1,200 = 66.7 Mbps of useful upload throughput. Add other traffic and uncertainty separately when considering a service tier. For daily use, the household planner addresses simultaneous activities rather than just a single file.