An hCaptcha solver extension for Chrome.

The VanishCaptcha extension watches for hCaptcha while you browse, asks the API for a token, and writes that token into the page. Connect an API key and solving runs on your balance. It sends the sitekey, the page URL, and rqdata when the widget has one — never the rest of the page.

Install unpacked ↓

What it does

Auto-solves hCaptcha as soon as the widget is on the page, when auto-solve is on.
Uses your API key for unlimited solving against the account balance. New accounts start with free credits.
Image challenges go through the same token API as the SDKs. Drag and audio challenges are not solved yet.
Per-site pause and a blocklist for sites where it should stay quiet.
A status pill next to the widget, and a popup that shows the key, monthly stats, and the detect → open → solve → verify steps.

Install

Load the unpacked extension. There is no Chrome Web Store listing yet.

Open the extension folder — the one that contains manifest.json.
Open chrome://extensions and turn on Developer mode.
Click Load unpacked and select that folder.
Open the popup, click Got it — start solving, and connect an nc_live_ key from the dashboard.

For a fresh automation profile, drop a provision.json next to the manifest, or open the provision URL with the key in the fragment. Both are described in the extension README.

How it works

The extension does not screenshot the challenge and it does not click inside the widget. A content script reads the sitekey (and rqdata on enterprise widgets) and sends those to POST /v1/solves. Recognition runs on VanishCaptcha's servers. The token that comes back is written into h-captcha-response and the widget callback, which is the same injection the solving guides do by hand.

The extension carries no solving model. It is a thin client over the API, with settings for auto-solve, animated or fast injection, the status overlay, and a list of domains to skip.

Privacy

A solve sends the captcha sitekey, the page URL, and optional rqdata. It does not send browsing history or page content outside the widget. The privacy policy covers the service; the extension options page links to it.

Prefer to call the API directly?

The extension is the no-code way to use VanishCaptcha while browsing. For a scraper or a browser you drive yourself, call the API from the Python or Node.js guide. The API reference has cURL, Python, Node, and Go.

Last updated October 2026.

Frequently asked

Do I need a VanishCaptcha account?

Yes. Solving uses an API key. Create one in the dashboard — new accounts include free credits — then paste it into the popup or the extension settings. The popup’s daily counter is the onboarding allowance; a solve itself runs on the connected key.

What does the extension send?

The sitekey, the page URL, and rqdata when the widget has it. It does not upload a screenshot of the challenge or of the page around it.

Which challenges can it solve?

hCaptcha image challenges, including enterprise widgets that carry rqdata. It does not solve reCAPTCHA, Cloudflare Turnstile, or FunCaptcha. Drag and audio hCaptcha types are marked Soon in settings and are not solved.

Why doesn’t Chrome show a debugging banner?

The extension never attaches the debugger. It injects the API token into the response field. Chrome’s “started debugging this browser” banner is what appears when an extension clicks inside the widget through the debugger API, which this one does not do.

Can I install it outside the Chrome Web Store?

That is the install path. Turn on Developer mode at chrome://extensions, choose Load unpacked, and select the folder that contains manifest.json.