A 90 GB game on a 100 Mbps connection. Go make dinner. Then go make breakfast.
Use this free download time calculator to estimate how long a download will take. Enter the file size in GB and your connection speed in Mbps, and get the time in minutes — for game installs, OS updates, video files, and backups.
The confusion here is deliberate and industry-wide: files are measured in bytes, internet speeds in bits, and there are 8 bits in a byte. That factor of eight is why a "100 Mbps" connection downloads at about 12 MB/s and why everyone feels slightly cheated.
Inputs:
Steps:
Megabits = Size (GB) × 1,024 × 8 Seconds = Megabits ÷ Speed (Mbps) Minutes = Seconds ÷ 60
At 100 Mbps, about 2.3 hours. At 500 Mbps, 27 minutes. At 1 Gbps, roughly 14 minutes — assuming the server can keep up, which is often the real limit.
Because plans are advertised in megabits and downloads display megabytes — divide by 8. A 400 Mbps plan shows about 50 MB/s at best, minus Wi-Fi and overhead losses.
Divide by 8. 100 Mbps = 12.5 MB/s, 300 Mbps = 37.5 MB/s, 1 Gbps = 125 MB/s. This single division explains most internet complaints.
Streaming 4K needs about 25 Mbps per stream, video calls 3–5 Mbps, gaming very little bandwidth but low latency. Large downloads are the only common task that genuinely benefits from 500+ Mbps.
No — it gives the theoretical best case at the speed you enter. Protocol overhead, Wi-Fi, and server limits typically add 10–20%, so treat the result as a floor.
We roast the number, not you. Two hours is the download. The 40 minutes of "preparing to install" afterward is between you and the launcher.
Real downloads rarely sustain peak speed. Server capacity, network congestion, Wi-Fi interference, and other devices in the house all cut throughput, and some ISPs shape large transfers. Use the estimate for planning and expect 10–25% longer in practice.
Minutes = (GB × 1,024 × 8) ÷ Mbps ÷ 60, binary GB, no overhead allowance. Educational & entertainment only.
Generated for educational and entertainment purposes.