Steam Slow Download Speed: Find the Real Bottleneck

By LK Wood IV · Published 2026-09-18 · Updated 2026-09-18 · ~10 min read · St. Louis County, MO

One retailer link below is an affiliate link; if you buy through it TechFuel HQ may earn a small commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Commissions never influence what gets recommended — see our disclosure.

A slow Steam download is two different problems sharing one progress bar, and almost every guide treats it as one. What you get instead is a list of eight to thirteen client toggles in a row, tried in hope, with nothing in it that tells you which of the two problems you are looking at. On September 14, 2026 I worked through Bing’s top ten for this query and read the four how-to pages in it that would load. Their fix lists ran from eight items to thirteen. Not one of them opens the file where Steam writes down exactly what it is about to do before it does it.

That file settles the question in about ten seconds. So it goes near the top here.

Which problem you have

Step 1. Settle the units before you change anything

It is the first answer the most recent of the threads below reached for, and it costs nothing to check.

Internet connections are sold in bits per second. Steam reports downloads in bytes per second. A byte is eight bits, so one transfer produces two numbers that differ by a factor of eight. Valve publishes a conversion table for exactly this confusion, tucked inside a collapsed block on its slow-downloads article headed “Example download speed conversions”, and the bottom row of it lists a 50 megabits/second connection against 6.25 MB/S.

Watch it play out. In a Steam Community thread opened on September 3, 2026, the poster set a 74.15 Mb/s speed test against what they wrote down as a 9.1 Mbps Steam download, and asked why the thing had suddenly broken overnight. The first reply did the arithmetic. Steam’s readout is in bytes, so that 9.1 was 9.1 MB/s, and 74 Mb/s divided by eight comes to about 9.25 MB/s. Two numbers, two units, one speed. Nothing was broken.

To make the two numbers comparable, open Steam, Settings, Downloads and tick Display download rates in bits per second. Valve also points out that the speed shown in your system tray is your local network link rate rather than your internet speed, which is why a “1 Gbps” adapter tooltip proves nothing about your actual connection to the outside world.

Multiply your Steam figure by eight. If the result lands anywhere near your speed test, your download is already running as fast as the line you pay for, and every remaining step on this page is going to tell you the same thing in more words. You are done here.

Step 2. Read the byte plan

Here is the part no ranking page does.

Before Steam starts an update it works out three totals and writes them down. How many bytes it must download, how many it will reuse from files you already have, and how many it will stage onto your drive. Those totals live in two places. You can open both right now.

The easier one is the game’s manifest. Go to steamapps in your Steam library folder and open appmanifest_<appid>.acf in Notepad. Two lines matter:

"BytesToDownload"		"7305760"
"BytesToStage"		"2217366028"

That is the real file on my desktop as I write this, for Total War: WARHAMMER III. Steam needs 7.31 MB off the internet and is going to write 2.22 GB to my SSD. The download is a rounding error. The drive does everything.

The fuller version is logs\content_log.txt in your Steam folder. Search it for update started and you get a line per update:

[2026-09-02 15:12:44] AppID 1142710 update started : download 1220164112/42976779808,
store 0/0, reuse 0/0, delta 0/0, stage 2008143587/81633734737

The second number in each pair is the total. That update had 42.98 GB to download and 81.63 GB to stage.

I parsed all 46 update records in my log, covering September 2 to 16, 2026. The pattern is consistent and it is not subtle:

A fresh download stages about what it downloads. A patch to a large packed game stages hundreds of times what it downloads. Seventeen WARHAMMER III patch records landed in that fortnight, and every one of them pulled between 1.70 MB and 18.27 MB off the internet while writing between 2.21 GB and 4.73 GB onto the drive.

So when a 2 MB patch takes a minute, the byte plan has already explained the wait.

Step 3. When the drive is the wait

Valve documents why this happens, in the developer documentation rather than the support pages. SteamPipe splits every file into roughly one-megabyte chunks so it can send only the changed ones. Packed files break that. Valve’s guidance to developers spells out the consequence: to update a 25 GB pack file, SteamPipe always builds a new 25 GB file, and if the update only requires 10 bytes of changes it still copies almost the entire 25 GB from the old file to the new one. The documentation then says, plainly, that depending on the client storage hardware this can be a very slow process.

