A free Thunder Client alternative without login

Thunder Client made a GUI API client inside VS Code popular. Its recent versions ask you to sign in before you can send requests, and the free plan now has limits. If you only want to fill in a URL, press Send and keep your requests next to your code, Plainwire does that for free, with no account and no limits, and stores everything as plain .http files in your repository.

Plainwire is an independent open-source project. It is not affiliated with or endorsed by Thunder Client, Postman or REST Client.

Take your collections with you, no export and no login (new in 0.17). Thunder Client keeps your collections, environments and history as files on your computer. Plainwire reads them straight from that folder: run Plainwire: Import from Thunder Client…, or plainwire import --thunder in a terminal, and they become .http files in your project. Nothing is sent anywhere. Where Thunder Client stores its data.

What changed in Thunder Client

According to the Thunder Client pricing page (as read on 20 November 2026), the free plan allows 50 requests per collection and 50 collection runs per month, while Git Sync and custom scripting are on paid plans. Recent versions also require signing in to an account to send requests, which is the most common complaint in the extension’s recent marketplace reviews. Thunder Client remains a capable product with features Plainwire does not have yet; if those limits do not affect you, there may be no reason to switch.

Comparison

Facts about other products are taken from their public pages and listings as of November 2026. “Not verified” means we could not confirm it either way.

Plainwire 0.17Thunder Client (free plan)REST Client
PriceFree, MIT open sourceFree plan; paid plans from $3/user/month (billed annually)Free, open source
Sign-in to send requestsNeverRequiredNever
GUI request editorYesYesNo (text only)
Requests per collectionUnlimited50Unlimited
Storage format.http files in your repoJSON; saving to the workspace with Git Sync is a paid feature.http files in your repo
Team syncThrough git, freeGit Sync on paid plansThrough git, free
EnvironmentsYesYesYes
Request chainingYes (named requests)YesYes (named requests)
ScriptingYes, JetBrains-style JavaScript, free (guide)Paid plansNo
Test assertions / collection runnerYes, # @assert + Run all, no run limitsYes; runner limited to 50 runs/monthNo
Command-line runner for CIYes, free CLI + GitHub Action on the same .http filesYes (@thunderclient/cli, Node 22+)No
GraphQL editorYes, Query + Variables (guide)YesGraphQL requests written as text
Import Thunder Client / Postman / cURLYes / Yes / Yesn/a / Yes / YesNo / No / Yes (cURL)
TelemetryNoneNot verifiedNot verified
Last releasev0.17, November 2026November 20262022
Install in Cursor / VSCodium.vsix now; Open VSX coming soonOpen VSXOpen VSX

How to switch in five minutes

  1. Install Plainwire. Download the .vsix from the latest release and run Extensions: Install from VSIX… (see install steps).
  2. Import, without exporting first. Open your project and run Plainwire: Import from Thunder Client… (Command Palette, or the button in the Plainwire sidebar). It lists the Thunder Client data it finds on this computer, in VS Code, Cursor, Windsurf, VSCodium and other editors, and in the project’s thunder-tests folder, with the number of collections, requests and environments in each. Pick one; you do not need to export anything or sign in to Thunder Client. Plainwire writes the requests as .http files into your workspace. Already have exported JSON files? Choose Choose exported or data file(s)… in the same list.
  3. Set up environments. Imported environment values go into http-client.env.json. Move secrets (tokens, passwords, API keys) into http-client.private.env.json and add that file to .gitignore.
  4. Commit. Review the new .http files, send a couple of requests from the Send Request links, and commit them. Your teammates get the collection with their next git pull, no account needed.

The full field-by-field mapping is on Thunder Client collections to .http files.

What a migrated request looks like

A Thunder Client request with a bearer token, a query parameter and a JSON body becomes a block like this:

### Create order
POST {{baseUrl}}/orders?dryRun=false
Authorization: Bearer {{token}}
Content-Type: application/json

{
  "sku": "TSHIRT-M",
  "quantity": 2
}

It is readable in code review, works in REST Client and JetBrains IDEs, and opens as a form in Plainwire.

What does not carry over

Why plain files

A collection that lives in a vendor’s storage can be limited, moved behind a login or lost in an update. A .http file in your repository cannot: you can read it, diff it, review it and run it with several different tools. That is the main design choice behind Plainwire, and the reason it never needs an account.

Questions

Will Plainwire add limits or a login later?

The core client is MIT-licensed open source, so it can always be used, forked and built without an account. Sending requests, collections, environments and imports are part of that open-source core.

Can I use Plainwire and Thunder Client side by side?

Yes. They do not share storage. Plainwire only writes .http / .rest files and its own local history; when you import, it reads Thunder Client’s files but does not change them.

Does it work in Cursor and Windsurf?

Yes, install the same .vsix with Extensions: Install from VSIX….