| Field | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
| No summary available. | ||
Wget commands turn a download job into a repeatable text recipe. That matters when a file is large, a crawl needs boundaries, or a transfer has to resume after an interruption without guesswork. This generator builds that recipe for HTTP, HTTPS, and FTP targets and renders it for Bash/Zsh, PowerShell, or Windows CMD.
A hand-written command is easy to get mostly right while still missing the one flag that changes the outcome: resume behavior, timestamp checks, crawl depth, output placement, or a header the server expects. Here you describe the job in form fields, then inspect a finished Command, an Options summary, and a JSON snapshot before you copy anything.
One common use case is a release archive that may need to restart after a weak connection drops. Another is a documentation copy that should stay inside one branch of a site instead of walking upward into parent folders. The same form can also build API-style fetches with exact header values.
A clean preview still needs a privacy check. The command is assembled in your browser, but the current field values are also mirrored into the page URL so the state can be shared. If you type a real password, bearer token, cookie, or secret header, that value can end up in the address bar, browser history, and any copied link.
Treat the generated line as a starting point for an actual transfer, not as proof that the remote server will accept your headers, credentials, or crawl pattern. Build with test URLs and placeholder secrets first, then replace them only at the point of execution.
Start with Preset even if you plan to edit everything afterward. Quick download is the clean first pass for one file, Resume large file adds the restart and retry behavior people usually forget, Mirror static site turns on recursive retrieval and link conversion, API fetch starts with typical headers, and FTP transfer switches the example URL and credential mode.
If all you have is an existing line from a shell history or README, paste it into Import existing wget command first. The parser rebuilds supported flags, headers, auth fields, and shell preference much faster than manual re-entry. It is still a best-effort round trip, so compare the imported Flags row to the original line before you trust it.
Recursive download with Recursive depth. Mirror mode is meant for broad site copies, and the tool warns when you pair it with a custom depth.Random wait only after Wait between files is greater than zero. Use Retry wait only when Retry attempts is also greater than zero.Authentication and Extra headers affect the shareable page state, and imported secrets become risky once they populate those fields.Shell, re-read the rendered Command. Bash/Zsh, PowerShell, and CMD do not quote paths or continuation lines the same way.Before copying, clear every item in Errors, then read each line in Warnings and confirm that URL, Recursive, Authentication, and Flags still match the job you meant to run.
A wget invocation is a sequence of tokens: the program name, a set of option flags, any values attached to those flags, and one final target URL. This tool models that sequence directly. It validates the address, resolves headers and authentication, chooses either long or short flag variants, and then quotes each value according to the selected shell.
The package accepts only absolute HTTP, HTTPS, and FTP URLs. Header lines are parsed from Name: value text, User-Agent and Referer can be set separately, and authentication adds --user plus --password when you supply them. For short-flag output, only eligible single-letter switches are combined.
Rendering changes by shell after the token list is built. Bash/Zsh multi-line output uses backslashes, PowerShell uses backticks, and CMD stays single-line. Path handling is shell-aware too: ~/... becomes $HOME for Bash/Zsh and PowerShell, while CMD maps it to %USERPROFILE%.
URL and reject missing or non-HTTP/HTTPS/FTP schemes.User-Agent, Referer, output filename, directory prefix, and any structured headers.Continue partial, Timestamping, No clobber, and Content disposition.Recursive download, Mirror mode, Recursive depth, waits, retries, timeouts, and rate limits.The option labels follow GNU Wget terminology rather than inventing a new vocabulary. In the manual, --mirror is described as a shorthand that enables recursive retrieval, timestamping, infinite recursion depth, and removal of FTP directory listings. The same manual also notes that --content-disposition is experimental, that --continue is for resuming partial transfers, and that --no-check-certificate disables certificate verification.
| Input or Result | Format | What It Controls or Shows | Why It Matters |
|---|---|---|---|
URL |
Absolute HTTP, HTTPS, or FTP address | Final target token in the command | If this is wrong, every other flag is attached to the wrong request. |
Output file and Download directory |
Optional text paths | Saved name and directory prefix | They decide whether the file keeps the remote name or lands in a controlled location. |
Extra headers, User-Agent, Referer |
Name: value lines and presets |
Request metadata sent to the server | Header spelling often decides whether an API or protected endpoint responds correctly. |
Authentication |
None, HTTP Basic, or FTP credentials | Adds --user and optional --password |
A missing username blocks generation, and embedded secrets can leak through history or shared URLs. |
Command |
Quoted text command | The runnable output | This is the string your shell will evaluate, so it deserves a final read in the destination shell. |
Options |
Summary table | Human-readable rows such as Flags, Retries, and Recursive |
It is the fastest place to spot a mismatch before you copy. |
JSON |
Structured snapshot | Inputs plus derived values | Useful when you want to compare runs or feed the result into another tool without re-parsing the command. |
Warnings and Errors |
Message lists | Ignored settings, unsafe combinations, or blocking problems | They are the difference between a polished preview and a command you should still stop and fix. |
| Field | Accepted Pattern or Boundary | Tool Behavior | Interpretation |
|---|---|---|---|
URL |
Must parse as absolute HTTP, HTTPS, or FTP | Invalid or unsupported schemes add an Error and suppress output |
No command is shown until the target address is structurally valid. |
Custom agent |
Non-empty when User-Agent is set to custom |
Blank custom values raise a Warning |
The command falls back to the default agent unless you provide a real string. |
Extra headers |
Each non-empty line needs one colon | Malformed lines raise Warnings and are skipped |
A header missing from the count usually means the line never became a flag. |
Random wait |
Wait between files > 0 |
Without a positive wait, the setting produces a Warning |
Jitter only makes sense when there is a base delay to vary. |
Retry attempts and Retry wait |
Retry attempts >= 0, Retry wait >= 0 |
Negative values are Errors; wait without tries is only a Warning |
A retry delay is descriptive only when the command will actually retry. |
Recursive depth |
Recursive download or Mirror mode must be active |
Depth without recursion raises a Warning |
A depth value on its own does not make the command recursive. |
Authentication |
Username required when mode is not None |
Missing usernames are Errors; empty passwords trigger a prompt warning |
The tool refuses to guess who should authenticate. |
Limit rate |
Values such as 500k, 2m, or plain bytes |
Unusual formats raise a Warning but are still emitted |
The tool lets you keep non-standard text, but it asks you to double-check it first. |
Generation happens in the browser, but privacy is not automatic. Current field values are synchronized into the page URL, so local command assembly and share-state exposure are both true at the same time.
Use the generator in two passes: build the intent first, then verify the output surfaces before you copy.
Preset, then set Shell and Multi-line. If you already have a command, use Import existing wget command instead of retyping it.URL, then decide whether to fill Output file or Download directory. The summary box should update with the host, scheme, and flag count as soon as the address is valid.User-Agent, Referer, and Extra headers. If a header line is malformed, the Warnings list will tell you which line failed.Advanced for transfer behavior such as Continue partial, Timestamping, Recursive download, waits, retries, and rate limiting. If Authentication is enabled without Username, the tool will stop with an Error until you fix it or set the mode back to None.Command tab, then switch to Options. Compare Flags, Recursive, Retries, and Authentication against the job you want to run.JSON tab only if you need a structured snapshot, then copy or download the command after every Error is gone and each Warning has been resolved or consciously accepted.The most important outputs are the blocking and summary surfaces underneath the badges. Errors decide whether the command is safe to generate at all, while Warnings tell you a setting is unusual, ignored, incomplete, or potentially unsafe in context.
Command only when Errors is empty.Flags row to confirm behavior, especially after importing or changing flag style.Recursive, Retries, and Limit rate to sanity-check crawl scope and pacing.Authentication as a reminder that credentials are present, not as proof they are correct for the server.A polished command preview does not verify that the remote host accepts your headers, that the certificate should be bypassed, or that the downloaded file is the right one. Run the line in a safe test context first, then confirm the transfer result with server responses and the final artifact itself.
Pick Resume large file, keep Shell on Bash/Zsh, set URL to https://downloads.example.org/releases/app.tar.gz, and leave the remote filename unchanged. The generated Command includes resume and retry behavior, Resume shows Enabled, and Retries shows the preset summary.
That is a sensible pattern for a multi-gigabyte artifact on an unreliable link. Verify the finished file against the publisher's checksum after the transfer completes.
Select Mirror static site, set URL to https://docs.example.org/guide/, and then type 2 into Recursive depth. The Recursive row shows Mirror, but Warnings tells you that mirror mode ignores the custom depth.
If you need a shallow crawl, turn off Mirror mode, enable Recursive download, and keep the depth limit there instead.
Choose API fetch, change the first header line to Authorization Bearer TOKEN, and set Retry wait to 10 while Retry attempts stays at 0. The Warnings list reports the missing colon in the header line and explains that retry wait only applies when retries are greater than zero, while the Headers row in Options no longer counts the broken header.
Fix the line to Authorization: Bearer TOKEN, then either add a positive retry count or clear the delay. Once both warnings disappear, the Flags row is a much better representation of what the shell will actually send.
Avoid that when possible. The tool assembles commands locally, but it also syncs current fields into the page URL. Real secrets can therefore leak through the address bar, browser history, screenshots, or shared links.
Random wait needs a positive Wait between files, and Retry wait only makes sense when Retry attempts is greater than zero. When those prerequisites are missing, the tool keeps the main output but explains the mismatch in Warnings.
The reverse parser rebuilds the switches this package explicitly supports. Unsupported wget options, shell-specific constructs, or ambiguous quoting can be skipped. After import, compare the original line against the generated Flags row and Command preview instead of assuming a perfect round trip.