What is wget Non-Verbose Mode vs Quiet Mode?

When automating file downloads or scraping websites using the wget command-line utility, managing terminal output is crucial for keeping scripts clean and logs readable. This article explains the functionality of wget’s non-verbose mode (-nv or --non-verbose) and details how it differs from the completely silent quiet mode (-q or --quiet). By understanding these two logging levels, you can choose the right balance between suppressing unnecessary download progress bars and retaining critical error messages for troubleshooting.

Understanding Non-Verbose Mode in wget

By default, wget is highly verbose. It displays a real-time progress bar, download speed, ETA, connection handshakes, and HTTP response headers. While this is helpful for manual downloads, it clutters log files during automation.

The non-verbose mode, invoked with the -nv or --non-verbose flag, significantly cuts down this output. It turns off the live progress bar and basic connection details, but it does not make the command completely silent. Instead, it reduces the output to a simple, one-line summary for each completed download, while still reporting critical errors.

Example of Non-Verbose Output: 2026-06-06 12:00:00 URL:https://example.com/file.zip [1048576/1048576] -> "file.zip" [1]

Understanding Quiet Mode in wget

The quiet mode, invoked with the -q or --quiet flag, takes output suppression to the absolute maximum. When you use this flag, wget becomes completely silent. It will not print progress bars, completion summaries, or even critical error messages (such as “404 Not Found” or “Connection Refused”) to the standard output.

Quiet mode is ideal for background cron jobs where you only care about the exit status of the command and want to avoid generating any terminal output whatsoever.

Key Differences: Non-Verbose vs. Quiet Mode

The fundamental difference between the two modes lies in error reporting and basic confirmation.

Output Comparison

Use Case Selection

Feature / Behavior Non-Verbose Mode (-nv) Quiet Mode (-q)
Live Progress Bar Disabled Disabled
Success Confirmation Enabled (Single-line summary) Disabled
Error Logging (e.g., 404, 500) Enabled Disabled
Best Used For Automated scripts where you still need to log errors and verify successes. Background cron jobs where any output triggers unwanted system emails.

Choosing between these two modes depends entirely on your logging requirements. If you need to review your logs later to see if a file successfully downloaded or why it failed, non-verbose mode is the correct choice. If you want total silence and plan to rely strictly on the script’s exit codes for error handling, quiet mode is the better option.