What Is a CAPTCHA Solver? How a Task Flows, Step by Step

A CAPTCHA solver is a tool that takes a CAPTCHA challenge and hands back what the form needs to accept it: a text answer, a token or a cookie. So what is a captcha solver in practice? It is the part of an automation that your script calls when a page asks for proof of a person. You send it the details of the challenge, wait, and get a value to put into the form. This guide covers the three ways solvers are delivered, the four steps every task follows, what comes back, and how to choose.
If you want the widget side, what a CAPTCHA is and why sites use one, start with what a CAPTCHA is and how it works. This guide starts where that one ends.
What a CAPTCHA solver does
A solver does one job: it produces the output a human would have produced. It doesn’t change the page, it doesn’t log in for you and it doesn’t decide what the site does next. Your script still loads the page, finds the challenge, submits the form and reads the reply.
What is a captcha solver made of? Three delivery shapes
Every solver is one of three shapes, and the shape decides cost, speed and where your data goes.
| Shape | Where the solving happens | How you pay | How you call it |
|---|---|---|---|
| Remote service | On the vendor’s servers, by workers or models | Per solve, billed against a balance | An HTTP API from your own code |
| Browser extension | Depends on the product: it can call a remote service or a program on your PC | Depends on the product | No code, it works inside your browser tabs |
| Local solver | On your own machine | A flat license, no per-solve fee | A local HTTP API, SDKs, or a companion extension |
A remote service bills per solve, so its cost grows with every challenge you send. A comparison of ten solving services lays out the architectures and the dated rates, so this guide doesn’t rank anyone.
CapSkip is the local shape. It is a Windows application that listens on 127.0.0.1:8080, solves on your own hardware and charges one flat license. Its Chrome and Firefox extension talks to that same app, so one install covers both the no-code and the scripted route.
The four steps of every task
Almost every solver, remote or local, runs the same cycle. Submit, poll, take the result, inject it.
- Submit. Send the challenge details to the solver: the method, the site key and the full page address. You get back a job id.
- Poll. Ask for the result with that id. While the job is running the solver answers that it isn’t ready.
- Take the result. When it is ready you get the token. CapSkip delivers each result once, so keep it from the reply that carried it.
- Inject. Place the value in the form field that the widget itself would normally fill, then submit the form before it expires.
CapSkip speaks the 2captcha-style API, so the first two steps are two HTTP calls. Here is a reCAPTCHA v2 task by hand, with the placeholders you replace. The method name and every parameter come from the API documentation.
# 1. Submit. CapSkip answers with the job id.
curl.exe -X POST -d "key=YOUR_API_KEY&method=userrecaptcha&googlekey=YOUR_SITEKEY&pageurl=https://example.com/login&json=1" http://127.0.0.1:8080/in.php
# {"status":1,"request":"12345"}
# 2. Poll with that id until the token is ready.
curl.exe "http://127.0.0.1:8080/res.php?key=YOUR_API_KEY&action=get&id=12345&json=1"
# {"status":0,"request":"CAPCHA_NOT_READY"} means wait 5 seconds and poll again.
# {"status":1,"request":"03AHJ_Vuve5Asa4...","userAgent":"Mozilla/5.0 ..."}These are one-line curl.exe calls, so they run as written in Windows PowerShell and in cmd. In cmd, skip the lines that start with a hash, which PowerShell treats as comments. If the key is wrong on a server with API key validation on, CapSkip returns an error code instead of a job id. For a reCAPTCHA v2 task the documentation says to wait 15 to 20 seconds before the first poll, and to wait 5 seconds and ask again if the answer is that the job isn’t ready. An empty reply means the result was already read or the id doesn’t exist. The JSON reply carries a userAgent value. Send that User-Agent when you submit the form, because some sites compare it with the one the token was earned with.
Doing it in code
The official SDKs for Python, Node.js, PHP and .NET wrap the submit and poll loop in one call. The same task in Python, ending with the inject step, looks like this.
# pip install capskip requests
import requests
from capskip import CapSkip
PAGE = "https://example.com/login"
solver = CapSkip(apiKey="YOUR_API_KEY", host="127.0.0.1", port=8080)
# One call: the SDK submits the task and polls until the token is ready.
# poll_json=1 asks for the JSON poll, which adds the userAgent value.
result = solver.recaptcha(sitekey="YOUR_SITEKEY", url=PAGE, poll_json=1)
# Inject: send the token in the field the widget would have filled,
# with the User-Agent the token was earned with.
reply = requests.post(
PAGE,
data={"username": "alice", "g-recaptcha-response": result["code"]},
headers={"User-Agent": result["userAgent"]},
)
print(reply.status_code)The API key only matters when API key validation is switched on in CapSkip. Without poll_json=1 the SDK polls in plain text and the result holds the token but no userAgent value. The API docs leave that value out when no User-Agent is available, so check for it if a site compares User-Agents. The SDK page lists the methods for every language and challenge type.
What comes back, and where it goes
Google’s documentation says the reCAPTCHA token reaches your server as the g-recaptcha-response parameter when the form is submitted, and that your server then verifies it with Google. Each token is valid for two minutes and can be verified once. Cloudflare’s server-side validation guide describes the same arrangement for Turnstile: the cf-turnstile-response field, a 300 second lifetime and tokens meant for single use. The site’s own server does the checking. That’s why a solver has to return a real token rather than anything you could type in.
| Challenge | What the solver returns | Where it goes |
|---|---|---|
| Text image | The characters read from the picture | The text box beside the image |
| reCAPTCHA v2, v3, Enterprise | A token | g-recaptcha-response |
| Cloudflare Turnstile widget | A token | cf-turnstile-response |
| MTCaptcha | A token | mtcaptcha-verifiedtoken, as named in the CapSkip API docs |
| GeeTest v3 | Three values | Form fields geetest_challenge, geetest_validate, geetest_seccode |
| DataDome | A cookie | Your next requests to the site, with the same IP and User-Agent |
| AWS WAF | Values that become a token, sent as a cookie | aws-waf-token |
Each row is proof that the challenge was passed, in the place the site looks for it. The request fields for each type are in the API docs.
What a captcha solver can’t do
- It can’t make a site accept the result. Tokens are checked by the site’s own server, and a stale or reused one is refused.
- It can’t cover every challenge. CapSkip lists the types it supports, and its homepage FAQ says plainly that it doesn’t solve FunCaptcha or Arkose. Check the list before you build around a solver.
- It can’t fix your network identity. Some tokens and cookies are tied to the IP address and User-Agent that earned them. Solving from one address and submitting from another can fail even with a perfect answer.
- It can’t settle whether you may use it. Whether solving is allowed depends on the site’s terms and your jurisdiction. See whether captcha solving is legal before you automate anything you don’t own.
How to choose a solver
Four questions settle most choices, and for a local solver each one maps to a real setting.
| Question | What it decides | In CapSkip |
|---|---|---|
| How many solves a month? | Per-solve billing against a flat license | One license, no per-solve fee, so a retry costs nothing extra |
| Where may the data go? | Remote service against solving on your own hardware | Solving runs on your Windows machine |
| Code or no code? | Extension against API or SDK | Extension, 2captcha-style API, or an SDK |
| How much runs at once? | Parallel tasks and addresses | Max. Threads per type, and a proxy list per type |
The setup guide describes Max. Threads as how many tasks of one type CapSkip solves at the same time, and recommends at least as many proxies as threads for the types that need them, so simultaneous tasks don’t share an address. Each type has its own row in the settings with its own threads, timeouts, retries and proxy list.
Running the solver on a server
Local mode listens only on the same computer. If your scripts run on another machine, switch the port setting to Server mode, so CapSkip accepts connections from your network or the internet, and use that machine’s address instead of 127.0.0.1. Server mode requires CapSkip to run as administrator, and a static public IP gives the most stable remote access for a server setup. The two modes are described under the connection settings in the setup guide. The server is still a Windows machine you control.
To keep the port reachable only from the machines you expect, add a Windows Firewall block rule for every other address.
FAQ
What is a captcha solver in simple terms?
A program or service that takes a CAPTCHA challenge and returns the answer, token or cookie the website expects. Your script submits the challenge details, waits for the result and puts it into the form.
Is a captcha solver a person or a program?
Both exist. Some services route challenges to paid workers, some use models, and some mix the two. With a local solver such as CapSkip the models run on your own machine, so no person is involved and nothing is uploaded.
Can a captcha solver run on a server instead of my PC?
Yes. Turn on Server mode in the connection settings, run CapSkip on a Windows machine you control, and point your scripts at its address. Add a firewall block rule for any address that shouldn’t reach it.
Does the solver click the checkbox for me?
Not through the API. The API returns a token and your code injects it. The browser extension is the route that fills the field and can press submit for you.
The short version
A solver turns a challenge into a value the site accepts, through four steps: submit, poll, take the result, inject. The shape you pick sets the cost and where your data goes. If you want that cycle to run on your own hardware with no meter running, an unlimited captcha solver that listens on your own machine and speaks the 2captcha-style API is the shape every example here used.
