⇄

cURL to Code Converter

Turn any cURL command into fetch, axios, or Python requests code. Parsed locally — safe for real tokens.

100% LOCALFetch / Axios / PythonShlex-safe parserLive preview100% local

Saved Configurations· Auto-save on

▾

The CalculatorPage 1

cURL command

Paste a cURL command to translate it into fetch, axios, or Python code

Data Source & Legal Disclaimer

Effective: 2026Last updated: 2026-09-07Update: Manual review

Sources: Parsing happens locally — MDN fetch API

cURL parsing and code generation run entirely in your browser. Your command (including any tokens!) is never uploaded.

See all data sources & update policy →

How it worksPage 2

↩ Back to calculator

How the parser reads a cURL command — illustrated

A shell tokenizer first splits the command, honoring single quotes (no escapes inside), double quotes (\\" \\$ escapes), and backslash continuations. Then a flag pass maps each option: -H becomes a header pair, repeated -d flags join with & exactly as cURL sends them, -F flags signal multipart FormData, -u becomes HTTP Basic auth, and the method defaults to POST when a body exists, GET otherwise. Output is copy-paste runnable — but review it: secrets in the command end up in the code.

Tokenize (shell rules) → map flags → emit fetch / axios / requests

Quote handling follows real shell semantics: single quotes are literal, double quotes allow escapes, backslash continues lines.

Documenting an API call — Kai's integration notes

Kai copies a working cURL from a Stripe-style dashboard and needs it inside his Next.js route handler.

Paste the command:The multi-line command (backslash continuations) parses to POST, two headers, and a JSON body — nothing to configure
Pick fetch:The emitted code is a drop-in await fetch(url, { method, headers, body }) for his route handler
Check the secrets:The Authorization bearer token from the command appears in the code — expected, since he pasted it locally; the privacy badge reminds him nothing was uploaded
Swap targets:For the Python docs he re-exports the same parse as requests code — one parse, three targets

↩ Back to converter

FAQ & detailsPage 3

↩ Back to calculator

Convert cURL to JavaScript Fetch, Axios, or Python requests online free. Everything runs locally; nothing is uploaded.

FreeToolHub cURL to Fetch Converter is a free browser-based tool — convert cURL to JavaScript Fetch, Axios, or Python requests online free. No signup, no upload; everything runs locally in your browser.

About this tool

What is this tool?

Convert cURL to JavaScript Fetch, Axios, or Python requests online free. Shlex-safe parsing, live preview.

Fetch / Axios / PythonShlex-safe parserLive preview100% local

Why Convert cURL at All

API documentation speaks cURL; your application speaks Fetch, Axios, or Python requests. Retyping a complex command - headers, auth, multipart bodies - is where transcription bugs live. Pasting the command and getting correct, idiomatic code in your actual HTTP client removes the entire class of copy mistakes.

Parsing Like a Shell, Running Like a Browser

The tokenizer mirrors Unix shell rules: single-quoted strings are literal, double-quoted strings honor backslash escapes, and trailing backslashes join continued lines. The parsed request - method, URL, headers, body, auth - previews live before generation, and the whole pipeline runs in your browser so credentialed commands never leave the page.

Reading the Generated Code Like a Reviewer

The generated fetch code is a starting point, and a quick review pass makes it production-ready. First, headers: cURL's single quotes vanish in JavaScript, so strings containing single quotes need escaping — the generator emits double-quoted strings for those, worth double-checking when the body contains both quote types. Second, error handling: fetch resolves successfully on HTTP 404 and 500, unlike axios, so a real implementation needs a res.ok check the one-liner does not include. Third, credentials: cURL's -b cookie flag becomes a Cookie header, but in browsers the cookie jar is managed by the credential option instead — same-origin requests usually want credentials: 'include' rather than a hand-built header. The axios and Python translations carry the same shape: correct as a skeleton, review before shipping.

Frequently Asked Questions

Which cURL flags are supported?

The parser reads -X (method), -H (repeated headers), -d (multiple bodies are joined with an ampersand), -F (multipart with @file detection), -u (basic auth), --url, -L (follow redirects), -k (insecure), -I (HEAD), -A (user agent), -e (referer), and -b (cookies). Unsupported flags are reported instead of silently dropped.

How are quotes and escapes handled?

Commands are tokenized with a shlex-style parser: single quotes protect everything inside, double quotes allow backslash escapes, and backslash line continuations join multi-line commands. This mirrors how a Unix shell would parse the same command.

Is my API token sent anywhere?

No. Parsing and code generation run entirely in your browser - a cURL command containing an Authorization header never leaves the page. This is exactly why the tool exists: pasting credentialed cURL into random websites is a real leak vector.

Why does my fetch code differ from the cURL in structure?

cURL expresses a request as command-line flags while fetch expresses it as an options object — the generator reorders rather than translates word for word. Flags like -X merge into method, -H into headers, -d into body, and -u into an Authorization header. The semantic request is identical even when the layout is not.

Can it handle multipart file uploads?

Yes for the cURL -F form syntax: the generator maps each -F field into FormData and drops the manual Content-Type header, because the browser must set the multipart boundary itself. Binary file references like @photo.jpg become a note in the output — attach a real File or Blob from your code at that field.