Article — Data Transfer Time
Data transfer time calculator
A data transfer calculator estimates how long a file or backup will take, given size and bandwidth. The formula is time (seconds) = size in bits / (bandwidth in bps x (1 - overhead)). A 100 GB backup at 100 Mbps with 15% overhead takes about 2 hours 37 minutes.
This calculator emphasizes uploads, backups, and server-to-server transfers, where asymmetric speeds and protocol overhead dominate. For pure consumer downloads, the related download-time calculator applies the same math with different defaults.
What is a data transfer calculation?
A data transfer calculation answers the question "how long will this move take" by dividing data volume by data rate. The hard part is unit consistency. Files are usually measured in bytes (a 1 GB file is 8,000,000,000 bits), while network bandwidth is usually measured in bits per second (a 100 Mbps line is 100,000,000 bps). Always normalize both sides to bits before dividing.
The IEEE and Cisco network references agree on one convention for the time math: bits and bps. The 8x factor between bytes and bits is the single biggest source of estimation errors in informal calculations.
The first ARPANET data transfer in 1969 ran at 50 kilobits per second. A 1 GB file would have taken 5.7 years to transmit at that rate. Modern 10 Gbps backbone links move the same volume in under a second.
The data transfer formula
The data transfer formula is simple: time (s) = bits to move divided by bits per second of effective bandwidth. With an overhead factor for real-world TCP, WiFi, and routing losses:
time = bits / (bps x (1 - overhead)) seconds1 GB = 8 x 10^9 bits SI units100 Mbps = 12.5 MB/s divide by 81 Gbps fiber, 1 TB file, 10% overhead ~2h 28mFor a 5 GB file on a 50 Mbps cable upload with 20% overhead, the math is: 5 x 8 x 10^9 = 40 billion bits, divided by (50 million x 0.80) = 40 million effective bps, equals 1,000 seconds, or 16 minutes 40 seconds. Without overhead the answer would be 800 seconds, undercounting by 25%.
Data transfer bits versus bytes
The bits-versus-bytes confusion runs deep. ISPs sell in bits per second because the number is eight times larger and looks more impressive. Operating systems show transfer speeds in bytes per second because file sizes are stored as bytes. The conversion is always divide-by-eight: 100 Mbps equals 12.5 MB/s, 1 Gbps equals 125 MB/s.
SI versus binary adds a second layer of confusion. ISPs and storage vendors use SI: 1 MB equals 1,000,000 bytes. Linux and RAM modules use the IEC binary form: 1 MiB equals 1,048,576 bytes. The two diverge by about 7% at the GB level. This calculator uses SI to match how bandwidth and storage are advertised.
Why data transfer overhead matters
Overhead is everything that prevents you from hitting the line speed printed on your ISP contract. TCP headers eat 5 to 10 percent. WiFi MAC contention costs another 10 to 30 percent depending on signal strength and competing devices. Long-distance routing adds latency and retransmission penalties. Cellular networks lose 25 to 40 percent at busy hours.
The realistic figure for sustained throughput is 60 to 85 percent of the advertised number. Wired gigabit Ethernet hits the high end; congested WiFi or 4G at peak hours hits the low end. Plan with 15% overhead as a sane default, more if the link is wireless or cellular.
Speedtest and Fast.com measure short, optimized traffic to nearby servers. A real backup running for an hour competes with other devices on your network, hits server-side throttles, and re-sends lost packets. Expect actual sustained throughput to come in 20 to 40 percent below your speed-test result.
Typical upload and backup speeds
Most residential plans are asymmetric: downloads are five to twenty times faster than uploads. A 100/10 cable plan means 100 Mbps down, 10 Mbps up. Fiber plans are usually symmetric, which is why cloud backups feel faster on fiber even at the same nominal speed.
- DSL upload 1 to 10 Mbps
- Cable upload 10 to 50 Mbps
- Fiber FTTH upload 100 to 1000 Mbps (often symmetric)
- 4G LTE upload 5 to 25 Mbps
- 5G upload 20 to 100 Mbps
- Office LAN 1 Gbps (1000 Mbps)
- Data-center fiber 10 to 100 Gbps
Data transfer for cloud and server moves
Cloud backups, virtual-machine migrations, and large file syncs are the most common reasons people run a data transfer calculation. A 1 TB initial backup at 50 Mbps cable upload with 20% overhead takes about 51 hours, or just over two days. That is why providers like Backblaze and AWS offer physical seed drives for the first sync; ongoing incremental backups only need to ship the daily delta.
For server-to-server moves inside a data center, the link is usually 1 to 10 Gbps Ethernet. A 100 GB VM image takes about 90 seconds at 10 Gbps even with full overhead. The bottleneck shifts from network to disk I/O.
For accurate estimates, run a 60-second iperf or speed-test between the actual source and destination, then plug that number into the calculator with zero overhead. The measured throughput already includes the real protocol and routing losses for that path.
Common data transfer mistakes
The classic mistake is comparing Mbps to MB/s as if they were the same unit. They differ by a factor of 8, and ignoring the case of the b versus B turns a 100 Mbps link into an imagined 100 MB/s monster. The second mistake is assuming the advertised rate is what you will get; subtract 15 to 25% for residential links. The third is forgetting upload asymmetry: a 100/10 plan uploads ten times slower than it downloads, and large backups will feel the gap.
A fourth mistake is ignoring file-system and disk-I/O limits on the endpoints. A 10 Gbps network link cannot move data faster than the source disk can read or the destination can write. A spinning hard drive caps at about 150 MB/s sequential, which is 1.2 Gbps. SATA SSDs run 500 MB/s (4 Gbps), NVMe drives 3 to 7 GB/s. For large backups, the slowest link in source-disk, network, and destination-disk wins.
A fifth, easy-to-miss issue is the small-file overhead. Transferring one 10 GB archive runs at near-line rate. Transferring 100,000 files totaling 10 GB through SFTP or rsync runs at a tiny fraction of that, because each file negotiates a new transfer. For backups of many small files, expect throughput well below what the calculator predicts; archive into a single tarball first when the underlying file system allows it.