Developer tool
Your Thunder Client requests are yours. Here they are.
Thunder Client keeps your saved requests as plain JSON in your own project folder, under thunder-tests. Drop those files here and get them back as .http files, Bruno, a Postman collection, or curl commands — with folders, headers, bodies and inherited collection auth intact. Free, no account, and nothing is uploaded: the conversion happens in this browser tab.
Drop your thunder-tests folder here
thunderclient.json, thunderCollection.json, thunderEnvironment.json — or just the first one.
Nothing is uploaded. The conversion runs in this browser tab.
Prefer to do it inside VS Code?
The same converter is packaged as an extension that finds your thunder-testsfolder on its own — including the copy in VS Code's global storage, if you never used a workspace — and writes the converted files next to it. Download thunder-export-0.1.0.vsix and install it with code --install-extension thunder-export-0.1.0.vsix, or from the Extensions view: … → Install from VSIX. Then run Thunder Export: Convert Thunder Client Collection from the command palette.
Frequently asked
Where are my Thunder Client requests stored?
In your project, not in the extension: open the workspace folder Thunder Client was used in and look for a thunder-tests directory. It holds thunderclient.json (your requests), thunderCollection.json (collections and folders) and thunderEnvironment.json (environment variables). Drop all three here. If you used Thunder Client without a workspace, the same three files live in the extension's global storage folder — on Linux and macOS that's under ~/.config/Code/User/globalStorage/rangav.vscode-thunder-client, and on Windows under %APPDATA%\Code\User\globalStorage\rangav.vscode-thunder-client.
Do my requests or API keys get uploaded anywhere?
No. The converter is plain JavaScript running in your browser tab — there is no upload, no request to our server, and nothing is stored. You can confirm it by opening your browser's network tab, or by loading the page and then going offline before you drop the files in; it still works.
Which formats can it convert to?
.http files (read by the REST Client and httpYac VS Code extensions and by JetBrains' built-in HTTP client), Bruno .bru files, a Postman v2.1 collection (which Postman, Insomnia and Hoppscotch all import), and a shell script of curl commands.
What carries over, and what doesn't?
Method, URL, path and query parameters, headers, all body types, collection folder structure, and auth — including auth set once on the collection and inherited by every request in it, which is the piece most converters silently drop. Thunder's test assertions and pre-request chains have no equivalent in any of the target formats, so they aren't converted; the tool lists exactly what it skipped after each conversion rather than leaving you to discover it later.
Why does it warn me about credentials?
Collections routinely have real tokens typed straight into a header or an environment variable. Of six public repositories used to test this converter, two had committed a live-looking JWT or OAuth client secret inside thunder-tests. The tool flags values that look like credentials so you can swap them for a variable before the exported files land in a repo. It shows only the field name and a masked preview — never the value.
Is it really free?
Yes. Getting your own data out of a tool shouldn't cost anything, and there's no account, no email, and no paid tier on this page.