Linux & Shell
Choose a shell and quote raw argument values. Add a command name to preview the complete call.
Processed in this browser. No command is executed and no input is uploaded.
Enter one executable name or path, without flags; leave blank for arguments only.
Array mode accepts strings only. Empty strings and embedded newlines are preserved.
Limit: 65,536 input + command characters; 1,000 arguments.
One shell layer only. CMD, nested commands and native Windows argument parsing are outside this preview.
Generated 1 argument(s). The preview has not been executed.
Use Shell escape when a file path contains spaces, a name contains an apostrophe, or a copied value contains dollar signs. A value that looks harmless in a text field can become several arguments when pasted into a terminal.
Decide where each argument begins before adding shell syntax. Single mode treats the entire editor as one value; a JSON array gives every value its own boundary, including empty strings and embedded newlines.
Shell escape treats ["", "two words"] as two arguments. The first stays empty, while the space inside the second stays part of that value. Nothing is trimmed, split on whitespace, sorted, or deduplicated.
POSIX closes the surrounding quotes before inserting a literal apostrophe; PowerShell doubles the quote. Switching the target rewrites the syntax while leaving your raw input untouched, including typographic apostrophes.
Choose a JSON string array for multiple values. [] means zero arguments; [""] means one empty argument. In single mode, an empty editor can produce an empty quoted argument when you run manually.
The optional command field is one executable name or path. Put flags and values in the argument array. In PowerShell, a quoted command path needs the & call operator, which is added to the preview.
Automatic conversion waits 350 ms after an edit. Turn it off to reveal the generation button or press Ctrl/Cmd + Enter. Any input or option change immediately disables export until a fresh result exists.
Every argument uses a single-quoted form. Dollar signs, wildcard characters, semicolons, backticks and command-substitution text stay literal. The result is one shell quoting layer, intended for direct use in the selected shell.
ASCII apostrophes and the four single-quote characters U+2018 through U+201B are doubled individually. Backslashes stay backslashes. A Windows path does not need JSON escaping in single mode; array mode follows JSON syntax.
The result joins independently quoted arguments with spaces and reports their count. Add an optional executable path, copy the full result, or download plain text. An empty list with no command has no text to export.
A POSIX single-quoted region cannot contain an apostrophe directly. Close it, insert an escaped apostrophe outside it, then reopen it: O'Brien becomes 'O'\''Brien'. The POSIX option generates this form for every occurrence.
Single quotes keep the enclosed value literal. Double quotes still allow expansions such as $HOME and $(...). This page deliberately generates literal quoting; use the original shell syntax yourself when expansion is actually intended.
Quote each argument separately, not the whole command line. For two values containing spaces, select array mode and enter two JSON strings. Check that the result reports two arguments before copying it into your script.
Whitespace or delimiter splitting can discard empty fields. Here, ["a", "", "b"] keeps all three arguments. [] has none, while [""] has exactly one. The distinction is explicit rather than guessed from blank lines.
Yes. PowerShell represents an embedded apostrophe by doubling it: 'don''t'. Its parser also recognizes curly single quotes, which this tool doubles without changing their character. This is separate from CMD quoting and native-program argument passing.
Unexpected permission result?
Use Shell escape with the shell you will actually paste into. Compare the argument count, inspect the preview, and copy only the current result.