Paste a Linux / bash curl command, get one that actually runs on Windows — the curl.exe alias, line continuations and JSON quoting all handled. 100% in your browser, nothing uploaded.
In Windows PowerShell 5.1, curl is an alias for Invoke-WebRequest, and the alias wins over any real curl in your PATH — so -H and -d fail with strange errors. The fix is to call curl.exe explicitly, which is exactly what this converter outputs.
'{"key":"value"}' needs no escaping.-d "{""key"":""value""}".\" inside single-quoted strings.\ vs ^ vs `bash continues a line with a backslash, cmd uses a caret, and PowerShell uses a backtick. PowerShell also breaks arguments that contain newlines, so multi-line JSON bodies must be collapsed to a single line. This converter rewrites all continuations and folds JSON automatically.
Paste it above. The converter rewrites line continuations, converts quotes to each shell's rules, and calls curl.exe in PowerShell — then you copy the result and run it as-is.
Because "curl" is a built-in PowerShell alias. Typing curl.exe (with the extension) bypasses the alias and runs the real curl bundled with Windows 10 and 11.
Both shells mangle double quotes when passing arguments to native programs. cmd needs them doubled, PowerShell needs them backslash-escaped inside single quotes. Wrong quoting sends a broken JSON body — the server replies "JSON parsing failed".
Windows Terminal shows the warning "You are about to paste text that contains multiple lines. If you paste this text into your shell, it may result in the unexpected execution of commands." — because each line may run as a separate command. It's a reliable sign your command is still in bash syntax: backslash continuations and single quotes don't survive Windows shells. Convert the command first; the output is safe to paste.
No. Everything runs locally in your browser with JavaScript. Your commands, tokens and responses never leave your machine.