CAPTCHA Solving Services Compared

How solving services work

A solving service sits between your client and the challenge. Your code sends the challenge details to the service's API, the service returns a solution, and your code submits it to the site.

There are two kinds of output. For image and text challenges, the service returns the characters or the positions to click. For token challenges such as reCAPTCHA and Cloudflare Turnstile, it returns a token, the string the site's own script would have produced, and your client submits it with the form.

Services also differ in who solves. Anti-Captcha states that all of its captchas are solved by human workers (Anti-Captcha). CapSolver and CaptchaAI describe themselves as AI-based (CapSolver; CaptchaAI pricing). Others do not say on their price pages. The distinction matters less than results on your target, which you should measure yourself.

Score-based systems change the picture. Google documents that reCAPTCHA v3 returns a score from 0.0 to 1.0 for each request, where 1.0 is very likely a good interaction and 0.0 is very likely a bot, with 0.5 as a suggested default threshold (reCAPTCHA v3 documentation). Cloudflare describes Turnstile as running small non-interactive JavaScript challenges to gather signals, with a managed mode that shows a checkbox only to visitors it rates as higher risk (Cloudflare Turnstile documentation). In both cases, whether you see a challenge at all depends on your session.

Prices from public price lists

Sources: 2Captcha pricing, Anti-Captcha, CapSolver, CapMonster Cloud prices, CaptchaAI pricing and NextCaptcha. 2Captcha listed its prices in euros on the day we checked, shown here as EUR. We did not measure success rates or solve times; the pages list their own figures, which we do not repeat.

We have reviewed several of these services: CaptchaAI and NextCaptcha, plus CaptchaSonic, NoCaptchaAI and OMOcaptcha, which are not in the table.

Per solve or by threads

Per-solve pricing is simple: you pay for what you use, and the price depends on the challenge type. It suits uneven volume and mixed challenge types.

Thread-based pricing, as CaptchaAI sells it, charges a flat monthly fee for a number of concurrent solving slots, with no limit on the number of solves. Its page says requests beyond your thread count are refused until a slot frees up. It suits high, steady volume where you can keep the threads busy.

To compare, estimate monthly solves by type and price them per 1,000 on each service, then compare with the thread plan that covers your peak concurrency. Check whether a service charges for every solution it returns or offers a way to report and recover the cost of ones the site rejects, because a high rejection rate on your target raises the effective price of each useful solve. Track accepted solutions, not just requests, and compare services on cost per accepted solution over a full week. At low volume, per-solve wins. At high, steady volume, threads can win, as long as your peak does not need more slots than you pay for.

Challenge types to check

Before choosing, list the challenges you actually meet and confirm each service supports them. The common ones are image and text CAPTCHAs, reCAPTCHA v2 checkbox and invisible variants, reCAPTCHA v3 and its Enterprise edition, Cloudflare Turnstile, AWS WAF challenges and GeeTest. CapSolver lists AWS WAF; CaptchaAI lists reCAPTCHA Enterprise, Cloudflare Challenge and GeeTest v3 among others; Anti-Captcha and 2Captcha list the main token types alongside image challenges.

Note that reCAPTCHA v3 prices on some services depend on the score you need. 2Captcha and Anti-Captcha both price v3 by score band on their pages. A token that carries a low score may be accepted by the solver's check and still rejected by the site, which brings the next section into focus.

Fewer challenges first: the IP and the browser

Every solved challenge costs money and time. The cheaper path is to meet fewer of them, and the inputs that decide that are under your control.

The network. Score-based systems weigh where a request comes from. Hosting ranges and addresses with abuse history start with a worse record. A carrier address, shared with ordinary subscribers through carrier-grade NAT, starts from the same record as everyday phone users. It is not a pass, but it removes one cause of extra challenges.

The browser. A headless browser with default settings, or a client whose fingerprint does not match the browser it claims to be, attracts challenges on any network. Use a real browser profile and keep it consistent.

Behavior. Steady pacing, normal navigation and loading the page's own resources all count toward the session's score.

The arithmetic is direct. Monthly solving cost equals pages loaded, times the share of pages that show a challenge, times the price per solve, plus retries for solutions the site rejects. Halving the challenge share halves the bill, whatever the solver costs.

For the network layer, a dedicated mobile line gives each browser profile a stable carrier exit. Compare countries and carriers on the mobile proxies overview, and see our guide to Cloudflare blocks and challenge loops for diagnosing repeated challenges.

A worked cost example

Here is the arithmetic with round, illustrative numbers rather than measured ones. Suppose a workflow loads 200,000 pages a month and the solver charges $1.00 per 1,000 token solves.

If 20% of page loads show a challenge, that is 40,000 solves, or $40.00 a month, before retries. If one solution in ten is rejected and must be solved again, add another 4,000 solves and $4.00.

Now suppose a cleaner setup, with a consistent browser profile, a carrier exit and slower pacing, cuts the challenge share to 5%. The same month needs 10,000 solves, or $10.00, and fewer rejections because the sessions score better.

The point is not the exact figures, which you should replace with your own logs. It is that the challenge share multiplies every other number, so it is usually the first thing worth improving.

Choosing in three steps

1. List your challenges. Log a week of challenges by type: image, reCAPTCHA v2, v3, Turnstile, AWS WAF or others. Drop any service that does not support your main types.
2. Price your mix. Multiply each type's monthly count by each service's price per 1,000, and compare the total with a thread plan sized for your peak concurrency.
3. Run a short test. Fund the two cheapest candidates with a small balance and send them the same challenges for a few days. Keep the one whose solutions your target accepts most often.

Then go back to the challenge share and work on reducing it. A solver is a cost of the challenges you cannot avoid, so the less often you need it, the less its price matters.

Integration in practice

Most services expose a similar flow: create a task with the challenge type, the page URL and the site key; poll for the result; submit the result with your form or request. Several also offer browser extensions that solve in the page.

Two practical points save trouble. Send the solver the same context your browser has, especially the page URL and, where supported, the proxy, so the token is tied to a consistent session. And log every challenge with its type, the solver's response time and whether the site accepted the result. Without that log you cannot tell whether a rising bill comes from more challenges, more rejections or a price change.

Terms and law

CAPTCHAs exist because site owners want to limit automated access. Solving them through a service can breach a site's terms of service even when the data itself is public, and computer misuse and anti-fraud laws differ by country. Read the terms of the sites you work with and take advice where it matters. Never use solvers for fraud, spam or other illegal activity.

How we checked

Prices, models and supported types come from each service's own pricing or home page, read on 30 October 2026. reCAPTCHA and Turnstile behavior is taken from Google's and Cloudflare's documentation. We did not test any solver and report no accuracy or speed figures. Some of these services are Coronium partners with reviews on this site.

Frequently asked questions