CAPTCHA Types Guide: Choosing the Right Solver for Your Task

Not all CAPTCHAs are equal. Some are solved in a split second by a checkbox; others require a full challenge token. Choosing the right solving strategy depends on the CAPTCHA you are facing and what your automation needs. This article compares the common types and when to use each.

reCAPTCHA v2

Google's most widespread CAPTCHA. It shows a checkbox and, when Google suspects a bot, expands into an image grid.

• Payload: sitekey + page URL.
• Type code: 4.
• Typical solve time: 2-10 seconds.
• Best for: most public websites, login forms, registration flows.

reCAPTCHA v3

Fully invisible. Google scores the page visitor from 0.0 to 1.0 and the site decides whether to act on the score.

• Payload: sitekey + page URL + action (if required).
• Type code: 5.
• Typical solve time: 1-3 seconds.
• Best for: sites that gate actions by score rather than showing a challenge.

hCaptcha

Privacy-focused alternative used heavily outside Google's ecosystem, with a distinctive pixel-art grid challenge.

• Payload: sitekey + page URL.
• Type code: 7.
• Typical solve time: 3-15 seconds.
• Best for: sites that intentionally avoid Google, plus many image-protected forums.

Cloudflare Turnstile

Cloudflare's modern alternative. It can run invisibly, show a checkbox, or require interaction only when suspicious.

• Payload: sitekey + page URL.
• Type code: 12.
• Typical solve time: 1-5 seconds.
• Best for: any site behind Cloudflare, including the majority of high-traffic sites.

GeeTest (v3 and v4)

A sliding-puzzle CAPTCHA very common on Chinese and international platforms. v3 uses a challenge object; v4 uses a captcha_id and often an action.

• Payload v3: gt + challenge + page URL. Type code 8.
• Payload v4: captcha_id + action + page URL. Type code 9.
• Typical solve time: 3-10 seconds.
• Best for: e-commerce platforms, game sites, and sites targeting the Asian market.

DataDome

An anti-bot protection layer that issues complex challenges, not just a CAPTCHA. It is used by high-traffic e-commerce and ticketing sites.

• Payload: page URL + captcha URL.
• Type code: 21.
• Typical solve time: variable, often longer.
• Best for: aggressively protected sites where standard CAPTCHAs do not appear.

Choosing the Right One

Ask three questions:

1. What does the site actually show? Inspect the network tab and look for g-recaptcha-response, cf-turnstile-response, h-captcha-response, or the GeeTest widget.
2. Does it need a token or text? Token CAPTCHAs need you to inject the answer into a hidden form field. Image CAPTCHAs just give you text to type.
3. How much latency can you afford? If your workflow can spare 15 seconds, human-assisted solving gives near-perfect accuracy. If you need instant answers, prioritize AI-solved types.

Key Takeaways

• Each CAPTCHA provider has a distinct payload and type code.
• Inspect the page to identify which provider you are dealing with.
• Match your latency budget to the solving strategy.
• The right choice is a balance of speed, cost, and accuracy for the site you target.

The next article shows how to integrate solving into browser automation with Selenium, Playwright, and Puppeteer.