What this tool does
Fetch → Curl uses a restricted, safe syntax for parsing, accepting only explicitly supported fetch calls, object literals, string Body, and common JSON.stringify structures. It never uses eval, new Function, or script injection; syntax that cannot be reliably understood will prompt Unsupported Fetch syntax.
- Supports fetch URLs, along with common method, headers, and body options.
- Recognizes string Body and common JSON.stringify literal forms.
- No input JavaScript, generated cURL, or any network requests are executed.
How to use it
- Paste a supported fetch call.
- Click "Convert to cURL".
- If the prompt does not support the syntax, please simplify it to an explicit literal structure.
- Check for escapes and headers after copying the command.
Common uses
- Reproduce front-end requests as terminal commands.
- Generate a shareable minimal request example for a bug report.
- Review Method, Headers and Body in fetch.
Privacy and security
The fetch code is only read through a restricted text parser, does not use eval or new Function, and does not perform code or network requests.
Fetch → Curl Features
Safely parses common fetch calls and generates cURL; does not use eval or new Function. Useful for everyday development and debugging; results can be reviewed, copied, or downloaded immediately.
FAQ
Will the tool run the JavaScript I pasted?
Absolutely not. Input is subject to restricted parsing only, no eval, new Function or script execution is used.
Are variables and arbitrary expressions supported?
Not supported. Syntaxes whose values cannot be statically and safely determined will explicitly report Unsupported Fetch syntax.
Can JSON.stringify be converted?
Common object or array literal forms are supported; dynamic function calls and variable dependencies are not guessed.
Will the request be sent after generation?
No, the output cURL is still just text.