Convert Curl to Php Curl

-X/--request, -H/--header, -d/--data, --data-raw, --data-binary, --data-urlencode, -u/--user (basic auth → CURLOPT_USERPWD + CURLAUTH_BASIC), -b/--cookie (→ Cookie header), -A/--user-agent, -e/--referer, -G/--get (build query string from -d), -F/--form (multipart → CURLFile), -L/--location, -k/--insecure, --compressed, --connect-timeout, --max-time.

Each -F 'key=value' becomes an array entry: "key" => "value". Each -F 'file=@path/to/file.jpg' becomes "file" => new CURLFile("path/to/file.jpg") with a comment that the path is relative to the PHP cwd at execution time. You may need to use realpath() or an absolute path depending on your setup.

cURL: curl -G 'https://api.com/search' -d 'q=hello' -d 'limit=10' → makes GET to https://api.com/search?q=hello&limit=10. The tool detects -G and appends the body parts to the URL as query string (preserving any existing ?...). No CURLOPT_POSTFIELDS emitted. Method stays GET.

Single-quoted PHP string. Inside PHP single quotes only \ and \' need escaping – no variable interpolation, no n processing. So a JSON body like {"$ref":"x"} stays literally {"$ref":"x"} (PHP won’t try to interpolate $ref). For URL/header values, double-quoted strings are used with \, \", \$, \n, \r escaping.

The tokenizer assumes POSIX/bash conventions: single-quoted = literal, double-quoted = backslash escapes active. Windows cmd uses different rules (double quotes only, ^ for escape, no single quotes). Convert your command to bash style first (Chrome DevTools “Copy as cURL (bash)” option works). Or run it under WSL/Git Bash.

Setting USERPWD without HTTPAUTH defaults to digest negotiation. Forcing CURLAUTH_BASIC matches the cURL CLI’s -u behaviour (which sends basic auth by default). Without explicit CURLAUTH_BASIC, PHP might attempt a digest dance the server doesn’t support.

Yes. \ + newline is collapsed to a space before tokenisation. So this works: curl 'https://x.com' \
-H 'A: b' \
-d 'data'. Also handles Windows-style \r\n line endings.

Not converted: --cert / --key / --cacert (you’d add CURLOPT_SSLCERT etc. manually with file paths), --proxy (would map to CURLOPT_PROXY but not implemented yet), -o/--output (PHP’s file_put_contents after exec is the equivalent), --resolve (DNS override). If you need these, add the corresponding curl_setopt calls after the generated code.

Yes. cURL input + generated PHP stay in your browser. No request is ever made, no data is logged. API keys, basic auth credentials, and Bearer tokens in your cURL never leave your device.