Turn a cURL command into ready-to-run code — multipart, body-from-file and repeated headers all handled correctly — or open a live WebSocket connection, filter the message log, and export it. Both run entirely in your browser.
{{ curlError }}
Ignored (no equivalent in generated code): {{ ignoredFlags.join(', ') }}
{{ generatedCode }}This only converts the command to code — it never sends the request. To actually fire it and see a real response, use the HTTP client in HTTP Status Codes.
The cURL Converter parses flags like -X, -H, -d, -F and -u out of a pasted command and re-emits the same request in 19 languages and formats. Repeated -H headers are merged into one value the way HTTP actually combines them, rather than letting a generated object/dict literal silently keep only the last one; -d @file.json is recognized as "read this file's contents", not sent as the literal text "@file.json"; and a flag it doesn't model (proxying, TLS options, rate limits…) is skipped and listed above the generated code instead of aborting the whole conversion.
Multipart (-F) gets real generated code for JS Fetch (FormData), Python requests, PHP cURL/Guzzle, and the Postman collection export; other targets get an explanatory comment naming what's missing rather than silently mishandling it. A file field can't carry real bytes — nothing running from a pasted command can read an arbitrary local path — so those targets reference the file by name for you to wire up.
The WebSocket Tester opens a real WebSocket connection from your browser to any ws:// or wss:// URL and logs every sent and received message, with an optional JSON pretty-print, a direction/text filter over the log, and an export of whatever the filter currently shows.
Both tools run entirely client-side. Nothing you paste, type, or connect to is sent to any server other than the one you point the WebSocket at.
