How Long Does It Really Take to Download a Game? A Real-World Guide
A 50 GB game on a 500 Mbps line takes 13 minutes in theory and closer to 18 in practice. Here is where the missing time goes.
Modern games are enormous. A single title can be 150 GB, and a console refresh can mean re-downloading a library that took months to accumulate. Knowing whether something will finish in fifteen minutes or overnight changes what you do with your evening.
The short answer
A 50 GB game takes about 13 minutes on a 500 Mbps connection in theory, and 16-18 minutes in practice once launcher binary sizes and network overhead are included.
The gap between those two figures is the interesting part.
The theoretical table
Assuming your full advertised speed, continuously available, with decimal file sizes:
| Plan | MB/s | 20 GB | 50 GB | 100 GB | 150 GB |
|---|---|---|---|---|---|
| 25 Mbps | 3.13 | 1 h 47 m | 4 h 27 m | 8 h 53 m | 13 h 20 m |
| 50 Mbps | 6.25 | 53 m | 2 h 13 m | 4 h 27 m | 6 h 40 m |
| 100 Mbps | 12.5 | 27 m | 1 h 7 m | 2 h 13 m | 3 h 20 m |
| 200 Mbps | 25 | 13 m | 33 m | 1 h 7 m | 1 h 40 m |
| 500 Mbps | 62.5 | 5 m | 13 m | 27 m | 40 m |
| 1000 Mbps | 125 | 3 m | 7 m | 13 m | 20 m |
Now for the four reasons your actual download will not match this.
1. Launchers report binary gigabytes
Steam, Epic and the consoles all display sizes using 1,024-based units while calling them 'GB'. Your connection speed, meanwhile, is decimal.
50 'GB' in Steam = 53.7 decimal GBThat is a 7.4% penalty applied before anything else goes wrong. On the 50 GB / 500 Mbps row above, it turns 13 min 20 s into 14 min 19 s.
2. Network overhead
Every packet carries TCP/IP and TLS headers that occupy bandwidth without being part of the game. Combined with retransmissions and connection management, expect to lose 5-10% of your theoretical throughput before any other factor.
3. The server has an opinion
You can only download as fast as the content server sends. This is the single largest variable and the one you have least control over:
- Launch day and patch day put every player in the world on the same servers at once. Speeds routinely halve.
- Steam download regions vary enormously. A poorly chosen region can cost you more than a slow plan would.
- Console CDNs are generally reliable but throttle harder during peak evening hours.
4. Your disk, and what the console is doing
Downloading is only half the job. The launcher decompresses data and writes it to storage as it arrives.
- On an NVMe SSD, storage is never the bottleneck.
- On a SATA SSD, you are fine up to roughly gigabit speeds.
- On a mechanical hard drive, sustained writes of 80-160 MB/s are typical — and the decompression makes it worse. Above about 600 Mbps of connection speed, the drive becomes your limit.
Consoles add another wrinkle: on PlayStation, downloading while a game is running can cut throughput dramatically, and both major consoles slow downloads in rest mode on some settings.
Realistic times
Applying a binary size and 85% efficiency — a fair planning assumption:
| Plan | 50 GB theoretical | 50 GB realistic |
|---|---|---|
| 50 Mbps | 2 h 13 m | 2 h 48 m |
| 100 Mbps | 1 h 7 m | 1 h 24 m |
| 200 Mbps | 33 m | 42 m |
| 500 Mbps | 13 m | 17 m |
| 1000 Mbps | 7 m | 8 m |
As a rule of thumb, take the theoretical figure and add a quarter. That is close enough to plan an evening around.
Making it faster
- Use Ethernet. The single biggest improvement available to most people, and it costs nothing if the cable reaches.
- Change your Steam download region to a nearby, less congested one.
- Pause other traffic. A 4K stream is 25 Mbps you are not using for the download.
- Check for a throttle setting in Steam, Epic or your console's network options.
- Install to an SSD if the title is large and your drive is mechanical.
- Start it before bed for anything above about 100 GB on a sub-100 Mbps connection.
The takeaway
The arithmetic is simple — size divided by speed — but the honest answer is about 25% above the theoretical one, because launcher sizes are binary and no connection runs at 100% efficiency.
If your download is dramatically slower than that, the cause is almost never your ISP. Check Wi-Fi, then the download region, then your drive, in that order.