Paste a curl command
Why convert curl commands?
Browsers and API tools (Chrome DevTools, Postman, Insomnia) give you a ready-made curl command that reproduces a request exactly. To run that same request in your own application you need code in the language your project uses. This converter parses the command and rebuilds it as correct, runnable code so headers, cookies, query strings, JSON bodies and form fields all survive the move.
What the parser handles
-X/--requestfor the HTTP method, with automatic POST detection from-dand-F-H/--header, repeated headers, and the combined--user-agent/--refererforms-b/--cookiecookie strings, plus cookie parsing from a Cookie header-d/--data/--data-raw,--data-urlencode, and-F/--formmultipart fields- Basic auth from
-u/--user,-kinsecure,-Lfollow redirects,-IHEAD - Shell quoting: single quotes, double quotes, escaped characters, and multi-line backslash continuations
Supported target languages
- Python using the
requestslibrary - Node.js using native global
fetch - Browser using
fetchfor front-end work - PHP using
curlviacurl_init - Go using
net/http - C# using
HttpClient - PowerShell using
Invoke-RestMethod - cURL reference, a normalized and commented version of the original
Why a parser instead of asking an AI
Language models reword curl commands from memory, so they quietly drop cookies, reorder headers, misplace query parameters, or invent flags that never existed. A tokenizer follows the exact shell grammar: every flag, quote and separator is processed with fixed rules, so the output matches the input command character for character. When you are moving a live authenticated request, deterministic parsing is the safer choice.
Privacy
Everything runs in your browser. The command never leaves the page, which matters when a request contains session cookies or API tokens you do not want to paste into a hosted service.
Comments & Ratings