NoneCap
How to solve hCaptcha automatically.
There are two different questions hiding in this search. One is from people who meet hCaptcha while browsing and are tired of clicking buses. The other is from developers whose script stops at a captcha. The answer depends on which one you are, so this page covers both.
| In your own browser | In a script or bot | |
|---|---|---|
| Tool | The NoneCap Chrome extension | The NoneCap API or an official SDK |
| Setup | Install from the Chrome Web Store | An API key and a few lines of code |
| Account | None for 100 free solves a day | Needed for the API key |
| What it does | Clicks through the challenge on the page you are viewing | Returns a token your code submits with the form |
| Good for | Everyday browsing, forms, logins | Scrapers, test suites, monitoring, agents |
In your own browser: install an extension
If you see hCaptcha on sites you use by hand, a browser extension is the simplest route. The NoneCap Chrome extension waits for an hCaptcha challenge to open and then solves it on the page, moving the cursor and clicking the way you would. Setup takes a minute:
- Add NoneCap from the Chrome Web Store.
- Open a site that shows hCaptcha. When the challenge appears, the extension starts on it.
- Use the extension's menu to pause it on a site, or add sites to a blocklist where it should never run.
You get 100 free solves a day without an account. Each challenge round counts as one, so a site that serves two rounds uses two. If you need more, you can add a NoneCap API key in the options and keep going on your account balance.
Chrome shows a banner saying the extension "started debugging this browser" while it solves. That is expected: drag and point puzzles ignore ordinary scripted clicks, so the extension uses Chrome's debugger permission to send real mouse input, and it detaches as soon as the attempt ends. It sends only the challenge area of the screen, and only while a challenge is open. The extension privacy policy spells it out.
In code: request a token
A scraper, test suite or agent has no one to click the tiles, and an
extension is the wrong tool there. Code solves hCaptcha by asking a solving
service for a token. Your script reads the
sitekey from the page, sends it with
the page URL to the NoneCap API, and gets back a P1_ token. It
puts that token in the form's h-captcha-response field and
submits. The site treats it as a normal pass.
The API reference documents the request, and there are guides for Python, Node.js, Golang, Selenium, Playwright and Puppeteer. Tokens expire after about two minutes, so request one right before you submit; the token guide covers the details.
What doesn't work any more
Older guides point at shortcuts that have stopped working. The hCaptcha accessibility cookie used to skip challenges, but it now needs an SMS check, expires daily and often isn't sent by modern browsers; the accessibility cookie guide has the history. Buster, the popular free extension, solves reCAPTCHA's audio challenge and does nothing on hCaptcha. Stealth browser plugins can lower how often challenges appear for a while, but no setup prevents them on a site that challenges everyone, which is why the reliable approach is to solve whatever shows up.
Last updated October 2026.