Download Time Calculator

Using the download time calculator

1. Enter the file size and pick its unit, from KB to PB.
2. Enter your download speed and pick its unit. Internet plans are quoted in bits per second (kbps, mbps, gbps, tbps), while download managers and file copy dialogs usually show bytes per second (B/s, KB/s, MB/s, GB/s, TB/s).
3. Tick Use SI standard if you want a kilobyte to mean exactly 1,000 bytes. Leave it clear for the 1,024-byte convention that Windows uses.
4. Press Estimate duration & ETA.

The result lists the duration in seconds and in minutes and hours, plus days and weeks once the transfer is long enough to reach them. The last line, Download ETA, is your device's clock plus the duration, shown in your own time zone. It assumes the transfer starts the moment you press the button and never pauses.

The seconds are always rounded up to a whole second, and the other units are worked out from that figure, so a 0.3-second transfer still reads 1 second. For hours and days, a remainder is shown in brackets when it helps, for example 1.42 (1 hours 25.33 minutes).

The same arithmetic applies to uploads: just enter your upload speed instead.

Bits per second versus bytes per second

A byte is eight bits. Network speeds are traditionally counted in bits per second, and file sizes in bytes. That is why a 100 Mbps plan seems to download at only 12.5 megabytes per second: 100 ÷ 8 = 12.5. Mixing the two up is the most common reason for a wrong estimate, and it makes the true download look eight times slower than expected.

The lower-case b in Mbps means bits, and the upper-case B in MB/s means bytes. To switch between them directly, use the Mbps to MB/s converter, the MB/s to Mbps converter or the general data storage and bandwidth converter.

How download time is calculated

Time is the amount of data divided by the rate at which it moves. Converting both to bits makes the units agree:

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

Worked example. A 2 GB file on a 25 Mbps connection.

• With SI units, 2 GB = 2 × 10⁹ bytes = 16 × 10⁹ bits. Dividing by 25 × 10⁶ bits per second gives 640 seconds, which is 10.67 minutes.
• With conventional units, 2 GB = 2 × 1,024³ = 2,147,483,648 bytes, or 17,179,869,184 bits. Dividing by 25,000,000 gives 687.19, rounded up to 688 seconds, which is 11.47 minutes.

The gap between the two answers, about 7.4%, comes entirely from the size convention. Bit rates are counted in thousands in both modes, because a megabit per second is defined as 1,000,000 bits per second.

To estimate a transfer in the other direction, rearrange the formula. The speed you need to finish in a given time is the size in bits divided by that time, and the amount you can move in a given time is the speed multiplied by the time.

SI or conventional units?

Two conventions are in use for storage sizes. The SI standard treats kilo, mega, giga, tera and peta as powers of 1,000, so 1 KB = 1,000 bytes and 1 GB = 1,000,000,000 bytes. Drive makers and many download sites advertise sizes this way. The conventional (binary) system counts in powers of 1,024, so 1 KB = 1,024 bytes and 1 GB = 1,073,741,824 bytes. Windows reports sizes this way, and the gap grows at each step: about 2.4% at KB, 4.9% at MB and 7.4% at GB.

Choose the option that matches how the size you are typing was measured. If a download page says 4.7 GB and your operating system says 4.38 GB for the same file, both are right; they use different units.

In conventional mode the KB/s speed option is counted as 1,048.576 bytes per second (one thousandth of a 1,048,576-byte MB/s), which is a long-standing quirk of how this calculator derives that unit. If you need exactly 1,024 bytes per second, enter the speed in B/s or MB/s instead.

How long will it take? Common sizes and speeds

Real transfers rarely reach these figures, as the next section explains.

Why real downloads take longer than the estimate

The calculator gives a theoretical minimum: the whole advertised speed, used continuously. In practice several things take a bite out of it:

• Protocol overhead. Headers, acknowledgements and encryption mean that part of every second carries control data rather than your file, commonly a few percent.
• Wi-Fi. Radio links share the air with neighbours and other devices and slow down with distance and walls. A cable connection is steadier.
• The sender's limits. A busy or throttled server may deliver far less than your line could take.
• Congestion and peak hours. Shared links on your provider's network, or between networks, slow down when many people use them.
• Competing traffic. Streaming, cloud backups and updates on other devices share the same connection.
• Latency and many small files. Each file needs a request and a response, so thousands of small files take much longer than one file of the same total size.
• Disk speed and CPU. Extracting, scanning or writing to a slow drive can hold the transfer back.

A practical rule is to treat the estimate as a floor and add a margin, perhaps 10 to 30 percent for a stable wired connection and more for Wi-Fi or a remote server.

Ways to speed up a download

• Use a cable connection or move closer to the router.
• Pause other transfers and streams that share the line.
• Download at off-peak times if the source is busy.
• Choose a nearer mirror or a content delivery network location when one is offered.
• Use a download manager that resumes interrupted transfers and opens several connections.
• Upgrade the plan only if the measured speed is the bottleneck. Check what you really get first, since the number on the bill is a maximum.

File type makes little difference to the time, because a network moves bytes and does not care what they mean. What matters is size, and whether the file is already compressed: zipping a folder of text can shrink it a lot, while photos, video and archives barely compress further. If you are planning storage as well as transfers, the RAID calculator shows how much space an array of drives leaves you.