BYTETOOLS

Download Time Calculator

Calculate how long a download takes from file size and connection speed, with correct Mbps vs MB/s handling, overhead allowance and the speed you need.

14 min 2 s
Download time
95.00 Mbps
Effective speed
842.1
Exact seconds

How it is calculated

time = (bytes × 8) ÷ (speed in bit/s × (1 − overhead)) = 80,000,000,000 bits ÷ (100 Mbps × 0.95)

Invert it: speed needed for a target time

You need at least 140.35 Mbps (17.54 MB/s) including the overhead allowance.

What is the Download Time Calculator?

The Download Time Calculator tells you how long a file transfer really takes. It handles the unit trap that skews most manual estimates — internet plans are sold in megabits per second while files are measured in megabytes, an 8× difference — and lets you choose decimal (1 GB = 10⁹ bytes) or binary (GiB) size conventions to match what your file manager shows.

  • Correct bits-vs-bytes conversion between Mbps plans and MB/s file sizes
  • Decimal (1000) or binary (1024) size convention toggle
  • Protocol overhead allowance for realistic estimates
  • Shows the full formula with your numbers substituted
  • Inverse mode — speed required to finish in a target time
  • 100% client-side arithmetic — works offline, nothing uploaded

How to use the Download Time Calculator

  1. 1

    Enter the file size and pick its unit (KB to TB).

  2. 2

    Enter your connection speed in Mbps, Gbps or MB/s — whichever you know.

  3. 3

    Adjust the overhead percentage if you want a more conservative estimate.

  4. 4

    Read the download time, and use the inverse section to find the speed needed for a target time.

About the Download Time Calculator

The Download Time Calculator tells you how long a file transfer really takes. It handles the unit trap that skews most manual estimates — internet plans are sold in megabits per second while files are measured in megabytes, an 8× difference — and lets you choose decimal (1 GB = 10⁹ bytes) or binary (GiB) size conventions to match what your file manager shows.

A configurable overhead percentage accounts for TCP/IP and TLS framing, retransmits and server throttling, so the estimate reflects reality rather than the theoretical line rate. The full formula is shown with your numbers plugged in, and an inverse mode answers the opposite question: what speed do I need to finish this download in a given number of minutes?

It works for any transfer — game downloads, backups, uploads to cloud storage — and runs 100% locally in your browser. Nothing is measured, uploaded or logged; it is pure arithmetic, available offline.

Frequently asked questions

How long does 1 GB take to download at 100 Mbps?

About 80 seconds at full speed: 1 GB is 8,000,000,000 bits, and 100 Mbps moves 100,000,000 bits per second. With a realistic 5–10% protocol overhead you land around 84–89 seconds. If it takes far longer, the bottleneck is usually Wi-Fi, the server or your plan's real-world speed.

What is the difference between Mbps and MB/s?

Mbps is megabits per second and MB/s is megabytes per second — a byte is 8 bits, so 100 Mbps equals only 12.5 MB/s. ISPs advertise in bits (bigger numbers), download managers report in bytes, and confusing the two makes transfers look eight times slower than promised.

Why is my actual download slower than this calculation?

The line rate is a ceiling, not a promise. TCP/IP and TLS overhead, Wi-Fi loss, a slow or throttled server, other devices sharing the connection and VPNs all cut into it. The overhead field models the protocol share; a server-side cap can only be fixed by a faster mirror or a download manager with multiple connections.

Does upload time work the same way?

Yes — the same formula applies, but use your upload speed, which on most home connections is far lower than the download figure. A plan sold as 100/20 uploads at 20 Mbps, so pushing 1 GB to cloud storage takes roughly 400 seconds rather than 80.

Should I use the 1000 or 1024 convention for file sizes?

Use 1000 when the size comes from a website, drive label or macOS, and 1024 when it comes from Windows Explorer, which reports GiB while writing GB. The gap is about 7.4% per step at the gigabyte level — enough to notice on large downloads.

Related tools