Developer

cURL to JavaScript Fetch

Convert cURL commands to JavaScript fetch code for browsers or Node.js. Preserve request headers and bodies with optional secret redaction.

cURL to JavaScript Fetch

Convert cURL commands to JavaScript fetch code for browsers or Node.js. Preserve request headers and bodies with optional secret redaction.

Share:X LinkedIn Facebook

cURL command

Redact secretsRuntime

Generates code locally; it does not send requests. Redaction covers common header, query and body secret names; review the output for custom secrets. Unsupported flags produce an error.

Ready to run. Input limit: 1 MB characters.

Output

—

Output actions

Ready to copy output once your result appears.

cURL to JavaScript Fetch mini guide

Convert cURL commands to JavaScript fetch code for browsers or Node.js. Preserve request headers and bodies with optional secret redaction.

How to use cURL to JavaScript Fetch

1Paste one literal cURL command using POSIX shell quotes, or Load sample.
2Choose Redact secrets; for Fetch choose Browser or Node.js runtime.
3Select Convert cURL, review the generated code and copy or download it.

What it is good for

• Turn a cURL request into browser Fetch code.
• Prepare an ES-module request for Node.js 18+.
• Review headers and bodies before integration work.

Example

Input

curl 'https://api.example.com/users' -H 'Accept: application/json'

Output

const response = await fetch("https://api.example.com/users", {method:"GET", headers:{"Accept":"application/json"}});
console.log(await response.text());

Rules and limitations

Headers, explicit request methods, literal request bodies, cookie strings and basic authentication are preserved. Body input infers POST when no method is supplied. Repeated header names use the final value in the generated header mapping. Transport flags such as --compressed and --location are accepted but do not configure a separate network connection here.

Redaction defaults on and masks common Authorization, Cookie, API key, token, secret and password names in headers, query parameters and structured JSON or form bodies. Custom credential names can escape detection. Inspect the output before sharing it; disable redaction only when you deliberately need the actual credentials in local code.

Browser Fetch needs the destination server to allow your origin through CORS, and browsers control headers such as Cookie. Node.js 18+ has built-in fetch. Run the Node example as an ES module for top-level await. Fetch prohibits GET or HEAD request bodies; those combinations produce an error.

Common problems

Supports one HTTP or HTTPS request. File uploads, @file bodies, --data-urlencode, shell substitutions, pipelines and unsupported flags produce explicit errors. PowerShell and Windows cmd quoting are not parsed.

Conversion generates text only. It does not test API credentials, contact the remote server or guarantee the service will accept the request.

Frequently asked questions

Are API calls made during conversion?

No. The cURL input is parsed locally and converted to code.

Does it preserve authentication?

Basic auth and explicit authentication headers are supported; redaction masks them by default.

Can it convert file uploads?

No. Local files and multipart upload flags are unsupported.

Why does browser Fetch fail with CORS?

The remote server must permit your origin. Code generation cannot change its CORS policy.

Is my input uploaded or saved?

This tool processes input in your browser and does not save its input or output to local storage. Copy and download are user actions. The site uses analytics for page and action metadata and may use ads and production error reporting; see the Privacy Policy for those services.

About this tool

Maintained by Toolbench. For large or deeply nested files, split the input into smaller batches and verify representative results before using them in an import or application. Report reproducible problems through Contact.