Data Transfer Time Guide
Transfer math in one line
Transfer time is calculated with: time = data size / speed. If you know a deadline and data size, required speed is speed = data size / time.
These formulas are simple, but planning accuracy depends heavily on unit conversion and real throughput, not headline speeds.
Bits vs bytes
- b means bits, B means bytes.
- 1 byte = 8 bits.
- 100 Mbps is not 100 MB/s. It is about 12.5 MB/s before overhead.
Mbps vs MB/s and binary units
- Mbps, Gbps: commonly used for network links.
- MB/s, GB/s: commonly used for storage and application throughput.
- MiB/GiB use binary base (1024), while MB/GB use decimal base (1000).
Always confirm which unit a tool or provider is showing before estimating transfer duration.
Real-world bottlenecks
- Protocol overhead (TCP/IP, TLS, application layer).
- Congestion and packet loss on shared links.
- Wi-Fi signal quality and interference.
- Source and destination disk throughput limits.
- Cloud-side throttling and API rate limits.
Cloud and backup planning tips
- Use measured sustained throughput, not advertised peak bandwidth.
- Add margin for retries and contention during business hours.
- Separate planning for full backups vs incrementals.
- Model WAN and cloud paths independently when multi-hop.
Example calculations
- 500 GB at 20 Mbps: roughly 55+ hours before overhead adjustments.
- 1 TB at 1 Gbps: roughly 2.2 hours under ideal sustained throughput.
- 10 TB at 10 Gbps: roughly 2.2 hours ideal, usually higher in practice.