That is the whole mechanism. The reuse figure in the log is Steam reading your existing install back off the drive to build the replacement, which is why my 1.70 MB patch shows 1.97 GB of reuse sitting next to it in the same line. The sum will not quite close. Stage runs about 240 MB above download plus reuse on that patch, Valve does not document what else it counts, so read stage as the size of the write job.

Valve has also acknowledged the confusion in the client. The September 9, 2021 client update rebuilt the Downloads page, and the release notes say that previously the progress bar would only display the downloading content progress but not the disk allocation process, which would make an update appear completed when it was not.

What to do about it:

• Leave it alone and let it finish. On my Samsung 970 EVO Plus most of those multi-gigabyte staging passes took two to seven seconds. The slowest took 53 seconds, and that was a patch that downloaded 1.70 MB and wrote 2.21 GB.
• Move the library if it lives on a hard drive. Every patch means reading a couple of gigabytes off that drive and writing them straight back, and Valve names the client’s storage hardware as the thing that decides how long that takes. This is the one place on this page where the fix is hardware rather than a setting.
• Give the drive headroom. Valve’s documentation says Steam builds the new file alongside the old one and only then commits, so a patch needs room for both copies at once. How a nearly full drive behaves beyond that is my inference, not something Valve states.

My measurements come off an NVMe drive, so what I can show you is the cost on fast storage. For the slow case the authority is Valve’s own documentation, quoted above. If your games sit on a spinning disk and every small patch turns into a long wait, the byte plan in Step 2 will tell you whether staging is where that time goes.

Once the drive is fast enough, Steam will move the library for you. Settings, Storage, pick the new drive, then move the games across rather than reinstalling them.

Step 4. Read the per-host rates

If the byte plan says stage and download are close, then the bytes really are coming down the wire and you have a genuine network problem, which is the one case where the region and connection advice on every other page is pointed at the right thing. The same log tells you where it sits.

Search content_log.txt for stats: while an update runs. Steam logs one line per content server it is pulling from, plus an aggregate line:

[2026-09-02 15:17:11] stats: (SteamCache, 273) cache8-ord1.steamcontent.com:
2943899992 Bytes, 193 sec (121.74 Mbps). 5301 Hits / 439 Misses (92 %, 93 % bytes)
[2026-09-02 15:17:11] stats: (Invalid, 0) : 17440492742 Bytes, 291 sec (480.29 Mbps)

On my desktop that big update ran across ten Chicago hosts at once. Each one sat between 71.45 and 121.74 Mbps in the sample above, and across the whole fortnight no single host ever went above 185.95 Mbps. The two aggregate lines for that update read 480.29 and 591.67 Mbps. The minute-by-minute samples peaked at 850.26 Mbps, which is 85 percent of my gigabit port. Steam also logged how many servers it had been handed, between 30 and 35 each time.

That is what a healthy download looks like on my box. No single host is fast. The client makes up the difference by using many of them at once.

Now the useful part, and the comparison is against your own line rate rather than my numbers. If your per-host lines each read a few Mbps while your connection is rated far higher, the route to that region is your problem and Step 5 is the fix. If each host is quick but Steam has only opened two or three of them, the client is not spreading the load. If the hosts are busy and the aggregate is close to what your line can carry, go back to Step 2. The wait is on the drive.

The same lines appear on Linux. An Arch Linux forum post from March 2025 shows a user’s log with five Frankfurt hosts at 11.76 to 13.97 Mbps and a 64.25 Mbps aggregate, which is the same diagnostic on a much slower route.

Step 5. Change the download region, with a reason

Valve’s position is that Steam picks a content server based on where you are. If downloads run slower than expected, its article tells you to check the download region under Steam, Settings, Downloads, then to try various regions near your location until one performs better.

The community evidence says this works often enough to try and not reliably enough to trust. All of the following are from threads I opened:

• On the night of October 10, 2024, several people reported sudden slow downloads within hours of each other. One switched away from US servers to Ukraine or London and got expected speeds back. Another thanked the thread for the region tip and said it helped. A third tried Denver and Phoenix and still faced a two-day estimate for Baldur’s Gate.
• A reply posted on February 7, 2023 to that same 2021 thread came from someone in the Netherlands who switched to Germany, Hamburg. They reported going from 5 MB/s to a steady 45 MB/s after a decade of slow downloads.
• A different 2021 poster was pinned at 1.4 MB/s for over a month. They had already worked through multiple regions, several drives, three filesystems, both wired and wireless, and even a different house. Region changes did nothing for them.

