A Steam download showing 0 B/s does not always mean your internet connection has stopped. An update can finish receiving a small patch and then spend time rebuilding much larger files on your drive. First check whether Steam says it is downloading, patching, installing or verifying, and whether its disk activity is still changing.
That distinction matters because restarting a router cannot make a local file operation finish faster. It can also interrupt a healthy download. Use the checks below to decide which part deserves attention before cancelling the update or changing network settings.
Read the update state before the speed number
Open Steam’s Downloads view and note the active game’s state, downloaded amount and remaining work. Labels and layout can change between client versions. Look for separate network and disk activity rather than treating the biggest number as a complete progress report.
Valve explains that SteamPipe downloads compressed chunks, expands them on the client and reuses unchanged chunks during an update. For some packed game files, it constructs a replacement alongside the old file. A small download can therefore lead to substantial local reads and writes. This is documented in Valve’s explanation of SteamPipe patching; it does not mean every game uses the same update process.
| Observation | Useful next check |
|---|---|
| Network is quiet; disk activity and patch progress change | Watch the local update stage before investigating the router. |
| Steam says downloading; neither progress nor network activity changes | Check the queue, download settings and whether other internet services work. |
| Several downloads and websites fail on different devices | Investigate the shared connection separately. |
| Only one game’s update repeatedly fails with an error | Record the exact error and investigate that game’s installation or update. |
Make a short progress record
- Capture the starting state. Note the game, Steam’s state label, received amount, free space on the installation drive and any error. Avoid publishing account details in a screenshot.
- Observe an interval. Leave the queue visible for a few minutes. Note whether bytes, file progress or disk activity change. The interval is an observation window, not a universal deadline for declaring an update stuck.
- Check competing local work. A second game installation, file copy or backup can use the same storage device. Pause only work you can safely pause, then compare the same update stage.
- Separate a paused queue from a stalled transfer. Check for a scheduled-download window, a manual pause or another item being processed first. A configured limit is different from a fault.
- Record the result. “Network 0 B/s while patch progress advanced” is more useful than “Steam is slow.” If nothing changes, retain that observation and continue with the appropriate branch below.
Do not repeatedly cancel and restart a patch just to force the network graph upward. More network traffic would not necessarily mean more useful progress. Likewise, a busy drive is evidence of activity, not a guarantee that the installation is healthy.
If the download stage is the part that stalls
Check Steam’s Downloads settings for a bandwidth limit and the selected download region. Valve recommends checking the region and, where appropriate, trying a nearby region when content-server transfers are slow. Its slow-download guidance also explains the difference between bits and bytes. Do not cycle through many regions while a local patching operation is the bottleneck.
Next, test whether the problem extends beyond Steam. Pause the game transfer before running a separate browser internet speed test, and record the device, connection type and time. The browser test contacts its own measurement service, so a good result cannot certify the route to Steam’s content server. It can still provide a useful comparison for the connection’s available capacity.
If the browser test is also unexpectedly poor, compare another device or a wired connection under similar conditions. The Slow Internet Troubleshooter helps choose a focused next check. If the browser is healthy and only Steam transfers stall, preserve the Steam-specific evidence rather than assuming your broadband plan is too slow.
A small patch can mean a large local job
Consider an illustrative update with a small received patch and a much larger installed archive. The archive may still need to be read and rebuilt even after the required network chunks arrive. This is a conceptual example of the behavior Valve documents, not a benchmark performed on a particular game or storage device.
A download-time calculation estimates the transfer portion from file size and rate. It cannot predict how long a game’s decompression, verification or patch construction will take. Adding faster internet will not shorten every stage by the same proportion.
Know when to collect an error instead of more speed tests
If Steam reports a disk-write, missing-file or other installation error, copy its wording and check the relevant Steam or game support instructions. Retain the installation drive, available space and whether other games update successfully. Do not delete game folders, disable security tools broadly or reset the router as a default response to an unidentified error.
For an issue that repeats without a clear error, provide support with the game, client version, state label, time, connection method and your progress record. Explain whether another download worked and whether local activity continued. Our guide to speed tests versus actual downloads covers normal rate differences; this record addresses the different question of where an update stops advancing.