Shell Argument Literal Builder

How to use Shell Argument Literal Builder

Serialize an authored executable and string argument list into literal POSIX sh or PowerShell command source without running it. Prepare a command for review when spaces, empty values, quotes or dollar signs must remain literal argument data. Start from a JSON argument vector rather than asking an ambiguous pasted command to reveal its intent. The tool creates an actual text artifact and preserves your supplied strings; it never calls a shell, executable, remote host or interpreter.

1. Provide optional utf-8 argument model, literal command and argument model.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• Strict UTF-8 JSON up to 50,000 bytes, with exactly command and args members, unique safe object keys, at most 10,000 values and 40 levels. A file takes precedence over pasted text. Command is a nonblank single-line string up to 1,000 bytes; 0–200 argument strings may be empty and contain tab, CR or LF, each up to 4,000 bytes. Combined literal data is at most 20,000 UTF-8 bytes. NUL, other C0 controls, DEL and malformed Unicode are refused.
• POSIX mode single-quotes every complete word. An embedded ASCII apostrophe becomes adjacent closed/open quoted segments with a literal apostrophe between them. No unquoted parameter, command, glob, arithmetic or tilde expansion is generated. Newlines inside an argument remain inside its quoted literal, not a new command.
• PowerShell mode emits a call operator followed by one separately quoted positional literal for the command and each supplied argument; an empty argument vector adds no extra argument. Verbatim single-quoted strings double ASCII and smart single quotes. This models PowerShell string syntax; it does not certify native executable argument transport, Windows legacy quoting, cmd.exe, remote shells, shells nested by an invoked program or a particular application parser.
• A quoted argument is still an option if the invoked program treats it as one. Quoting does not make a dangerous executable, destructive option, untrusted script path or a command that later interprets arguments safe. Review the complete source and application semantics before deliberately using it elsewhere. No command is run by this page.
• Output is at most 100,000 UTF-8 bytes in literal-command.txt. This page is not a secret-removal tool: supplied passwords, tokens, paths and command values remain in its visible text and download. It neither reads environment variables nor infers executable locations.
• Structured text output is limited to 500,000 characters. Reduce the supplied source when that separate output budget is exceeded.
• Inputs are processed on this device and are not automatically saved or uploaded.