Skip to content
ToolBoxGeniehome

Download Time Calculator

Calculators · Added

A hundred-megabit connection does not download a hundred megabytes a second — it downloads twelve and a half, because a byte is eight bits, and that single factor of eight is behind most of the disappointment people feel about their broadband. This works out how long a file actually takes, keeps bits and bytes explicitly apart, handles both the decimal and binary meanings of a gigabyte, and shows the same file against a range of connection speeds so the number has something to be compared with.

%

Leave at 100 for the theoretical best case. Real transfers rarely reach the full line rate.

Try:

How to use the download time calculator

  1. 1Enter the file size and choose its unit — GB and GiB are different by 7.4%, and both are offered.
  2. 2Enter your connection speed and choose whether it is quoted in bits per second or bytes per second.
  3. 3Leave the throughput percentage at 100 for the theoretical best case, or lower it to reflect what you actually see.
  4. 4Press Calculate.
  5. 5Read the time, and use the comparison table to see what a faster or slower connection would give.

Examples

A film on standard fibre

Input
5 GB at 100 Mbps
Result
6 min 40 s

The line carries 12.5 MB every second, so 5,000 MB takes 400 seconds.

A large game download

Input
50 GB at 300 Mbps
Result
22 min 13 s

Tripling the connection speed cuts the time to a third — the relationship is simple, which is why the surprise is always in the units rather than the arithmetic.

The same file on an old line

Input
700 MB at 8 Mbps
Result
11 min 40 s

A single CD's worth of data. It is a useful reminder of what the units mean: 700 MB is 5,600 megabits.

About the download time calculator

The three unit traps, in order of how often they bite

The first and biggest is bits against bytes. Networking has quoted speeds in bits per second since long before personal computers existed, and storage has been measured in bytes for just as long. The two units meet at the download progress bar, and the factor of eight between them is the single most common reason a connection feels slower than it was sold as. The convention that helps is capitalisation: a lower-case b means bits, as in Mbps, and an upper-case B means bytes, as in MB/s.

The second is decimal against binary prefixes. A kilobyte is a thousand bytes by the SI definition and 1,024 bytes by long-standing computing habit. The difference is 2.4% at kilo, 4.9% at mega, 7.4% at giga and 10% at tera — small enough to overlook and large enough to explain a missing forty gigabytes on a new drive. The IEC introduced KiB, MiB and GiB in 1998 to name the binary versions unambiguously, and this page offers both.

The third is the quietest: a connection speed is a capacity, not a guarantee. It describes the rate at which the link can carry data, in the same way a road's speed limit describes how fast you may drive rather than how fast you will get home. Everything between you and the server — the server itself, the peering between networks, the Wi-Fi in the room — can be the thing that decides the actual figure.

Reading the comparison table

The table shows the same file against a spread of common connection speeds, and its purpose is to make the shape of the relationship visible. Time is inversely proportional to speed, so doubling the connection halves the wait — but the absolute saving shrinks as speeds rise. Going from 8 Mbps to 25 Mbps takes a five-gigabyte download from about eighty-three minutes to twenty-seven, a saving of nearly an hour. Going from 300 Mbps to a gigabit takes the same file from two and a quarter minutes to forty seconds.

That diminishing return is worth knowing before paying for an upgrade. Beyond a few hundred megabits, the time spent waiting for a large download stops being the thing that shapes how the internet feels, and latency, server capacity and local Wi-Fi start to dominate. A gigabit line on a congested 2.4 GHz Wi-Fi channel will deliver a worse experience than a hundred-megabit line on a cable.

Where the higher speeds do still earn their keep is concurrency rather than single files: several people streaming at once, a large upload running in the background, or a machine syncing while somebody else is on a call. Those are capacity problems, and capacity is exactly what the headline figure buys.

Frequently asked questions

Why is my 100 Mbps connection only downloading at 12 MB/s?
It is doing exactly what it says, and the two figures are the same speed written differently. Connection speeds are sold in bits per second and file sizes are measured in bytes, and there are eight bits in a byte. Divide 100 by 8 and you get 12.5 MB/s, which is the number a download manager shows. Nothing is being lost — the unit simply changed between the advertisement and the progress bar.
What is the difference between GB and GiB?
A gigabyte is a thousand million bytes, using the decimal prefix that the SI system defines and that drive manufacturers and ISPs use. A gibibyte is 2³⁰ bytes, or 1,073,741,824, which is 7.4% larger. Operating systems have historically shown the binary figure while labelling it GB, which is why a drive sold as 1 TB shows up as roughly 931 GB. Both units are offered here so a size can be entered as whatever it was actually quoted in.
Why does the real download take longer than this says?
Because the line rate is the ceiling, not the delivery. Protocol headers occupy part of every packet, acknowledgements travel back up the link, encryption and connection setup cost time before any data moves, and the file has to be written to a disk that may be slower than the network. On top of that, a single download is limited by whatever the server is willing to send you, which is often well below your capacity. The throughput percentage exists to fold all of that into one honest number rather than pretending to model it.
Does uploading work the same way?
The arithmetic is identical — swap your upload speed into the box. What differs is the figure to use. Many connections are asymmetric by design, with upload speeds a fraction of download, and on older cable and DSL lines the difference can be tenfold. Check the upload figure specifically rather than assuming it matches, particularly before scheduling a large backup.
Will a faster connection always make downloads quicker?
Only up to the point where something else becomes the constraint. If a server limits each connection to 5 MB/s, upgrading from 100 Mbps to 1 Gbps changes nothing for that download, though it does let several run at once at full speed. Latency matters too: a distant server with a long round-trip time can take a while to reach full rate regardless of capacity, which is why a large file from a nearby mirror often beats the same file from a faster but further one.

Related tools