# Performate vs postman-to-k6 (CLI converter)

Canonical HTML: https://performate.app/compare/postman-to-k6

postman-to-k6 (and similar CLI converters) emit a k6 script from an exported Postman collection. Performate imports that JSON into a desktop workspace so environments, scenario types, and reports stay together after the first conversion.

## Why not only a CLI converter from Postman to k6?

| Capability | Performate | postman-to-k6 CLI |
| --- | --- | --- |
| Output | Workspace: requests, variables, scenarios, reports | A generated .js file (one-shot) |
| Environments | Imported and reused across runs | Mapped into the script; you maintain the file |
| Next release | Re-import or edit in the app | Re-run the converter and merge by hand |
| OS / install | Windows desktop app; k6 bundled | Node/npm (or Docker) plus a separate k6 install |

## When to choose which

### Choose Performate when you need

- Postman → k6 as an ongoing workspace, not a one-off script dump.
- Scenario types, thresholds, live metrics, and shareable reports in one app.

### Choose a CLI converter when you need

- A single generated file to commit and run with k6 you already installed.
- No desktop app, or a non-Windows generator host.

## FAQ

### Is Performate the same as postman-to-k6?

No. postman-to-k6 is an open-source CLI that writes a script. Performate is a Windows k6 desktop app that imports collections, runs scenarios, and shares reports.

### Can I still use the CLI converter with Performate?

You can import existing .js tests. Most teams skip the extra converter step and import Postman JSON directly into a Performate workspace.

Related: https://performate.app/resources/postman-to-k6