Megabits and megabytes
The most common confusion: internet speeds are sold in megabits per second (Mbps), while file sizes are shown in megabytes (MB) or gigabytes (GB). A byte is 8 bits, so:
100 Mbps = 12.5 MB per second, at best.
That means a 1 GB file on a 100 Mbps line takes at least 80 seconds, not 10.
The formula
Time = file size in bits / (speed in bits per second × (1 - overhead))
For a 50 GB backup on a 100 Mbps connection with 10% overhead:
50 × 8,000,000,000 bits / (100,000,000 × 0.9) = 4,444 seconds = 1 hour 14 minutes.
On a 1 Gbps line the same backup takes about 7 minutes 24 seconds.
Why real downloads are slower
- Protocol overhead. TCP/IP headers, encryption and acknowledgements use 5-10% of the bandwidth.
- Wi-Fi. Walls, distance and neighbours' networks can halve the real speed. A cable to the router often fixes it.
- The other end. A server can only send as fast as its own connection and disk allow, and many limit each download.
- Shared lines. Everyone in the house or office shares the same connection.
- Upload is slower on most home plans, unless you have symmetric fibre. Check your upload speed before planning an off-site backup.
Set the overhead to 0% for the theoretical best case, or 20-30% for a busy Wi-Fi network.
GB or GiB?
Storage makers count 1 GB as 1,000,000,000 bytes. Windows and some tools count in binary units, where 1 GiB is 1,073,741,824 bytes, about 7% more, and still label it "GB". That is why a "1 TB" drive shows as about 931 GB on a computer. Pick the unit that matches where you saw the size.
Moving a lot of data
For server migrations and backups, a few habits save hours:
- Compress first. Text, logs and databases often shrink to a fraction of their size with gzip or zstd.
- Use resumable tools like
rsyncorrclone, so a dropped connection does not mean starting over. - Copy only what changed. After the first full copy,
rsyncsends only the differences. - Run it overnight, when the line is free.