Use effective throughput
A nominal 100 Mbps connection may deliver less for the actual transfer. Wi-Fi, VPNs and busy networks can make observed throughput much lower.
Use tool
đź”’ Inputs are processed locally in your browser.
FREE WEB TOOL
Estimate file transfer time from file size, throughput, latency and an estimated number of round trips.
đź”’ Inputs are processed locally in your browser.
Estimate transfer time from file size and effective throughput, then add a simple latency component based on latency per round trip and an estimated round-trip count. It is a planning model, not a network simulator.
30 ms × 20 = 600 ms is added. For a large file, throughput usually dominates this simple fixed-latency term.This does not simulate TCP congestion control, TLS handshakes, HTTP/2 or HTTP/3, or parallel transfers. It is only a “base transfer plus fixed round-trip waits” estimate.
A nominal 100 Mbps connection may deliver less for the actual transfer. Wi-Fi, VPNs and busy networks can make observed throughput much lower.
If your measurement is one-way delay rather than RTT, convert or interpret it consistently before using it here.
Use 0, 1, 2 and so on for the number of latency waits you want to add to the model.
For multi-gigabyte transfers, hundreds of milliseconds of fixed waiting can be tiny compared with the total data-transfer time.
Protocol behavior and concurrency matter much more for request-heavy workloads. Use browser/network traces or load testing for production performance work.
Related references: Digital storage units · SI prefixes & units