Article — Download Time Calculator
The download time calculator, explained
Download time equals file size divided by speed. The arithmetic is one line: a 1 GB file at 100 Mbps takes about 82 seconds. The work is matching units before dividing — file sizes are in bytes, connection speeds are advertised in bits, and the factor of 8 between them is the most common source of confusion about why downloads feel slower than the plan suggests.
What "download time" depends on
Two numbers set the theoretical minimum: how big the file is, and how fast the connection moves data. Everything else — server response time, route congestion, WiFi overhead, the CPU speed of your laptop — adds delay on top of that minimum. A download time calculator gives you the floor. Real-world results are usually 10-20% above the floor.
For files under a few megabytes, latency (round-trip delay) matters as much as bandwidth. For files above a few hundred megabytes, bandwidth dominates. A 5 GB game install runs the connection at full tilt for most of its duration; a 50 KB web page loads in the time it takes a packet to round-trip the server twice.
The download time formula
time = size / speed (both in matching units)seconds = bits / (bits per second) core form1 byte = 8 bits conversion factorThe widget handles the unit translation internally. You enter the file size in KB, MB, GB, or TB and the speed in Mbps, MB/s, or Gbps. Internally it converts to bits and bits per second, divides, and presents the answer as a human-readable duration.
The FCC redefined US broadband in March 2024. The minimum benchmark moved from 25/3 Mbps to 100/20 Mbps — meaning a service must deliver at least 100 Mbps down and 20 Mbps up to be marketed as "broadband." The old 25 Mbps standard had been in place since 2015 and was widely seen as obsolete.
Mbps versus MB/s: the factor of 8
The single most common source of "why is my internet slower than advertised" is a unit confusion. ISPs advertise in Mbps — megabits per second. Browsers and download managers report progress in MB/s — megabytes per second. One byte is eight bits, so MB/s is always Mbps divided by 8.
A 100 Mbps plan downloads at 12.5 MB/s peak. A 1 Gbps fiber line tops out at 125 MB/s. The numbers feel wrong only because the advertising unit was chosen to look bigger. Both measurements describe the same connection.
Download time by connection type
What "fast enough" looks like depends on the file. A 1 GB HD movie:
- 10 Mbps (slow DSL, congested cell) — about 13 minutes
- 25 Mbps (low-end cable, old broadband floor) — 5.4 minutes
- 100 Mbps (current US broadband floor) — 82 seconds
- 500 Mbps (typical good cable or DOCSIS 3.1) — 16 seconds
- 1 Gbps (gigabit fiber, mid-band 5G) — 8.6 seconds
- 10 Gbps (high-tier fiber, business links) — under one second
For a 50 GB game install, multiply each of those by 50. Even a 1 Gbps line takes seven minutes to pull down a modern triple-A title, which is why background steam downloads are a built-in feature of most launchers.
Real-world download time vs theoretical
The formula gives ideal numbers. Reality runs slower for three reasons. Protocol overhead — TCP/IP headers, TLS handshakes, retransmissions — eats 5-10% of bandwidth. Congestion control means TCP backs off when it detects packet loss, so a saturated path delivers less than its raw capacity. And the slowest hop between you and the server caps the entire transfer; if a midpoint router is congested, your fiber line cannot compensate.
A good rule of thumb: divide ideal time by 0.85. A 1 GB file at 100 Mbps takes about 82 seconds in theory and 95-100 seconds in practice. For TCP-based downloads from a well-provisioned CDN (Cloudflare, Akamai, Fastly), the gap is closer to 5%. For peer-to-peer transfers or downloads from undersized origin servers, the gap can be much larger.
If a speed test (Ookla Speedtest, Fast.com) shows the plan but real downloads do not, the bottleneck is not the ISP. Suspect WiFi (5 GHz radio versus 2.4 GHz, distance to router), the source server, or your device. Wired Ethernet plus a CDN-hosted file is the cleanest way to confirm that the link itself is delivering.
Binary versus decimal gigabyte
File sizes use two definitions that disagree by about 7.4%. Windows and Linux file managers report sizes in binary units: 1 GB = 1024 MB = 1,073,741,824 bytes. Storage vendors and network speeds use decimal: 1 GB = 1000 MB = 1,000,000,000 bytes. A "1 TB" hard drive labelled by a vendor is 909 binary GB when the operating system reports it.
This widget uses binary for file size to match what file managers show, and decimal for connection speed to match how ISPs measure. The slight mismatch is the reason the "multiply MB by 8" shortcut is not exact — the actual factor is about 8.39 to reconcile the unit systems.
Troubleshooting slow downloads
A four-step diagnosis covers most cases. First, run a speed test on a wired device — if it matches the plan, the ISP link is fine. Second, retry the slow download from a different source (a CDN-backed file, not a hobbyist server). Third, check WiFi by repeating the download next to the router. Fourth, look at simultaneous activity on the network — streaming, gaming, and large uploads share the link.
If the speed test fails to deliver advertised speed on wired Ethernet, the issue is upstream: a congested neighbourhood node, a degraded copper or coax run, a saturated peering link between your ISP and the source's transit provider. ISP support can usually narrow it down with a line check.
Download time on cellular networks
Cellular performance varies more than fixed broadband. Mid-band 5G can hit 500-900 Mbps in good coverage and drop below 50 Mbps a hundred metres later as the device falls back to 4G LTE or to a more distant cell. Download time on cellular is dominated by signal quality, cell loading, and carrier-imposed throttling on certain plans, not by the headline speed advertised in marketing.
Two practical implications. First, a single bad speed test on a phone does not represent the connection — run several at different times. Second, large downloads on cellular often work better at off-peak hours; midnight to 6 AM typically shows 2-3x the throughput of evening prime time on the same line because fewer users compete for the same radio capacity.
Old WiFi 5 gear caps around 400 Mbps real-world; WiFi 6/6E supports much higher. If you bought a gigabit plan and downloads run 300 Mbps, the router or the device's wireless chipset is the bottleneck, not the line. Test on wired Ethernet before blaming the ISP.