The formulas
All three calculations are the same relationship, data = rate × time, solved for a different unknown. The only real difficulty is the units, so the calculator converts everything to bits and seconds first.
t = (S × 8) ÷ (R × (1 − o))
R = (S × 8) ÷ (t × (1 − o))
D = Rs × t ÷ (8 × (1 − o))
S is the size in bytes and the 8 turns bytes into bits. R is the connection speed in bits per second, t is the time in seconds and o is the protocol overhead as a fraction (10% is 0.1). Rs is a stream’s bit rate and D the data it uses, in bytes. Overhead shrinks the useful share of the line to 1 − o, so a transfer takes longer, a deadline needs a faster line, and a stream uses more data on the wire than its stated bit rate.
Bits, bytes and two kinds of prefix
A byte is 8 bits. Network speeds are quoted in bits per second, written Mbps or Mbit/s with a small b, while file sizes are quoted in bytes, with a capital B. A 50 Mbit/s connection therefore moves at most 50 ÷ 8 = 6.25 MB/s.
Prefixes come in two families. The SI prefixes kilo, mega, giga and tera are powers of 1,000: 1 GB is 1,000,000,000 bytes. The binary prefixes kibi, mebi, gibi and tebi, standardised in IEC 80000-13, are powers of 1,024: 1 GiB is 1,073,741,824 bytes, about 7.37% more. Network speeds always use the decimal family. Storage makers use decimal too, which is why a 1 TB drive appears in Windows as 931 GB: it holds 1,000,000,000,000 bytes, which is 931.32 GiB, and Windows shows GiB with the label GB.
Worked example: 4 GB at 50 Mbit/s
- Size in bits. 4 GB = 4,000,000,000 bytes × 8 = 32,000,000,000 bits.
- Speed in bits per second. 50 Mbit/s = 50,000,000 bit/s.
- Divide. 32,000,000,000 ÷ 50,000,000 = 640 seconds, which is 10 min 40 s.
- Allow for overhead. If you assume 10% overhead, only 45,000,000 bit/s carries your data, so the time is 640 ÷ 0.9 = 711.1 seconds, or 11 min 51.1 s.
If the 4 is really 4 GiB, as Windows would show it, the file is 34,359,738,368 bits and takes 687.2 seconds, or 11 min 27.2 s. If the speed is misread as 50 MB/s, the estimate drops to 80 seconds, eight times too optimistic.
Speed for a deadline. To send 10 GB in 30 minutes you need 80,000,000,000 bits ÷ 1,800 seconds = 44.44 Mbit/s of throughput, before overhead.
Streaming. A 5 Mbit/s video stream watched for 2 hours moves 5,000,000 × 7,200 ÷ 8 = 4,500,000,000 bytes: 4.5 GB, or 4.19 GiB, which is 2.25 GB an hour.
Why real transfers take longer
The plan speed is a ceiling. The speed in an internet plan is the most the access line can carry. Congestion in the evening, a busy Wi-Fi channel, the speed of the far server and other devices on the same connection all reduce what one transfer gets.
Upload and download differ. Many connections are asymmetric, with upload speeds a fraction of download speeds. Use the upload figure when sending files or backing up to the cloud.
Overhead is not a fixed number. Each packet carries headers, acknowledgements travel the other way, and lost packets are sent again. How much this costs depends on the protocols, packet size and link quality, so the calculator leaves it as your assumption.
Streaming services adapt. Most video services change the bit rate to suit the connection, so the data used per hour varies from moment to moment. Use the rate for your chosen quality setting as a planning figure.