cURL Converter — To Fetch, Axios & Python Requests
One input, three targets: paste any cURL command and switch between fetch(), axios, and Python requests output instantly. The parser understands quoting rules, line continuations, data flags, and basic auth — and the whole pipeline runs offline in your browser.
Zero upload, ever
Parsing and code generation run in your browser — URLs, headers, and tokens never touch a server.
Live 100 ms conversion
Output updates as you type or paste, with one-keystroke copy via Cmd/Ctrl + Enter.
Three idiomatic targets
fetch() with async/await, axios.request config, or Python requests — not naive string wrappers.
Paste a cURL command to convert
cURL command
Paste a cURL command — idiomatic code appears here instantly, converted entirely in your browser.
Technical documentation
What this cURL converter supports
The parser covers the flags you actually paste from terminals and browser DevTools: -X/--request, -H/--header, -d/--data, --data-raw, --data-binary, --data-urlencode, -u/--user, -G/--get, -I/--head, --json, -A/--user-agent, -e/--referer, and -b/--cookie. Cosmetic flags like -s, -L, -k, and --compressed are ignored safely, and credentials embedded in a URL (https://user:pass@host/) are extracted automatically.
Quoting is handled the way bash does it: single quotes pass through literally, double quotes honor backslash escapes, ANSI-C $'…' strings decode \n and \t, and the ''' idiom for embedded apostrophes works. Multi-line commands pasted with trailing backslashes — or Windows caret continuations — are joined into a single command before parsing.
Method, body, and query-string intelligence
If no -X flag is present, the converter infers the verb: GET for bare commands, POST when a body flag exists, and HEAD for -I. With -G, body data is moved into the query string exactly like curl does, and GET requests carrying -d data are converted to query parameters as well — because browsers reject GET request bodies.
JSON is detected from the Content-Type header, the --json shorthand, or the shape of the body itself. JSON payloads are re-serialized as pretty-printed object literals — JSON.stringify({...}) in JavaScript, json= in Python — while form data keeps application/x-www-form-urlencoded semantics with a raw string body.
Why client-side matters for a cURL converter
Real cURL commands routinely contain bearer tokens, session cookies, API keys, and basic-auth credentials. Uploading those to a conversion API means trusting a third party with production secrets. This tool ships as pre-rendered HTML plus a static JavaScript bundle; the transpiler itself is pure TypeScript with no network calls, so your command is parsed by your own browser and never transmitted, stored, or logged.
Because everything is static and pre-rendered, the tool also works offline once the page has loaded — convenient for air-gapped machines, locked-down corporate laptops, and quick conversions from a train.
Graceful failure instead of silent wrong code
Malformed input produces a readable amber explanation — unterminated quotes, headers missing a colon, flags without values, or unsupported file-backed data like -d @payload.json and -F multipart uploads — instead of silently generating broken code. The last successful conversion stays visible so you never lose work mid-edit.
When a command uses features that genuinely require filesystem or stdin access, the error tells you which flag caused it and why, so you can inline the payload yourself and re-convert.
Frequently asked questions
Is this cURL converter really free and private?
Yes. The converter runs entirely in your browser as a static page — there is no backend API to receive your command. It is free to use with no sign-up, no rate limits, and no logging of any kind.
Which programming languages can I convert cURL to?
Three targets are supported today: native JavaScript/TypeScript fetch() with async/await, axios using axios.request(), and Python 3 using the requests library. Dedicated landing pages for each target are linked below.
What happens if my cURL command is malformed?
You get an inline amber alert explaining exactly what failed — for example an unterminated quote or a header missing its colon — and the last successful conversion remains on screen so you can fix the command without losing the output.
Does it support file uploads with -F or -d @file?
No. Reading local files requires filesystem access that a client-side converter cannot provide. The parser detects these flags and raises a clear error instead of generating code that would silently send the wrong thing.
Are query parameters and URL fragments preserved?
Yes. Query strings are passed through verbatim, and --data-urlencode plus -G combinations are merged into the URL exactly the way curl would, with each value percent-encoded on your behalf.
Can I use the output commercially?
Yes — the generated code is yours. It is plain, dependency-free source (except axios/requests, which are open source) with no attribution required.