Steam Downloading Slowly: What Actually Helps (2026)

Before changing anything, check the units: Steam reports megabytes per second and your provider sells megabits, so a 100 Mbit/s line cannot exceed roughly 12.5 MB/s in that window. If the number really is low after that division, Valve's own troubleshooting names the things that move it — download region, download cache, library folder permissions, the disk, and other software on the same connection — and this guide follows that order. The steps that do not appear anywhere in Valve's documentation, and the ones this guide will not send you to, are traffic "boosters" and rerouting services.

Short answer

Divide by eight first. Steam shows MB/s; your plan is in Mbit/s.
Change the download region — Settings → Downloads → Download Region — and test more than one.
Clear the download cache and repair the library folder; both are two clicks in Steam's own settings.
Exclude Steam library folders from live antivirus scanning and close download managers and P2P clients.
If the drive is pinned at 100% while the download stalls, the bottleneck is unpacking, not the network.

Change the download region, and test more than one

This is the first real lever and Valve puts it in their basic troubleshooting list. Their explanation: the Steam content system is divided into geographical regions, the client detects yours automatically and uses servers there, and sometimes servers in a region are slow, overloaded or suffering a hardware failure.

The path is Steam → Settings → Downloads → Download Region.

One detail from the same page is the one people skip, and it is the difference between this working and not working: Valve says you may need to test several regions other than your own. One swap is not a test.

Pick a region, start the download, watch for a minute, then try the next. Neighbouring regions are the sensible candidates — a server on the other side of the planet has physics working against it.

Clear the download cache and repair the library folder

Two more from Valve's basic list, both fast and both reversible.

Clear the download cache: Steam → Settings → Downloads → Clear Cache. Valve describes this as flushing locally cached configuration data so the client fetches it from Steam servers again. It logs you out; keep your password handy.

Repair the library folder: Steam → Settings → Storage → ... → Repair Folder. The reasoning in Valve's own words is that library folders need to be writable by all users to update properly, and those permissions sometimes break. A folder Steam cannot write into does not produce a clean error message — it produces a download that crawls or dies partway.

If your downloads are not merely slow but throwing messages, the wording in the brackets is the diagnosis, and the Steam error messages guide sorts those by family.

Is the disk the bottleneck?

Often, and it is easy to mistake for a network problem because the symptom is a speed graph that saws up and down.

Steam does not simply save a file; it unpacks and writes the game as it goes. On a mechanical drive, or a drive already busy with something else, that write is the limit, and the network sits idle waiting for it. Valve's own troubleshooting treats the drive as a real suspect: the basic list suggests creating a second library folder on another drive — Steam → Settings → Storage → + — and installing there as a test, and the advanced list includes checking the drive for errors through the drive's Properties → Tools → Error checking.

If the drive is at full utilisation while the download stalls, no network setting will help.

Two more from the advanced section that people dismiss and that Valve lists anyway: run a memory diagnostic with mdsched if downloads fail rather than merely crawl, and disable overclocking — Steam Support states that running hardware outside manufacturer-recommended settings can cause memory and file corruption, which is a good way to keep re-downloading the same files forever.

After a big install finishes with an unclean drive history, a file verification is cheap insurance. Steam warns not to run it during a virus scan or a defrag, and reminds you that a few files failing verification is normal for most games.

Antivirus, firewalls and the programs Valve lists by name

Valve's list of interfering software is unusually specific, and most of it competes for exactly what a download needs — disk and bandwidth:

Category	What Valve says it does	What to do for a test
Antivirus	Hooks deep into disk and network operations	Exclude Steam library folders from live monitoring
P2P and file sharing	Can consume a large portion of your bandwidth	Close it while downloading
FTP and web servers	Bandwidth-intensive by design	Stop the service during the download
Download accelerators and managers	Curate network traffic; Valve says to disable them while using Steam	Turn off
IP filtering and blocking tools	Known to cause issues with Steam and game connections	Disable for the test
VPN software	Can prevent the client reaching the Steam network	Disable for the test
Firewalls	May stop Steam talking to its servers	Add exceptions, or test with it off briefly

Valve also raises a point that is invisible in Task Manager's main view: many applications launch with the computer and never show a window, so a "clean" desktop can still have three of the categories above running.

