Skip to content

Video

Download & Upload Time Calculator

Calculate download and upload times for any file size — covering game downloads, video uploads, and cloud backups — with real-world protocol overhead.

Looking for all-in-one video bitrates, file sizes, and transfer calculations?Open Video File Size & Bitrate Suite →
File Size Presets:
Common Connection Speeds:
23m 24s
Need the bandwidth behind those speeds, or why Mbps ≠ MB/s?Mbps to MB/s →Bytes vs Bits guide →

Game Sizes in the Real World

Triple-A titles have grown past 100 GB, and the download-time arithmetic explains why patch nights feel longer than they should: at 300 Mbps with 5% overhead, the calculator puts a 50 GB download at roughly 23 minutes — but a 120 GB Call-of-Duty-class title at the same speed is nearly an hour, and on a 100 Mbps line it crosses two and a half hours.

The overhead input exists because the pipe never delivers 100% of its rated rate. Protocol headers, Wi-Fi retransmissions and concurrent devices routinely consume 5–15%. If your measurements consistently disagree with the estimate, the fix is usually measuring the real throughput and entering that — not doubting the math.

Planning a Download or Upload Realistically

The basic estimate is file size in bits divided by line speed in bits per second. A 60 GB game on a 300 Mbps line is 480,000 megabits, so about 1,600 seconds, or roughly 27 minutes, before overhead. Protocol overhead and server throttling usually add 5 to 15 percent.

Uploads deserve their own check, because residential connections often have far lower upload than download speed. A 5 GB video that downloads in a few minutes can take over an hour to send on a 10 Mbps uplink. If the figure is far from your experience, test the connection at a quiet hour: shared Wi-Fi and busy evenings are the usual reasons the actual time is longer.

How the Estimate Is Built

  1. Enter the file size and your measured connection speed (use the speed you actually get, not the plan rate).
  2. The transfer time accounts for configurable protocol overhead — TCP/IP headers typically cost 5%.
  3. Downloads and uploads use the same math but different real-world speeds: home connections are asymmetric, so upload runs slower.
Formula & Technical Standard
Time (s) = (File Size in Bytes * 8) / (Speed in bps * (1 - Overhead %))

Worked Example

50 GB Game Download
Input: 50 GB at 300 Mbps
Output: Approx. 23 minutes 24 seconds
Reflects real transfer time on home broadband.
5 GB Video Upload
Input: 5 GB at 20 Mbps upstream
Output: Approx. 35 minutes 45 seconds
Upload runs at the upstream rate, which on cable and ADSL is far slower than download.

Common Questions

Why do downloads take longer than the math says?

Server bandwidth caps, CDN throttling, and Wi-Fi signal interference lower throughput. The calculation is exact for the speed you enter, so the practical trick is measuring your real speed.

How accurate is the estimate?

Estimates are mathematically exact for the throughput you enter, but real-world accuracy is roughly +/-10-20% because of server throttling, network congestion, and Wi-Fi packet loss. Use a realistic measured speed instead of your plan rate for best results.

Why is my upload much slower than my download?

Residential broadband is asymmetric by design: providers allocate more bandwidth downstream because browsing and streaming consume far more than they produce. Fiber symmetric plans are the exception.

Does the file size units choice matter?

Yes — a "50 GB" download is 50 decimal gigabytes (50 × 10^9 bytes) from most stores, while your operating system may show the same file as 46.6 GiB. The difference is decimal vs binary units, covered in the Data Storage Converter.

Deeper context: read our related guide.