Postman / Insomnia Collection Converter

Convert a whole collection at once

Exporting a collection from Postman (Collection v2.0 / v2.1 JSON) or Insomnia (JSON export, format 4) gives you a single file with every request your team has built. This converter turns that file straight into runnable code — one labeled snippet per request — instead of making you open each request and copy snippets one by one:

• cURL — one command per request, with -H, -u, --data-raw, --data-urlencode, -F and friends, formatted across multiple lines with backslash continuations (or one line per command if you untick the option).
• JavaScript fetch() — modern await fetch(...) snippets with a headers object and a correctly typed body (JSON.stringify(...), URLSearchParams, or FormData).
• JavaScript axios — await axios({...}) snippets; JSON bodies become plain object literals and basic auth uses axios's native auth option.

Folders are flattened and each snippet is preceded by a comment with its folder path and request name, so the output stays navigable. Everything runs locally in your browser — your collection, tokens, and passwords are never uploaded.

Worked example

Input (a Postman collection with one request):

{
  "info": { "name": "Demo API" },
  "item": [{
    "name": "Create user",
    "request": {
      "method": "POST",
      "url": "https://api.example.com/users",
      "auth": { "type": "bearer", "bearer": [{ "key": "token", "value": "abc123" }] },
      "body": { "mode": "raw", "raw": "{\"name\":\"Ada\"}",
                "options": { "raw": { "language": "json" } } }
    }
  }]
}

Output with the cURL target:

# Create user
curl -X POST 'https://api.example.com/users' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer abc123' \
  --data-raw '{"name":"Ada"}'

Switch the output format to fetch() and the same request becomes:

// Create user
const response = await fetch('https://api.example.com/users', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer abc123',
  },
  body: JSON.stringify({"name":"Ada"}),
});
console.log(await response.text());

What's covered

Per request: HTTP method (GET omits -X, HEAD becomes curl -I), the full URL (raw or reassembled from Postman's structured url object), headers (disabled entries are skipped), and every common body mode — raw text, JSON (a Content-Type: application/json header is added when missing), x-www-form-urlencoded, multipart form-data (file fields become @path in curl and placeholder FormData appends in JS), whole-file bodies, and GraphQL (wrapped into the standard {"query": ..., "variables": ...} JSON body). Auth is honored at request level or inherited from the collection: basic (curl -u, a base64 Authorization header for fetch, axios's auth option), bearer tokens, and API keys sent as a header or query parameter.

{{variable}} placeholders are resolved from the collection's own variables and Insomnia environments; the Variables field adds or overrides values (Postman environment export JSON, a plain JSON object, or KEY=VALUE lines — both {{name}} and Insomnia's {{ _.name }} forms are matched). Anything unresolved is left verbatim so you can spot it.

Limits and edge cases

• At most 200 requests per collection; larger collections are rejected with a clear count.
• Input must be JSON: Postman Collection v2.0/v2.1 or Insomnia export format 4. Postman v1 collections and Insomnia's newer YAML exports aren't parsed — re-export as v2.1 / JSON.
• Pre-request and test scripts are not executed, and dynamic values such as {{$guid}} or {{$timestamp}} are not generated — they stay as-is in the output.
• File references (@photo.png, form-data file fields) keep the exported path; attach the real file when you run the snippet.

FAQ