Thunder Client Pro Paywall: What Changed and Your Best Alternatives

TL;DR

Thunder Client moved git sync – the feature that stored your collections as JSON files in your project – behind a Pro paywall. Free users can still send requests, but their collections no longer live in git by default. Your best alternatives are REST Client (free, file-based), Apidog (free workspace with cloud sync), and for existing users, staying on an older Thunder Client version with limited support.

Introduction

Thunder Client built its reputation on being the lightweight, free, git-friendly API client inside VS Code. Developers adopted it because it stored collections as JSON files in their project directory, which meant API requests could live in source control alongside the code they tested.

When Thunder Client introduced its Pro tier and moved git sync to paid, it changed the core value proposition that made the tool popular. This article covers exactly what changed, what free users lost, and the migration paths available in 2026.

The timeline: how the paywall happened

Thunder Client launched as a fully free VS Code extension. The original model stored collections as JSON files in a .thunder-tests directory inside your project. These files committed to git naturally and worked well in team environments.

As Thunder Client grew, the development team introduced a Pro tier to fund continued development. The features that moved to Pro were:

Git sync: The ability to store collections as JSON files in your project directory. This is the most significant change. Free-tier users now have their collections stored in VS Code’s extension storage, not in their project.

Team sharing: Sharing collections with teammates through git-based workflows.

CLI runner: Running collections from the command line for CI/CD pipelines.

The free tier retained basic request sending, local collections, and environment variables. For developers who only used Thunder Client for ad-hoc testing, the change was not immediately painful. For developers who had collections committed to their repositories, the change meant either paying for Pro or losing the workflow.

What free users actually lost

If you were on the free tier before the paywall and updated Thunder Client, here is what changed:

Collection storage location: Before, collections lived in your project directory as JSON files. After, collections moved to VS Code’s internal extension storage. This means collections are:

• Not visible in your project file explorer
• Not included when you run git add
• Not accessible to teammates who clone your repository
• Tied to your local VS Code installation

Git history: Previously, you could see who changed a request and when. That history disappears when collections move out of git.

Code review integration: API collection changes can no longer be reviewed as part of a pull request. A team member adding a new endpoint to your API and updating the corresponding Thunder Client collection used to be one commit. Now it requires a manual export/import cycle or paying for Pro.

Option 1: Stay on an older Thunder Client version

Technically possible, practically limited. VS Code sometimes installs extension updates automatically. You can disable auto-updates for a specific extension by right-clicking it in the extensions panel and selecting “Disable Auto Update,” then installing a specific version by downloading the .vsix file from the extension’s release history.

The problems with this approach:

• Older versions do not receive bug fixes or security patches
• VS Code updates may break compatibility with older extension versions
• This is a maintenance burden, not a long-term solution
• The Thunder Client team may change storage formats, making old versions less useful over time

This option buys time but is not a sustainable migration path.

Option 2: Switch to REST Client

REST Client by Huachao Mao is the most popular VS Code HTTP extension and the cleanest replacement for Thunder Client’s git sync workflow.

REST Client uses .http files – plain text files you create in your project. A request looks like:

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

You save this file in your repository. Anyone who clones the repo has the request. It diffs cleanly in git, shows up in code review, and requires no paid plan.

Migration steps:

1. Install the REST Client extension (search “REST Client” by Huachao Mao in VS Code marketplace)
2. Export your Thunder Client collections as JSON (this still works on the free tier)
3. Manually recreate your most important requests as .http files
4. Delete or archive the Thunder Client collections you no longer need

There is no automated migration tool that converts Thunder Client JSON to .http format perfectly, but for most collections the conversion is straightforward.

What you give up: REST Client has no GUI. You write requests by hand in text format. For developers used to clicking through Thunder Client’s tabbed interface, this is a workflow shift.

Option 3: Switch to Apidog

Apidog offers a free workspace that solves the same problem git sync solved in Thunder Client, without the friction of plain-text files.

The Apidog VS Code extension connects your editor to an Apidog cloud workspace. Your collections live in Apidog’s cloud and sync across devices automatically. The free tier supports up to three users, meaning small teams get shared collections without paying anything.

Migration steps:

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

What you gain over Thunder Client free:

• Cloud sync across all your machines
• Team sharing with up to three users free
• Request history and API documentation
• A desktop app that shares the same workspace as the VS Code extension

What you give up: Collections are in Apidog’s cloud, not in your local git repository as plain text. If you need collections in git for compliance or offline access, REST Client is a better fit.

Comparing the migration paths

FAQ

When exactly did Thunder Client move git sync to Pro?Thunder Client introduced the Pro tier and moved git sync during 2023. Users on the free tier lost the .thunder-tests directory storage with extension updates after this change.

Can I export my Thunder Client collections before switching?Yes. The free tier still allows exporting collections as JSON. Go to the Thunder Client panel, right-click a collection, and export. Do this before switching tools so you have a backup.

Is REST Client harder to use than Thunder Client?It depends on your workflow. If you are comfortable writing configuration files and enjoy having requests as readable text, REST Client is not harder – just different. If you rely on clicking through a GUI, the transition takes adjustment.

Does Apidog store collections in my git repository?Apidog stores collections in the cloud, not in your local project directory. If you need collections in your git repository specifically (for offline use or compliance reasons), REST Client is a better fit.

Will Thunder Client’s free tier get worse over time?The Thunder Client team has not announced plans to reduce the free tier further. But the precedent of moving git sync to paid means the free tier could change again. Building on a paid tier or migrating to a more predictable free tool reduces this risk.

What is the fastest way to migrate from Thunder Client to Apidog?Export your collections from Thunder Client, create a free Apidog account, import the JSON, and install the VS Code extension. Most users can complete this in under 30 minutes.

The paywall changed Thunder Client’s position in the market. Both REST Client and Apidog offer what Thunder Client used to provide for free – just in different forms. The right choice depends on whether you want plain-text files or a cloud-synced workspace.