cURL to Fetch Converter

About curl to fetch

Paste a curl command copied from API documentation, browser dev tools or shell history and get equivalent JavaScript. You choose between fetch and axios output, and a parsed summary shows the method, URL, headers, basic-auth user and body that were extracted. Anything the converter cannot translate is listed as a warning instead of being dropped silently.

How to use it

1. Paste the whole command into the curl command box. Backslash line continuations and a copied shell prompt are both handled.
2. Check the Parsed request card to confirm that the method, URL, headers and body are what you expected.
3. Read any warning box, for example about --insecure, multipart -F fields or an unsupported flag.
4. Pick the fetch or axios tab under Generated code.
5. Press Copy, or Download to save request-fetch.js or request-axios.js.

A JSON POST with basic auth

curl -X POST https://api.example.com/users -H 'Content-Type: application/json' -u admin:secret -d '{"name":"Ada"}'

const response = await fetch("https://api.example.com/users", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Authorization": "Basic " + btoa("admin:secret"),
  },
  body: JSON.stringify({
    "name": "Ada"
  }),
})
(followed by a response.ok check and a response.json() call)

When to use it

• Moving a working request from API docs into a Node script or browser app without retyping the headers.
• Turning a Copy as cURL export from browser dev tools into code that reproduces a bug.
• Converting a webhook test command from a vendor guide into an axios call for an existing codebase.
• Learning how curl flags such as -G, -I or -u map onto fetch options.

Questions about curl to fetch

Which curl flags are understood?

-X, -H, -d with its --data-raw and --data-binary variants, -u, -A, -e, -b, -G, -I, -L, --compressed and --url. Output-only flags such as -s, -v and -i are accepted and ignored, and anything else produces a warning.

Which method is chosen when I leave out -X?

The rule follows curl itself: GET by default, POST when a body or form is present, and HEAD with -I. With -G the data is moved into the URL query string and the request stays a GET.

Why was my JSON body reformatted?

If the Content-Type header mentions json and the body parses, the generator emits JSON.stringify with the object pretty-printed. A body that is not valid JSON falls back to a plain string literal so nothing is altered.

What happens with -d and no Content-Type header?

curl sends application/x-www-form-urlencoded in that case, so the generated code adds the same header explicitly. That keeps the JavaScript request behaving like the original command.

Can it handle -k or file uploads with -F?

Neither converts. A browser cannot disable TLS checks, so -k only raises a warning, and -F fields are listed in a warning so you can build a FormData object yourself.

Related tools

• HTML minifierMinify your HTML by removing all the unnecessary characters.
• CSS minifierMinify your CSS by removing all the unnecessary characters.
• JS minifierMinify your JS by removing all the unnecessary characters.
• JSON validator & beautifierValidate JSON content and make it looks good.
• SQL formatter/beautifierFormat & beautify your SQL code with ease.
• HTML entity converterEncode or decode HTML entities for any given input.