Several strangers going slow on the same evening points at a region or a route. One machine slow for a month while everything else on the network is fine does not. That person belongs in Step 6.

Step 6. Confirm the link you think you have

A gigabit connection that negotiated at 100 Mbps caps Steam at roughly 12 MB/s, and Steam has no readout that would tell you the link is the reason. The client just looks slow.

In the Arch Linux thread above, the first reply was exactly this. That user had gigabit service. They went and read the link rate, and found their network card had negotiated a 100 connection instead of a 1000. On Windows, open PowerShell and run:

Get-NetAdapter | Select-Object Name, InterfaceDescription, LinkSpeed

Mine reports Intel(R) Ethernet Controller (3) I225-V at 1 Gbps. If yours says 100 Mbps on a gigabit line, replace the cable before anything else and reseat both ends.

Valve’s network troubleshooting article makes the related point about wireless. It says wireless and powerline connections can cause intermittent failures due to interference and recommends testing Steam over a direct wired connection. That matters more than it sounds. In the December 2024 thread where a poster spent the afternoon toggling disk write caching, they mentioned in passing that the PC was on Wi-Fi, and nobody went back to it.

Valve’s article also notes that a connection with problems only at certain hours, its example being evenings between 5pm and 11pm, may be shaped by the provider.

Step 7. The client settings worth checking, in one pass

These are the toggles the other guides lead with. They are worth a minute each, once the two diagnostics above have told you which half of the problem you are in.

Limit Download Speed. Steam, Settings, Downloads. Confirm it is off. Valve notes that the rates listed there are in kilobytes and megabytes a second while most connections are rated in bits, which is a reliable way to set a limit eight times tighter than you meant to.

Security software and VPNs. Valve keeps a list. Anti-virus hooks very deep into user systems and can affect disk and network operations. VPN software has the potential of preventing the Steam client from reaching the Steam network. Valve names download accelerators specifically and says they should be disabled while using Steam, and says peer-to-peer programs have the potential to consume a large portion of your bandwidth or other system resources if not properly configured. Valve’s slow-download article adds that some third-party applications can cause Steam to use incorrect content servers, which is the mechanism behind “only Steam is slow”. Disable one temporarily, restart Steam, retest, then turn it back on.

Clear Download Cache. Steam, Settings, Downloads, at the bottom. Valve says it can solve problems with games that will not download or start, that it will not affect your currently installed games, and that you will need to log in again afterwards. It fixes downloads that are stuck. It will not make a working one faster.

Steam server status. Valve’s network article puts checking its own status page first, ahead of every local step, on the reasoning that a system-wide outage explains the symptom and nothing you change at home will help until it clears. It takes one look.

What not to do

Do not edit steam_dev.cfg to disable HTTP/2 on Windows. The three config lines circulating for this come from ValveSoftware’s Linux issue #10248, opened in November 2023 and closed as completed on October 15, 2024. The header on that issue now tells readers the problem is solved and to use a newer distribution. The HTTP/2 variable it names, @nClientDownloadEnableHTTP2PlatformLinux, is Linux-scoped in its own name; the other two are undocumented client internals with no platform in them at all. I found no Valve documentation for any of the three. You would be setting undocumented client variables against a bug that was fixed on a different platform.

Do not toggle disk write caching on a guess. The advice circulating for this points in both directions at once. In a January 2022 thread about disk usage swinging between 100 MB/s and zero, one reply said their own write caching had been switched off and that turning it back on made a huge difference. In December 2024, a poster was told the opposite, turned write caching off on a Kioxia Exceria G2, and reported that nothing had really changed, after which the person advising them concluded the storage angle was a dead end for that machine. The byte plan in Step 2 answers the underlying question without touching a disk policy at all.

Do not reinstall Steam for a speed problem. It is a large action for a symptom that has cheap diagnostics, and it carries a real risk if you do it the wrong way. Valve’s update and installation article says to reinstall Steam to the same location where it is already installed, that installing into the same location will preserve all installed games, and then warns in capitals that uninstalling Steam will delete all game content. The Steam not opening guide covers the safe route if you ever do need it.

