cURL to JSON Converter
Code GeneratorsTurn cURL commands into structured JSON request objects, or generate a ready-to-paste n8n HTTP Request node. Headers, auth, query strings and bodies preserved — 100% local.
Paste a cURL command — get structured request JSON or a paste-ready n8n node.
cURL to Python Converter
Convert any cURL command into clean Python code. Get ready-to-run requests, httpx and FastAPI snippets with headers, auth, JSON and form data preserved — free and private.
JSON to YAML Converter
Convert JSON to clean, readable YAML instantly. Choose 2 or 4 space indentation, validate JSON in real time, then copy or download — nothing ever leaves your browser.
Slack Webhook Builder
Build Slack messages visually — headers, markdown, buttons and image blocks. Live preview, generated JSON payload and one-click test delivery to your webhook URL.
Docker Run to Compose Converter
Convert any docker run command into a clean docker-compose.yml. Parses ports, volumes, env vars, restart policy and networks, with optional Traefik label generation.
How to Use
Three steps from raw data to finished output — no account required.
- 1
Paste the cURL command — flags, headers, auth and JSON or form bodies are parsed instantly.
- 2
View the structured request JSON, or switch to the n8n tab for a complete HTTP Request node.
- 3
Copy the payload — the n8n node pastes directly into an HTTP Request node's JSON view.
Frequently Asked Questions
Everything you need to know about the curl to json converter.
A clean object with the HTTP method, full URL, a headers map, parsed query parameters and the body — JSON payloads are parsed to real objects, while form data is returned as key/value pairs.
In n8n, open an HTTP Request node (or create one), click 'Edit as JSON' (or open the node's JSON view) and paste the generated node definition. It includes method, URL, header and query parameters, the JSON body and typeVersion 4.2 settings.
Yes. Authorization headers, Bearer tokens, basic auth from -u and cookies are all preserved verbatim in both output tabs — review them before sharing, since commands often contain live credentials.
Yes. Shell line-continuation backslashes, single and double quoted values and escaped characters are tokenized correctly, so commands copied from documentation — however they are wrapped — parse cleanly.