⌘ K
curl → 10 languages · headers · auth · body · live

Convert cURL to code

Translate any cURL command into idiomatic snippets for Python, Node, Go, Java, Rust, PHP, Ruby, C# and PowerShell. Pick a language and paste your command — the rest is automatic.

cURL → Code
Input
161 B
4 lines
Output
262 B
10 lines
Status
ready
live
Ratio
1.63×
out/in
input · curl command
output · python (requests)
import requests

headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer abc123"
}
payload = {"name":"Alice","role":"admin"}

response = requests.post("https://api.example.com/users", headers=headers, json=payload)
print(response.json())
Quick Start

How to port a cURL command

Pick a target language from the dropdown. The cURL parser handles flags, headers, auth and bodies the same way for every backend, so output stays consistent across stacks.

  1. 01

    Paste cURL

    From DevTools, Postman, or a docs snippet.

    Parsing is strict-but-tolerant — comments and trailing commas are accepted on input where the source format historically permits them; output stays canonical.

    inputstricttolerantliveparse
    input · sourcecurl · live
    curl -X POST https://api.example.com
    loaded · parsedtarget · ready
  2. 02

    Pick a target

    Choose Python, Go, Rust, PHP, Ruby, C#, Java, PowerShell or Node axios.

    Conversion preserves type information where the target supports it (numbers stay numeric, booleans stay boolean) so the destination parser never has to re-coerce.

    targettype-preservinglosslesslivememoised
    lang · optionsselect · live
    Python (requests)
    options applied · liveround-trip
  3. 03

    Read idiomatic code

    Generators emit `requests.get` for Python, `http.NewRequest` for Go, and so on.

    Re-encoding is idempotent: running output back through the same converter produces the same bytes, which keeps round-trips git-friendly.

    genidempotentround-tripdiff-cleandeterministic
    out · convertedcode · ready
    requests.post(url, json=payload)
    converted · livediff-clean
  4. 04

    Copy or download

    Grab the snippet and drop into your project.

    Copy writes via navigator.clipboard.writeText; downloads use the target’s native MIME so editors apply the right syntax highlighting on open.

    exportclipboardtarget MIMEblobclient-side
    ok · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Converting between formats, safely

Pick the strictest source format

Lossy formats hide bugs. Choose JSON or YAML as your source-of-truth, convert downstream as needed.

Round-trip in CI

If your converter is idempotent, your CI can verify A → B → A equals the original. Catches subtle data loss.

Numbers vs strings differ

YAML/TOML have a number type; CSV doesn’t. Quote IDs in CSV to keep leading-zero values intact.

Watch character encoding

Source format may be Latin-1 / Windows-1252; target should be UTF-8. Convert encoding before structure.

Preserve comments where you can

YAML and TOML support comments. Don’t silently drop them — they often encode intent.

Schema-aware beats blind

Use a schema to guide conversion. Field types, required-ness, and defaults survive better with structure.

Related toolscURL to fetch()cURL to PythoncURL to GocURL to RustHAR to cURLcURL to PowerShell
Use Cases

When to port cURL

Migration, polyglot teams, integration tests.

SDK scaffolding

Bootstrap a client by porting a few cURL examples to your stack. Type information survives: numbers stay numeric, booleans stay boolean, strings stay strings. The destination parser doesn't have to re-coerce, which avoids the "'true' becomes "true"" bug class.

round-trip safe

Docs samples

Ship cURL + your stack-of-choice side by side in API docs. Run output back through the inverse converter to verify idempotent round-trips in CI. A → B → A should produce byte-identical input — if it doesn't, you've found data loss.

type-preserving

Polyglot teams

Hand the same call off to backend engineers in their language. Comments and metadata survive where the target format supports them (YAML, TOML, HCL). The tool doesn't silently drop intent-encoded annotations, which keeps your config self-documenting.

schema-aware

CI checks

Convert a smoke-test cURL into Python for CI assertions. Pair with a schema (JSON Schema, OpenAPI, Zod, Pydantic) to catch shape drift on either side. Catch breaking changes at conversion time rather than at runtime in production.

lossless

Quick repros

Recreate a bug in a Java or Go service with one click. Output respects target-format conventions: quoting in CSV, indent in YAML, brackets in JSON. Existing parsers don't need patches, and the result drops into legacy pipelines unchanged.

diff-clean

Learning a stack

See how the same HTTP call looks across nine ecosystems. Encoding-aware: handles UTF-8 vs UTF-16 vs Latin-1 / Windows-1252 transparently. The character-set surprise that breaks "works on my machine" doesn't apply here.

spec-grade
FAQ

Frequently asked questions

Python (requests), Node (axios), Go (net/http), Java (OkHttp), Rust (reqwest), PHP (cURL), Ruby (Net::HTTP), C# (HttpClient), and PowerShell.
Yes — -u user:pass and -H Authorization headers both flow through to the generator.
Basic --data and --data-binary are supported. Multipart form-data needs manual tweaks per language.
When the body is not JSON-shaped, generators emit a raw string so you can edit it without re-encoding.
No. Parsing and code generation both run locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!