Thunder Client Pro Paywall: What Changed and Your Best Alternatives

TL;DR

Thunder Client has moved git sync—saving your collections as JSON files in your project—behind a Pro paywall. Free users can still send requests, but collections are now stored in VS Code's extension storage, not in your project or git. Your best free alternatives: REST Client (file-based, git-friendly), Apidog (cloud sync, free workspace), or sticking with an old Thunder Client version (limited support).

Try Apidog today

Introduction

Thunder Client was popular with developers because it was a lightweight, free, git-friendly API client inside VS Code—collections lived as JSON files in your project directory, making them version-controlled alongside your code.

With git sync now restricted to the Pro tier, this core value is gone for free users. Below, you’ll find what changed, what’s missing, and how to migrate in 2026.

The timeline: how the paywall happened

Originally, Thunder Client was a free VS Code extension, storing collections as JSON in a .thunder-tests directory—naturally git-tracked.

With the introduction of the Pro tier, several features moved behind the paywall:

• Git sync: Collections as JSON in your project directory (now Pro-only).
• Team sharing: Share collections via git.
• CLI runner: Run collections from the command line for CI/CD.

The free tier still covers basic request sending, local collections, and environment variables. But if you relied on git for API collections, your workflow is affected unless you upgrade to Pro.

What free users actually lost

After updating Thunder Client as a free user, these changes take effect:

• Collection location: Collections move from project JSON files to VS Code’s internal extension storage:

  • Not visible in your project directory
  • Not tracked by git
  • Not shared with teammates via repository
  • Tied to your local VS Code install

• Git history: Request changes and history are no longer tracked in git.

• Code review integration: You can't review API collection changes via pull requests; sharing now requires manual export/import or Pro subscription.

Option 1: Stay on an older Thunder Client version

You can freeze Thunder Client at an older version to keep git sync:

1. Disable auto-update: Right-click Thunder Client in VS Code extensions panel > "Disable Auto Update".
2. Install specific version: Download .vsix from the extension’s release history and install manually.

Limitations:

• No bug fixes or security updates.
• Potential incompatibility with future VS Code versions.
• Maintenance hassle.
• Storage formats may change, reducing usefulness over time.

This is a short-term workaround, not a long-term solution.

Option 2: Switch to REST Client

REST Client by Huachao Mao is the top free, file-based replacement.

• Uses .http files—plain-text requests in your project, tracked by git.

• Example request:
  

  GET https://api.example.com/products HTTP/1.1
  Authorization: Bearer {{token}}
  Accept: application/json
  

• Requests are version-controlled, diffable, and code-reviewable.

Migration steps:

1. Install REST Client extension in VS Code.
2. Export Thunder Client collections as JSON.
3. Manually rewrite your key requests as .http files.
4. Remove or archive your old Thunder Client collections.

No automated converter exists, but moving requests is usually straightforward.

Downside: REST Client has no GUI—you author requests as plain text.

Option 3: Switch to Apidog

Apidog solves the git sync problem via cloud workspaces, not plain files. Free tier supports up to 3 users, with synced collections across devices.

Migration steps:

1. Export Thunder Client collections (File > Export).
2. Create a free Apidog account at apidog.com.
3. In Apidog, click “Import” and upload your JSON export.
4. Install the Apidog VS Code extension.
5. Sign in to your Apidog account in the extension.
6. Your imported collections appear inside VS Code.

Benefits over Thunder Client free:

• Cloud sync across devices
• Team sharing (up to 3 users free)
• Request history & API documentation
• Desktop app with the same workspace

Trade-off: Collections are in Apidog’s cloud, not local files in git. If you need git-based storage, REST Client is better.

Comparing the migration paths

Option	Git sync	Free	GUI	Migration effort
Old Thunder Client (frozen)	Yes (old ver.)	Yes	Yes	Low (unsustainable)
REST Client	Yes (.http)	Yes	No	Medium
Apidog	Yes (cloud)	Yes (3 users)	Yes	Low–Medium
Thunder Client Pro	Yes	No (~$10-15/mo)	Yes	None

FAQ

When did Thunder Client move git sync to Pro?

1. Free users lost .thunder-tests storage after updating.

Can I export my collections before migrating?

Yes. In Thunder Client, right-click a collection and export as JSON. Always export before switching tools.

Is REST Client harder to use?

It depends. If you prefer editing files and having versioned requests, it’s straightforward. If you rely on a GUI, expect an adjustment period.

Does Apidog store collections in my git repository?

No, Apidog stores collections in the cloud. For git-based storage, use REST Client.

Will Thunder Client free tier lose more features?

There’s no official announcement, but the move to paywalled git sync suggests the free tier could change again. For stability, consider migrating.

Fastest migration to Apidog?

Export from Thunder Client, create a free Apidog account, import your JSON, and install the VS Code extension. Most migrations take under 30 minutes.

---

Thunder Client’s free tier no longer supports git-based collections. For a file-based workflow, use REST Client. For cloud sync and team sharing, Apidog offers what Thunder Client once did—choose based on your team’s needs.