How to Calculate Download Time (With Examples)

The download-time formula and unit shortcut

The underlying rule is time equals data divided by rate. The only awkward part is that file sizes normally use bytes while internet speeds normally use bits per second.

With decimal units, one GB contains 8,000 megabits. That gives a practical shortcut when the file is in GB and speed is in Mbps.

• Exact form: time (seconds) = file size (bits) ÷ speed (bits per second)
• Decimal shortcut: time (seconds) = file size (GB) × 8,000 ÷ speed (Mbps)
• If speed is already in MB/s: time (seconds) = file size (MB) ÷ speed (MB/s)

• Calculate an exact download time

Worked example: 100 GB at 100 Mbps

Start with the decimal shortcut: 100 GB × 8,000 ÷ 100 Mbps. The multiplication gives 800,000 megabits, and dividing by 100 megabits per second gives 8,000 seconds.

Convert 8,000 seconds by dividing by 60. That is 133 minutes 20 seconds, or 2 hours 13 minutes 20 seconds. It is an ideal network-transfer time, not an installation estimate.

• 100 GB × 8,000 = 800,000 megabits
• 800,000 Mb ÷ 100 Mb/s = 8,000 seconds
• 8,000 seconds = 2 hours 13 minutes 20 seconds

Download-time cheat sheet: 1 GB to 100 GB

This table uses the same decimal formula and assumes a perfectly steady connection. It is useful for checking your own arithmetic before adding a real-world time allowance.

Turn a speed test into a realistic input

Run the test on the same device, in the same room, and on the same Wi-Fi or Ethernet connection that will handle the download. A result from a wired desktop does not describe a console behind two walls.

Repeat the test at least twice. If it swings from 180 to 240 Mbps, entering the lower normal result gives a safer plan than using the highest burst. For a long overnight transfer, a sustained rate observed during another large download is better still.

• Pause unrelated downloads and cloud backups before measuring.
• Check whether the result is Mbps or MB/s before entering it.
• Use download speed for downloads; do not substitute upload speed.
• If a VPN will remain active, measure with that VPN active.

Why a launcher ETA keeps changing

Steam, PlayStation, Xbox, browsers, and app stores estimate the remaining time from recent throughput. When the rate changes, the ETA changes with it. That behaviour is normal and often more honest than freezing the first estimate.

The network may also pause while the device verifies, decrypts, decompresses, patches, or writes data. A launcher can therefore show a low network rate even when the internet connection itself is healthy.

• Wi-Fi interference and distance change usable throughput.
• Busy content servers can cap a single user or region.
• Other devices compete for the same connection.
• Packet loss causes retransmissions.
• Storage and CPU work can become the bottleneck during installation.

Decimal GB, binary GiB, and the 7.4% gap

Network rates use decimal SI units. NetCalcKit therefore treats 1 GB as 1,000,000,000 bytes and 1 Mbps as 1,000,000 bits per second. Some operating systems and technical tools use binary units, where 1 GiB is 1,073,741,824 bytes.

One GiB contains about 7.4% more bytes than one decimal GB. If a screen labels binary data as GB, a hand calculation using decimal GB can look a little too optimistic even before network overhead is considered.

• Check the difference between Mbps, MB/s and MiB/s

Mistakes that produce believable but wrong times

The most dangerous mistakes do not create an obviously absurd answer. They create a neat-looking ETA based on the wrong unit or the wrong speed.

• Dividing GB directly by Mbps without converting bytes to bits.
• Reading 100 Mbps as 100 MB/s and making the answer eight times too fast.
• Using the internet plan maximum instead of the device’s sustained rate.
• Using installed size when the launcher lists a smaller compressed download.
• Adding no allowance for server limits, Wi-Fi variation, or protocol overhead.
• Treating download time as total time even though verification and installation follow.