How to throttle download speed with wget

Large wget transfers can fill a shared connection and make SSH sessions, browser traffic, or calls feel slow. A rate cap keeps the download moving while leaving predictable headroom for everything else on the same link.

GNU wget throttles transfer speed with --limit-rate. Current GNU documentation says the value is in bytes per second, accepts k and m suffixes, and still accepts decimals such as 2.5m for finer tuning.

Wget enforces the cap by sleeping after fast network reads, so the average rate settles near the requested value during a longer transfer instead of staying exact on every progress line. Small files can finish before the limiter stabilizes, and each parallel wget process applies its own ceiling independently.

Related: How to show download progress in wget
Related: How to add wait and random delays between wget requests
Related: How to limit total download size with wget

Steps to throttle download speed with wget:

  1. Run wget with --limit-rate and watch the completed transfer line settle near the chosen ceiling. 
    $ wget --limit-rate=300k https://downloads.example.net/release-4m.bin -O release-300k.bin
Length: 4194304 (4.0M) [application/octet-stream]
Saving to: 'release-300k.bin'
##### snipped #####
2026-04-22 07:25:00 (300 KB/s) - 'release-300k.bin' saved [4194304/4194304]

    Use a file large enough to run for several seconds, otherwise the final average can finish before the limiter has time to settle.

  2. Raise or lower the same cap and repeat against the same file until the background transfer stops crowding out other traffic. 
    $ wget --limit-rate=1m https://downloads.example.net/release-4m.bin -O release-1m.bin
##### snipped #####
2026-04-22 07:25:21 (1022 KB/s) - 'release-1m.bin' saved [4194304/4194304]

    Decimal values such as --limit-rate=2.5m remain valid when 300k or 1m is too coarse for the link.

  3. Set a default cap in /$HOME/.wgetrc when the same account should reuse it automatically. 
    ~/.wgetrc
limit_rate = 300k

    Each command-line --limit-rate value overrides the startup-file default. Related: How to configure default options in ~/.wgetrc

  4. Check the finished files before reusing the same command in another job or script. 
    $ ls -lh release-300k.bin release-1m.bin
-rw-r--r--  1 user user 4.0M Apr 22 07:25 release-300k.bin
-rw-r--r--  1 user user 4.0M Apr 22 07:25 release-1m.bin

    --limit-rate controls transfer speed only; it does not verify checksums or file integrity after the download finishes.