Skip to content
K Knidox Search…
Computer Science · Networking

Download Time Calculator

Estimate how long a download takes from file size and connection speed — handling megabits vs megabytes correctly.

How big is the file?
Size unitDecimal (1 MB = 1000 KB).
Your download rate.
Speed unitMbps/Gbps are bits; MB/s is bytes.
Common scenarios — tap to try
Estimated download time
6 min 40 sec

5 GB at 100 Mbps ≈ 400 seconds total (12.5 MB/s effective). Decimal (SI) units; ideal rate, before overhead.

To find download time, convert the file to bits (bytes × 8) and divide by the speed in bits per second. A 5 GB game is 40,000,000,000 bits; on a 100 Mbps line (100,000,000 bits/s) that is 400 seconds ≈ 6 min 40 sec. The ÷8 step matters because speeds are in megabits, files in megabytes.

Why 100 Mbps is not 100 MB/s

Internet plans are advertised in megabits per second (Mbps), but files are measured in megabytes (MB). A byte is 8 bits, so the two differ by a factor of 8. A 100 Mbps connection moves at most about 12.5 MB/s, which is why a “fast” plan can still feel slow when you watch the download counter tick over in megabytes. This calculator keeps the units straight: pick Mbps or Gbps when your speed is in bits, or MB/s when it is already in bytes, and it converts everything to bits before dividing.

Everything here uses decimal (SI) units, so 1 MB = 1000 KB = 1,000,000 bytes and 1 GB = 1,000,000,000 bytes. That matches how ISPs and file managers on macOS and Linux report sizes and speeds.

time (seconds) = file size × 8 ÷ speed in bits per second

1 byte = 8 bits · convert MB→bytes (×1,000,000) then bytes→bits (×8) before dividing

Worked example: 5 GB on 100 Mbps

Convert the file to bits, convert the speed to bits per second, then divide.

  1. 1
    Convert the file size to bytes. 5 GB × 1,000,000,000 = 5,000,000,000 bytes (decimal units).
  2. 2
    Convert bytes to bits (× 8). 5,000,000,000 × 8 = 40,000,000,000 bits, because 1 byte = 8 bits.
  3. 3
    Convert the speed to bits per second. 100 Mbps × 1,000,000 = 100,000,000 bits per second.
  4. 4
    Divide bits by bits per second. 40,000,000,000 ÷ 100,000,000 = 400 seconds.
  5. 5
    Express it as a readable duration. 400 seconds = 6 min 40 sec. This is the ideal time before overhead.

Megabits per second → megabytes per second

Divide Mbps by 8 for the maximum MB/s, then read a rough time for a 1 GB (1000 MB) file.

Plan speedMax MB/s (÷8)Time for 1 GB
25 Mbps3.125 MB/s≈ 5 min 20 sec
50 Mbps6.25 MB/s≈ 2 min 40 sec
100 Mbps12.5 MB/s≈ 1 min 20 sec
500 Mbps62.5 MB/s≈ 16 sec
1 Gbps125 MB/s≈ 8 sec

Why real downloads run slower than this

The number here is a best case: file size in bits divided by the raw link speed. Real transfers rarely hit it. Protocol overhead (TCP/IP and TLS headers, acknowledgements, retransmissions) skims a few percent off the top. The server or CDN may cap your rate, throttle after a burst, or be busy. Wi-Fi, powerline adapters, and shared household connections all lose speed to interference and congestion. Disk write speed can also become the bottleneck on very fast links. Treat this estimate as the ceiling and expect the actual time to land somewhat above it.

Why is my download slower than my plan speed?
The calculator shows the ideal time from your raw link speed. Real transfers lose a few percent to protocol overhead and often much more to server caps, Wi-Fi interference, network congestion, or a slow disk. Expect actual times to run above the estimate.
What is the difference between Mbps and MB/s?
Mbps is megabits per second; MB/s is megabytes per second. A byte is 8 bits, so MB/s = Mbps ÷ 8. A 100 Mbps connection tops out around 12.5 MB/s. Plans are quoted in Mbps, download managers usually show MB/s.
Why does the calculator multiply by 8?
File sizes are in bytes and connection speeds in bits, so the two must be in the same unit before dividing. Multiplying the file size in bytes by 8 turns it into bits, matching the speed. Skipping this step makes the answer eight times too small.
Does protocol overhead change the result?
Yes, a little. TCP/IP, TLS, and acknowledgement packets add roughly 3–10% overhead, so usable throughput is below the raw link rate. The tool reports the ideal time and leaves that margin out, so treat it as a floor on the real duration.
Does this use decimal or binary units?
Decimal (SI): 1 MB = 1000 KB = 1,000,000 bytes and 1 GB = 1,000,000,000 bytes. That matches how ISPs quote speeds and how macOS and Linux report file sizes. Windows counts some sizes in powers of 1024, which can make its figures look slightly different.
How do I estimate time for a 5 GB game on 100 Mbps?
5 GB is 40,000,000,000 bits (5 × 1,000,000,000 × 8). Divide by 100,000,000 bits per second to get 400 seconds, or about 6 min 40 sec — before any overhead.
Can I enter my speed in MB/s directly?
Yes. Choose the MB/s (megabytes/s) unit and the tool skips the ÷8 conversion, since your speed is already in bytes. Use Mbps or Gbps when your speed comes from a speed test or an ISP plan, which quote bits.