Parse a curl command into its parts and convert it to fetch, axios, Python, Go, Java, C# or PowerShell, with unsupported flags reported rather than dropped.
Waiting for a command
Paste anything starting with curl. Nothing is executed.
Nothing to convert yet
Paste a curl command on the left.
cURL Converter runs entirely on your device — nothing is uploaded, and no request is ever sent.
You’re on the Free plan. Compare plans
A curl command copied out of a browser's network tab is the most common way an API request travels between people, and it is rarely in the language you need. This parses it and writes it out again.
Every flag it recognises is listed with what it did, and every flag it does not recognise is listed as unsupported. That second list is the point. A converter that silently drops `--insecure` hands you code that verifies certificates when the original did not, and the difference only appears when something fails in production.
Flags with real consequences are explained rather than just applied. `--insecure` turns off the check that you are talking to the server you meant, which belongs in a local debugging session and nowhere else.
The shell tokeniser handles the syntax curl commands actually use — single and double quotes, backslash continuations, `$'...'` — and says so rather than claiming to be a shell. A command using substitution or a pipeline is reported as beyond it, because guessing there produces a request that differs from the one you pasted.
Nothing is executed and nothing is sent. The command is parsed as text.
No. It is parsed as text and never run. No request is sent and no shell is involved.
It is listed as unsupported rather than ignored. That matters most for flags that change behaviour — dropping `--insecure` quietly would give you code that behaves differently from the command you pasted.
No, and it says so rather than guessing. Quoting, escapes and continuations are handled. A command using substitution, variables or a pipeline is reported as beyond what this can read faithfully.
Because curl does not care what is in `-d`; it sends bytes. If the Content-Type says JSON the body is treated as JSON and checked. Without that header it stays raw, which is what curl itself does.
Yes — the HTTP Request Builder emits curl among its targets, so a request built there comes out as a command you can paste into a terminal.