curl → fetch / axios / Python / Go

What this tool does

Paste a curl command and get the equivalent code in JavaScript (fetch or axios), Python (requests), Node.js (https module), or Go (net/http). The tool parses your curl command properly — handling quoted strings, multi-line continuations with backslash, all the common flags (-X, -H, -d, -F, -u, -b, --data-raw, --data-urlencode, and several others) — and produces code that does the same HTTP request from your language of choice.

This is the tool you reach for after copying a curl example from an API's documentation. Stripe, Twilio, GitHub, OpenAI, AWS — they all show curl. Most of the time you're building in something else. Manually translating the headers and body to your language takes 5 minutes and is error-prone. This takes one keypress.

What it handles correctly

• HTTP method via -X or implied — if you pass -d or -F without an explicit -X, the method is correctly inferred as POST (same as curl itself).
• Headers via -H "Name: Value", multiple times. Order is preserved.
• JSON bodies — when the body looks like JSON (starts with { or [ and parses successfully), the output uses the language's native JSON helper (JSON.stringify(...), Python's json= kwarg, etc.) and adds Content-Type: application/json if you forgot it.
• Form-urlencoded bodies — recognized when the body matches key=value&key=value shape, with the correct Content-Type applied.
• Multipart form data via -F — produces FormData in JS, files= in Python, etc.
• Basic auth via -u user:pass — converted to either an Authorization: Basic … header (fetch, Go) or the language's auth-helper (axios auth: {…}, Python auth=(…)).
• Multi-line commands with \ continuations — copy-paste from a code block in the docs without manual cleanup.
• Combined short flags like -XPOST are handled the same way curl does.
• The -G flag for forcing GET — body data is correctly moved into the URL query string.

What it deliberately doesn't try to do

• File uploads via -F 'file=@path' are partially supported — the field name comes through, but you need to wire up the actual file in your language (browsers' FormData can take a File from an input element; Node has fs.createReadStream; Python has files={'file': open(path, 'rb')}).
• Proxy options, retries, timeouts, max-redirects aren't replicated. They're tooling-level concerns that don't translate cleanly across languages.
• --insecure / -k emits a comment in the output, not an actual TLS bypass — browsers can't disable certificate verification from JavaScript, and you almost never want to in production code anyway.

Common gotchas

• Cookies copied from a browser — when you grab "Copy as curl" from DevTools, the cookie often includes session tokens that expire in minutes. The code converts fine, but the request will fail with 401/403 once the token expires. Either re-login and re-copy, or use a proper auth mechanism (Bearer token, API key) instead.
• The --data flag URL-decodes content but --data-raw doesn't. If your body contains % or +, the choice between these two flags matters and the output reflects what you typed.
• Multiple -d flags get joined with &, matching curl's actual behavior. -d a=1 -d b=2 becomes a=1&b=2, not two separate request bodies.
• The @ prefix in -d @file.json means "read body from a file". The output preserves the literal @file.json as the body string — you need to replace it with actual file-reading code in your language.

Workflow tips

In Chrome DevTools, the Network tab has "Copy as curl" — right-click any request. Paste the result here. Pick your target language. Done.

For larger API integrations (more than a handful of endpoints), use a proper SDK or generate a client from the OpenAPI spec rather than translating curl examples one by one. This tool is for the quick "I need to call this one endpoint" cases — bootstrap a single request, then move on.