cURL to fetch / axios Converter

Chrome / Firefox / Safari DevTools → Network tab → right-click any request → Copy → Copy as cURL. Postman and Insomnia have a similar export.

Yes. --json shorthand sets the body and adds the Content-Type: application/json and Accept: application/json headers if you didn't set them already.

Flags that don't change the request payload are ignored — fetch and axios already follow redirects by default, and verbose output is a CLI-only concern.

axios uses data for request bodies, and if the body parses as valid JSON the converter emits it as a JS object literal — but only when the Content-Type is JSON or unset. With a form or other Content-Type, or a body that doesn't parse, it stays a string, because axios would URL-encode an object sent as a form and change the bytes curl sends.

They are merged into one body separated by &, which is what curl itself does: -d a=1 -d b=2 sends a=1&b=2, not two separate bodies and not a=1b=2. The same applies across the data flags, so mixing -d and --data-raw in one command still produces a single joined body. --data-urlencode is percent-encoded the way curl does it: in name=value only the value is encoded, so q=hello world becomes q=hello%20world. Data sent with the -d family also gets curl's Content-Type: application/x-www-form-urlencoded unless you set one, and with -G the joined data goes into the query string of a GET instead of a body.

Yes, and it is encoded as UTF-8 before base64 as RFC 7617 requires. This is worth stating because the naive approach — passing the string straight to the browser's btoa — reads it as latin-1 instead: an accented password comes out as different bytes that the server will reject, and anything above U+00FF, such as Korean or Japanese, makes btoa throw outright. Check the generated Authorization header if a login works in curl but not in the converted code.