Is it my connection, or Steam?

Valve's network article answers this in a specific order, and the order matters because the first two steps are free.

Check the Steam server status page before anything else — if the platform is having a wide outage, nothing on your side is broken. Then test the router: the same article notes that wireless and powerline connections cause intermittent failures through interference, and asks you to test with a direct wired connection where possible. Restarting modems and routers is on Valve's advanced list too, with a blunt reason: network hardware gets into a slow or broken state after running for a long time.

Then there is the case where it is genuinely not you. Valve writes that if your Steam connection only misbehaves during certain hours — they give the example of evenings between 5pm and 11pm — it is possible your ISP is shaping or blocking the connection, and the recommendation is to test at other hours and contact the provider. They even publish a short list of named providers found to block Steam traffic.

Ports matter only on managed networks. Steam needs HTTP and HTTPS on ports 80 and 443, plus TCP and UDP 27015–27050, to log in and download. Valve states plainly that these cannot be re-mapped to HTTP or moved to a custom port range, and names university, business and proxied networks as the usual places where they are blocked. On a home router this is not your problem.

What usually goes wrong

Comparing MB/s to Mbit/s. Symptom: "I pay for 300 and Steam gives me 35". Why: those are the same speed. Fix: divide the plan by eight before troubleshooting anything.
One region tested, conclusion drawn. Symptom: switching regions "does nothing". Why: Valve explicitly says several regions may need testing. Fix: try three or four, a minute each.
Antivirus excluded from the wrong folder. Symptom: speed still saws after adding an exception. Why: games often live in a second library on another drive. Fix: exclude every library folder, not just the default one.
A download manager or torrent client left running. Symptom: Steam is slow only in the evening, when the queue is active. Why: Valve names both categories as bandwidth consumers to disable. Fix: close them and retest before blaming the ISP.
Reinstalling Steam as step one. Symptom: an hour spent and the same speed afterwards. Why: reinstalling sits near the bottom of Valve's own list, after region, cache and permissions. Fix: work top-down; the cheap steps are cheap for a reason.

The realistic outcome is one of three sentences: it is the region, it is the disk, or it is the line. Two of those you fix in under five minutes, and the third you at least stop paying for with your evening. While the bar crawls, the random game picker settles what to play from what is already installed, or Doom in the browser fills the gap with no install at all.

Once it lands, CS2 launch options is the sane first stop for configuration. If the freshly downloaded game refuses to start, go to game crashes on startup; if it starts but plays badly, to FPS drops and stutters. Input misbehaving after a long break is its own thing: mouse lag and stutter.

FAQ

Why is my Steam download slower than my internet plan?

Usually because you are comparing two different units. Steam shows megabytes per second, and internet plans are sold in megabits per second, so a 100 Mbit/s line tops out around 12.5 MB/s in the Steam window. Check that first; if the number is still far below that ceiling, start with the download region, which is the setting Valve puts in its own basic troubleshooting list.

Does changing the Steam download region help?

It can, and Valve explains why. The content system is split into geographical regions, the client picks one automatically, and servers in a region can be slow, overloaded or broken. Steam Support suggests temporarily switching to a different region and adds that you may need to test several regions other than your own. It lives in Settings → Downloads → Download Region.

Should I limit my download speed in Steam?

Only to keep the rest of the household usable, not to go faster. What Valve does document as a real cause of slow or broken transfers is other software eating the line: P2P clients, FTP or web server software, and download accelerators, which their own article says should be disabled while using Steam.

Is a slow download a disk problem?

It can be, and Valve's troubleshooting treats it as a candidate rather than an afterthought. Their advanced list includes checking the drive for errors, and their basic list suggests creating a second library folder on another drive and installing there as a test. If the download stalls in bursts while the drive sits at full utilisation, unpacking is your ceiling, not the network.

Do I need to open ports for Steam?

On a normal home router, no. It matters on university, business and proxied networks, which Valve names specifically as places where required ports are blocked. Steam needs HTTP and HTTPS on 80 and 443 plus TCP and UDP 27015–27050 to log in and download, and Valve states these cannot be re-mapped to HTTP or moved to a custom port range.