Do not read a nearly idle Task Manager as proof. Two of the posters above opened with it. The one who started the October 2024 thread wrote that most of the performance metrics in Task Manager were barely even moving, and the 2021 poster listed never going above 5 percent on CPU, memory or disk. A staging pass that reads and rewrites 2 GB on an NVMe drive finishes in seconds. A one-second glance at Task Manager will miss it completely.

The nuclear option and what it costs

If the byte plan says network, the per-host rates are poor across several regions, the adapter is at full speed, and security software is ruled out, the remaining move is to take your own machine out of the picture. Put the PC on a phone hotspot and start a download.

That costs mobile data and about five minutes. What it buys is a clean split. If Steam is fast on the hotspot, then the problem lives in your router, your local network or the route your provider takes to Steam’s servers, and no setting inside the Steam client is going to fix any of those three. If it is equally slow on both, the problem is on the PC. Go back to Step 6 and Step 7 knowing that.

The 2021 poster who was stuck at 1.4 MB/s had effectively run this test by trying a different house entirely. That is the point at which to stop changing Steam settings.

What I checked on my own machine

Windows 11 Home, build 26200.9457, on September 18, 2026. Steam installed to C:\Program Files (x86)\Steam, library on a Samsung SSD 970 EVO Plus 1TB NVMe, networking through an Intel I225-V at 1 Gbps. The steam.exe file version reads 10.96.30.42, which is the file version on disk rather than the build number the About dialog shows.

I read content_log.txt and the appmanifest_*.acf files with Steam and every game closed, parsed all 46 update started records between September 2 and September 16, and timed each one against its matching scheduler finished line. I started no download and changed no Steam setting for this page, so every figure here comes from updates that happened on their own.

The gap I cannot close from this box is the slow-storage case. My staging passes finish in seconds because the drive is fast. The claim that a slow drive turns those same passes into a long wait rests on Valve’s SteamPipe documentation and on the community reports above rather than on any measurement of mine.

Sources

• Steam Support, Slow Downloads and Connection to Content Servers: https://help.steampowered.com/en/faqs/view/5AC5-8056-E88F-F3FF
• Steam Support, Setting Client Rates (Limit Download Speed) in Steam: https://help.steampowered.com/en/faqs/view/163C-7C89-406E-2F63
• Steam Support, Programs Which May Interfere with Steam: https://help.steampowered.com/en/faqs/view/1F39-DCB4-FF28-5748
• Steam Support, Troubleshooting Network Connectivity: https://help.steampowered.com/en/faqs/view/669A-2F68-D1D1-A5EC
• Steam Support, Clear download cache: https://help.steampowered.com/en/faqs/view/6AD7-820D-8BE5-E51F
• Steam Support, Update & Installation Issues: https://help.steampowered.com/en/faqs/view/21F5-8D5D-0141-7A5E
• Steamworks Documentation, SteamPipe content system: https://partner.steamgames.com/doc/sdk/uploading
• Steam Client Update Released, September 9, 2021: https://store.steampowered.com/oldnews/88497
• Steam Community, Speedtest 74.15 Mbp/s Steam download 9.1 Mbp/s (September 2026): https://steamcommunity.com/discussions/forum/7/590688498095390453/
• Steam Community, Steam downloading EXTREMELY slow (October 2024): https://steamcommunity.com/discussions/forum/1/7413579240795244505/
• Steam Community, Steam Slow Downloads (March 2021): https://steamcommunity.com/discussions/forum/7/3084376689320298303/
• Steam Community, Downloads from Steam are abysmally slow (December 2024): https://steamcommunity.com/discussions/forum/1/591756872987536923/
• Steam Community, Disk usage going up and down (January 2022): https://steamcommunity.com/discussions/forum/1/3203748716332508733/
• Steam Community, Steam Download rate stuck at 0 bytes/s (September 2013): https://steamcommunity.com/discussions/forum/1/864979008818608129/
• Arch Linux BBS, Downloading steam games too slow (March 2025): https://bbs.archlinux.org/viewtopic.php?id=304173
• ValveSoftware/steam-for-linux issue #10248, Http2 makes downloading speed slow: https://github.com/ValveSoftware/steam-for-linux/issues/10248