How do I convert a curl command to JavaScript fetch?

Paste the command into the box above and choose JavaScript · fetch. The tool reads the request method, every -H header, and any -d body, then writes a fetch() call with the matching method, headers object, and body. A simple `curl https://...` becomes a one-line `fetch(url)`; a POST with a JSON body becomes a fetch with method, headers, and JSON.stringify body.

How do I turn a curl request into Python requests code?

Select Python · requests. The tool maps the method to requests.get/post/etc., passes headers as a dict, and chooses the right body argument: a JSON body becomes the json= keyword (so requests sets Content-Type for you), while a form or raw body becomes data=. Basic auth from -u is added as an Authorization header.

What does the -d flag in curl mean when converting to code?

-d (or --data) sends a request body. Per the curl man page, using -d without -X automatically makes the request a POST, and curl sends the body as application/x-www-form-urlencoded unless you add your own Content-Type. The converter reproduces both of those defaults, so the generated code behaves like the original command.

How do I send custom headers in fetch like curl -H?

Each -H "Name: Value" becomes one entry in the fetch headers object. The tool splits on the first colon only, so values containing colons (like a full URL or a time) stay intact. Repeat -H as many times as you need; every header is carried through to all six output languages.

Can I convert a POST curl command with a JSON body to code?

Yes. When the command has Content-Type: application/json and a body that parses as valid JSON, the JavaScript output uses JSON.stringify, Python uses the json= argument, and Go embeds the JSON string. If the JSON is malformed, the body is emitted verbatim as a raw string so nothing is silently changed.

Is my curl command uploaded to a server?

No. Parsing and code generation happen entirely in your browser using a hand-written shell-style tokenizer — there is no eval, no shell, and no network request. Your tokens, URLs, and any secrets in the command never leave the page. That is the main reason to use this over tools that POST your command to their backend.

Why are some flags shown as skipped?

Runtime-only flags such as -o/--output, -T/--upload-file, --proxy, --cacert, and --retry have no faithful code equivalent, so the tool lists them in a warning banner instead of half-translating them. This keeps the generated request honest — you see exactly what was and wasn't represented.

Does it run the request for me?

No. The tool only converts curl into code; it never sends the request. That is deliberate — executing arbitrary requests from a web page invites CORS errors, SSRF, and abuse. Copy the generated code into your own project and run it there, where your credentials and environment live.

Developer · Utility

cURL to Code Converter

Paste any curl command and get the same HTTP request as ready-to-run code in JavaScript (fetch & axios), Python, Node.js, Go, and PHP. Everything is parsed in your browser — nothing is uploaded, no signup.

By Induwara Ashinsana— Executive Director, Ryzera TechnologiesUpdated Jun 30, 2026

Convert a curl commandto runnable code

Paste your curl command

Multi-line commands with trailing \ are supported. The leading $ prompt, if present, is stripped automatically.

Try a sample

MethodPOST

Headers2

BodyJSON

Output

JavaScript · fetch · request.js

const res = await fetch("https://api.example.com/messages", {
  method: "POST",
  headers: {
    "Authorization": "Bearer TOKEN123",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"to":"94743252452","text":"hi"}),
});
const data = await res.json();
console.log(data);

Flag mappings follow the official curl man page. Basic auth (-u) is base64-encoded per RFC 7617. Sources are listed below the tool.

How it works

A curl command looks simple, but turning it into code by hand means remembering how each flag maps to your HTTP client. This converter does that mechanically. It runs a small shell-style tokenizer over the command — respecting single quotes, double quotes, backslash escapes, and \ line continuations — then classifies each token against the official curl flag definitions. There is no eval and no shell: the command is read as data, never executed.

The flag-to-code mapping follows the curl man page:

-X / --request sets the HTTP method (uppercased).
-H / --header becomes one header, split on the first colon so values with colons survive.
-d, --data, --data-raw and --data-binary set the body. With no -X, the presence of data makes the request a POST — curl's documented default.
-u user:pass becomes an Authorization: Basic header, base64-encoded per RFC 7617.
-F / --form becomes a multipart form; -b becomes a Cookie header; -G moves the data into the query string as a GET.

Bodies are normalized before emitting. When the request carries Content-Type: application/json and the body parses as JSON, the JavaScript targets use JSON.stringify and Python uses the json= keyword (which lets requests set the header itself). A -d body with no content type is emitted as a raw string and tagged application/x-www-form-urlencoded, matching what curl actually sends. Runtime-only flags such as -o, --proxy, and --insecurecan't be reproduced in code, so they are listed in a warning banner rather than silently dropped — the output is never quietly wrong. The three worked examples below are encoded as an in-code self-test (verifyWorkedExamples()) that runs on every build.

Worked examples

Example 1 — simple GET

Input

curl https://api.induwara.lk/v1/tools

No -X flag and no body data.
curl man page: with no method and no body, the default is GET.
The single non-flag token is the URL.
Result: GET https://api.induwara.lk/v1/tools, 0 headers, no body.

Output · JavaScript · fetch

const res = await fetch("https://api.induwara.lk/v1/tools");
const data = await res.json();

Example 2 — POST with JSON body and auth header

Input

curl -X POST https://api.example.com/messages \
  -H "Authorization: Bearer TOKEN123" \
  -H "Content-Type: application/json" \
  -d '{"to":"94743252452","text":"hi"}'

-X POST sets the method explicitly.
Each -H splits on the first colon into a header.
Content-Type is application/json and the body parses as JSON.
Python uses json= so requests sets the Content-Type itself.

Output · Python · requests

import requests

res = requests.post(
    "https://api.example.com/messages",
    headers={
      "Authorization": "Bearer TOKEN123",
    },
    json={
        "to": "94743252452",
        "text": "hi",
    },
)
print(res.json())

Example 3 — Basic auth shorthand (-u)

Input

curl -u admin:secret https://api.example.com/status

-u admin:secret is HTTP Basic auth.
Per RFC 7617, encode base64('admin:secret') = YWRtaW46c2VjcmV0.
That becomes Authorization: Basic YWRtaW46c2VjcmV0.
No body is present, so the method stays GET.

Output · JavaScript · fetch

const res = await fetch("https://api.example.com/status", {
  headers: {
    "Authorization": "Basic YWRtaW46c2VjcmV0",
  },
});
const data = await res.json();

Frequently asked questions

Sources & references

The flag mappings on this page were last cross-checked against the curl man page on 2026-06-30. The parser's three worked examples are re-verified automatically on every deploy.

Related tools

LiveDeveloper

XML to JSON Converter

Convert XML to clean, well-formed JSON instantly and entirely in your browser. Handles attributes (configurable prefix), nested elements, repeated elements collapsed to arrays, CDATA, and a configurable text-node key. Locates well-formedness errors by line and column, and verifies every conversion with a JSON round-trip. No upload, no signup.

Open tool

LiveDeveloper

YAML ⇄ JSON Converter

Convert YAML to JSON and JSON to YAML entirely in your browser. Auto-detects direction, expands anchors/aliases and merge keys, handles multi-document streams, locates parse errors by line, and verifies each conversion with a round-trip check. No upload, no signup.

Open tool

LiveDeveloper

TOML ⇄ JSON Converter

Convert TOML to JSON and JSON to TOML in your browser with validation, type-mapping notes, and a round-trip integrity check, per the TOML v1.0.0 spec.

Open tool

Rate this tool

Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Found a curl flag that converts wrong, or want another target language?

Email me at [email protected] — most fixes ship within 24 hours.