Postman, Thunder Client & cURL to .http converter
Paste a Postman collection (v2.0/v2.1), a Postman environment, a Thunder Client collection export or thunder-tests/*.json file, an OpenAPI / Swagger definition (JSON or YAML; details), or a cURL command. You get plain .http files, one per folder, plus an http-client.env.json for environments. The files work in REST Client, Plainwire, httpYac and the JetBrains HTTP Client.
The conversion runs in this page with the same code as the Plainwire extension and CLI. Your collection is not uploaded or stored, and the page makes no network requests. Exported environments can still hold real tokens, so check them before you commit the files.
What gets converted
| From | To |
|---|---|
| Folders | One .http file per folder; nested folders become subfolders (Orders / Refunds → Orders/Refunds.http); requests outside folders go to requests.http |
| Requests | ### blocks titled with the request name, in the collection’s order |
| Collection variables | @name = value lines at the top of each file |
| Environments | http-client.env.json ({{var}} syntax is kept) |
| Bearer, Basic, API key auth | Authorization or the API key header / query parameter, inherited auth applied per request |
| Bodies: raw, JSON, form, multipart, GraphQL, binary | The same body in .http syntax; files as < ./path |
Thunder Client tests, simple Postman pm.test checks | # @assert status == 200, # @assert $.id exists and similar lines |
| Other Postman test scripts and pre-request scripts | Kept as > {% %} / < {% %} blocks that Plainwire runs with a Postman-compatible pm API (details) |
| Thunder Client scripts, folder- and collection-level Postman scripts | Not converted; listed under “Not converted” |
Then what?
- Open the files in VS Code, Cursor or VSCodium with Plainwire for a form editor, a response viewer, environments and a test runner. No account, no request limits.
- Or keep them as text with REST Client, and run them in CI with the free Plainwire CLI: one file with no dependencies, JUnit output.
- Going the other way? The .http to cURL and code converter turns requests back into cURL, fetch, Python, Go and 7 more.
Step-by-step guides with the full field mapping: Postman to .http, OpenAPI / Swagger to .http, Thunder Client to .http, cURL to .http.
FAQ
Is my collection sent anywhere?
No. The converter is a script on this page (source). It reads the text you paste or the files you choose, converts them in memory and lets you copy or download the result. Nothing is uploaded and nothing is stored after you close the tab.
Can I convert a whole thunder-tests folder?
Yes. Choose all of its JSON files at once (for example thunderclient.json, thunderCollection.json and thunderEnvironment.json, or the collections/ and environments/ files of the newer layout) and they are combined into one result.
Can I convert Thunder Client’s own data files?
Yes: drop a thunderclient.db, thunderActivity.json (the Activity history) or another Thunder Client .db file here. For a whole data folder, the extension (Plainwire: Import from Thunder Client…) or plainwire import --thunder reads it in one go, with no export or login; see where Thunder Client stores its data.
Postman v1 collections?
Not supported. Open the collection in Postman and export it again as Collection v2.1.
How is this different from the extension’s import?
It is the same converter. In VS Code, Plainwire: Import from Thunder Client / Postman / cURL writes the files straight into your workspace; the CLI does it with plainwire import.