How to run wget downloads in the background

Long-running downloads should not depend on an interactive terminal staying open. Running wget in the background lets large artifacts keep transferring after the prompt returns, which is useful for backup pulls, mirror jobs, and other maintenance tasks that can take several minutes or longer.

GNU wget detaches with --background (-b) and continues the transfer after startup. When you also set --output-file and --output-document, the detached job has a predictable log path and destination filename instead of falling back to the default wget-log output file.

Detached does not mean self-validating. A background transfer can still exhaust disk, hit quota limits, or leave a partial file after a network drop, so keep the job in a dedicated directory, retain its log, and verify the final artifact before another process uses it.

1. Create a dedicated working directory for the detached transfer and its log file.

   $ mkdir -p ~/downloads/wget-background
   $ cd ~/downloads/wget-background

   Keeping the payload and log together makes it easier to review the run later or remove it cleanly if the transfer fails.

2. Start the download in background mode with an explicit output filename and log path.

   $ wget --background --continue --output-document=sample-2m.bin --output-file=wget-background.log https://downloads.example.net/files/sample-2m.bin
   Continuing in background, pid 14193.

   If you omit --output-file, current wget builds write the detached log to wget-log in the working directory.

3. Confirm that the process is still running under the reported PID.

   $ ps -p 14193 -o pid=,command=
   14193 wget --background --continue --output-document=sample-2m.bin --output-file=wget-background.log https://downloads.example.net/files/sample-2m.bin

   Check the exact command line so you do not confuse this transfer with another background wget job on the same host.

4. Monitor the log while the transfer is active instead of attaching to the process directly.

   $ tail -f wget-background.log
      150K .......... .......... .......... .......... ..........  9%  195K 9s
      200K .......... .......... .......... .......... .......... 12% 1000K 7s
      250K ......

   Progress lines in the log are easier to review after the fact than a shell job that has already detached.

   Related: How to log wget output to a file

5. Verify that the process exited and the saved file reached the expected size.

   $ ls -lh sample-2m.bin
   -rw-r--r-- 1 user user 2.0M Mar 27 06:58 sample-2m.bin
   
   $ tail -n 1 wget-background.log
   2026-03-27 06:58:16 (250 KB/s) - 'sample-2m.bin' saved [2097152/2097152]

   No active process plus a final saved line in the log is the clean success state for a detached transfer.