const res = await fetch("https://api.example.com/users", { method: "POST", headers: { "Content-Type": "application/json", "Authorization": "Bearer abc123" }, body: "{\"name\":\"Toolora\"}" }); const data = await res.json();
How to use
01
Paste your curl command
Drop the full command into the text box, backslash line continuations included. It must start with curl and include a complete http or https URL, or the tool shows an error instead of code.
02
Pick an output language
Switch between the fetch, axios, and Python tabs above the output pane. Each tab regenerates instantly from the same parsed request, so comparing all three takes seconds and no re-pasting.
03
Copy the generated code
Hit the copy button at the top right of the code block and paste the snippet into your project. Swap hardcoded tokens for environment variables before committing anything.
Why cURL to Code
- Convert curl commands to fetch, axios, or Python requests.
- Handles -X, -H, -d, -u flags.
- Live, updates as you type.
Common questions
Which curl flags does the cURL to Code tool understand?
It parses -X (--request) for the method, -H (--header) for headers, -d along with --data, --data-raw, and --data-binary for the body, and -u (--user) for Basic auth. Flags outside that set, like --compressed or -b for cookies, are ignored. If your command depends on one of those, adjust the generated code by hand.
How do I convert a request copied from Chrome DevTools?
In the Network panel, right click the request, choose Copy, then Copy as cURL, and paste the result straight into the input box. DevTools includes every header the browser sent, so you'll usually want to delete the cookie and sec-fetch noise before using the output in a script.
Why did my converted request switch from GET to POST?
That mirrors curl's own behavior: attaching data with -d implies POST unless you force another method with -X. The tool applies the identical rule whenever you convert curl command snippets that carry a data flag, so the generated code matches what curl would really send.
Does the converter send my curl command to a server?
No. Parsing and code generation run as JavaScript inside your browser tab, and nothing is uploaded anywhere. That matters here more than in most tools, because pasted commands routinely contain live API keys and session tokens.
Can this work as a curl to python requests generator?
Yes, the Python tab produces an import requests line followed by a requests.get, requests.post, or matching method call with your URL, headers dictionary, and data argument filled in. It's plain requests code with no wrapper library involved.
What happens to quotes around my JSON body?
The tokenizer understands both single and double quoted arguments, so a body written as -d '{"name":"value"}' comes through intact. In the generated JavaScript and Python, the body appears as a properly escaped string literal you can replace with a native object if your client prefers it.
Is Basic authentication with -u supported?
Yes. A flag like -u admin:secret is converted into an Authorization header with the base64-encoded credentials, which is exactly what curl computes under the hood. You'll see the finished header in all three language outputs rather than a separate auth option.