Steam Downloads Slow? Fix the Real Bottleneck
Measure whether Steam, your disk or your line is the limit, then fix that layer: bandwidth cap, region, shader pre-caching or the drive.
A Steam download that crawls at 4 MB/s on a 500 Mbps connection looks like a Steam problem and usually is not. Steam is doing three things at once while it downloads - pulling compressed chunks from a content server, unpacking them, and writing the result to disk - and the slowest of those three sets the number you see. Change the wrong one and nothing improves, which is why the usual advice list ("clear your cache, change your region") works for some people and wastes an evening for everyone else.
This walkthrough measures first, then fixes the layer that is actually limiting you. Menu names below were written against the current Steam client for Windows; Valve moves and renames settings between client updates, so if a path is missing, the search box in Steam Settings will usually find the option under its new name.
Step 1: Read the Number Properly
Steam reports speed in megabytes per second, while your internet plan is sold in megabits per second. Divide the plan figure by eight to get the theory ceiling:
| Plan speed | Ceiling in Steam's units | Realistic peak on a good server |
|---|---|---|
| 100 Mbps | 12.5 MB/s | 10 to 11.5 MB/s |
| 300 Mbps | 37.5 MB/s | 30 to 35 MB/s |
| 500 Mbps | 62.5 MB/s | 48 to 57 MB/s |
| 1 Gbps | 125 MB/s | 90 to 110 MB/s |
Now watch the download screen for two minutes rather than ten seconds. The speed graph at the bottom of the Downloads page tells you more than the instantaneous figure: a line that holds steady at a low value is a throttle; a line that spikes to your ceiling and then collapses to zero repeatedly is a disk or unpacking problem; a line that sawtooths gently is server-side variation and needs no fix.
Confirm with Task Manager (Ctrl + Shift + Esc, Performance > Ethernet or Wi-Fi). If Task Manager shows the adapter receiving at 55 MB/s while Steam displays 12 MB/s, the data is arriving and Steam is spending its time on something else - almost always disk writes or decompression, and the fix is in Step 4, not Step 2.
Step 2: The Bandwidth Limiter Is On More Often Than People Think
Steam has a global cap that persists across restarts and is easy to set by accident - some users set it years ago to stop downloads saturating a shared connection and forgot. Check it before anything else:
- Open Steam > Settings > Downloads.
- Find Limit download speed. If it is ticked, untick it and watch the graph for thirty seconds.
- In the same panel, check Allow downloads during gameplay and Throttle downloads while streaming. Both can silently cap throughput when another Steam feature is active, including Remote Play.
Two neighbours of that setting cause the same symptom. Schedule auto-updates restricts the window in which downloads run at full speed; a queue that starts at 20:00 and slows at 22:00 is following a schedule, not failing. And if a game is set to Only update this game when I launch it, the queue behaves differently from what the Downloads page implies - the item sits at "Queued" and never starts.
Step 3: Change the Download Region Only After Measuring
The region setting decides which content server cluster you pull from, and it is persistent: Steam does not re-test it for you. The advice to pick a nearby country is mostly right, but the region with the lowest latency is not always the one with the best throughput - a nearer cluster can be congested while a slightly further one is idle.
- Go to Steam > Settings > Downloads > Download Region.
- Note your current speed over a full minute. Change to a neighbouring region, restart Steam so the change takes effect, and download a small update from your library - not a new 80 GB install, which wastes the test.
- Keep the best of three. If none of them beats your original, the region was not the problem, and you should put it back.
One caveat worth knowing: a region change can reset the client's connection to a depot mirror, and some networks (university and corporate) block the ports used by regions outside their own country. If speeds collapse to under 1 MB/s after a change, revert immediately.
Do not clear the download cache as a first step. Clearing it deletes partially downloaded content for every queued item and forces re-verification of installed games, which on a large library can take longer than the download you were trying to speed up. Try it only after Steps 2 and 4 have been ruled out.
Step 4: Find the Disk and CPU Bottleneck
Steam downloads compressed chunks and unpacks them, so the write path and the CPU both matter. On a mechanical drive, or an SSD that is nearly full and has run out of SLC cache, the unpacking step becomes the limit and the network sits idle between bursts.
- Watch Task Manager during a download. High disk queue with low network throughput means the drive is the bottleneck. High CPU with low disk and low network means decompression is the limit - expected on older four-core CPUs during large updates.
- Check free space. Steam needs room for the compressed download plus the unpacked files, and refuses to run at full speed when free space drops below roughly twice the download size. Moving the library to a drive with space is done from Settings > Storage > the drive's menu > Move.
- Install to an SSD rather than an HDD. The gap is large and measurable: the load-time comparison in this SSD versus HDD breakdown shows the same effect that a 30 GB update produces at write time.
Windows can also be the bottleneck without Steam's knowledge. Delivery Optimization (Settings > Windows Update > Advanced options > Delivery Optimization) will upload chunks to other PCs on your network or the internet while Steam downloads, competing for the same uplink. Turning off "Allow downloads from other devices" removes a contention source that shows up as an unexplained 10 to 20% loss.
Step 5: Shader Pre-Caching and the Silent Background Downloads
Steam downloads shader pre-caching data for many titles, and on some systems this runs alongside game downloads, halving the visible speed without appearing in the queue. It is worth checking once:
- Go to Settings > Downloads and find Shader Pre-caching. Set it to Only pre-cache shaders for games I play recently, or disable it entirely if disk space and bandwidth matter more than first-launch smoothness.
- Open the Downloads page and look for items with a small download size but a long completion estimate - these are usually shader or workshop items, and they can be paused individually without affecting the main game.
- Check Library > Downloads for the auto-update queue. A dozen games each pulling a 400 MB update every day will eat a bandwidth budget invisibly; setting them to update on launch only is the fix.
Step 6: The Network Path You Are Not Looking At
If the measurement in Step 1 showed the network at your plan ceiling, everything above has been unnecessary. If it showed the network well below it while other devices on the same connection are fine, the problem is between this machine and the router:
- Wi-Fi versus cable. A 2.4 GHz connection tops out near 8 to 10 MB/s in practice regardless of the plan. Moving to a 5 GHz band or an Ethernet cable is often the entire fix, and the latency side of the same trade is measured in the wired versus wireless comparison.
- A VPN or a proxy. Steam traffic through a VPN is routed to the VPN's exit, then to a content server chosen from that exit's location - which can be a different continent. Disconnect the VPN and re-test before adjusting any Steam setting.
- IPv6 problems. Some ISPs advertise IPv6 with a broken path to Steam's CDN. Disabling IPv6 on the adapter for a test is a two-minute check that occasionally explains a stubborn 2 MB/s ceiling.
- Router QoS or parental controls. A QoS rule that classifies game traffic as low priority, or a device limit, will cap one PC while leaving phones unaffected. Check the router's traffic statistics for this device during a download.
Do the Arithmetic Before You Blame the Client
A 60 GB install is 60,000 MB. At a steady 12.5 MB/s that is 4,800 seconds, or 80 minutes. At 50 MB/s it is 20 minutes. Those two numbers explain most "it has been downloading for two hours" complaints: at a 4 to 6 MB/s effective rate, a modern AAA install genuinely does take three hours, and no setting will change it by more than the underlying limit allows.
- Under 60 minutes for 60 GB - you are above 17 MB/s. Normal for a mid-tier plan, nothing to fix.
- 90 to 180 minutes - 6 to 11 MB/s. Typical of 2.4 GHz Wi-Fi or a 100 Mbps plan; check Step 6.
- Over four hours - below 4 MB/s sustained. That is a throttle, a damaged cable, a hammered drive or a shaped connection, and the steps above will find it.
Steam also reports a download size that differs from the installed size, because it downloads compressed depots and expands them. A 47 GB download can occupy 95 GB on disk. Budget for the larger figure when checking free space, and remember that the compressed figure is what determines the time on the network.
What to Do When Nothing Helps
If the network is at ceiling the whole time and Steam still under-reports, trust Task Manager and let it run - the discrepancy is display lag or unpacking pauses, not lost bandwidth. If throughput stays low across regions, cables and a fresh library location, the limit is almost always an ISP-level cap on Steam's CDN ranges, which some providers apply during peak hours. Testing at 07:00 and again at 20:00 tells you in one day whether you are being shaped, and that is the evidence to take to the provider rather than to Valve.
Two related checks are worth bookmarking: freeing space without losing saves for when the drive is the constraint, and the stuttering checklist for when the download is fine but the game is not.
