GeeTest Captcha Bypass - Automatic Solver

GeeTest protects sites with interactive puzzles - most commonly a slider you drag into place - backed by behavioral analysis of the drag itself. Surfsky solves GeeTest v4 with Captcha.solve or Captcha.autoSolve, and each solve is charged. GeeTest v3 is not solved.

Before you start

Start a browser and create a page-level cdp session as in the CAPTCHA setup example.

Manual captcha solving

Send Captcha.solve once the widget is on the page:

cdp = await page.context.new_cdp_session(page)
result = await cdp.send("Captcha.solve", {"type": "geetest"})
print(result["status"], result.get("usage"))

const cdp = await page.context().newCDPSession(page);
const result = await cdp.send("Captcha.solve", { type: "geetest" });
console.log(result.status, result.usage);

result = await browser.send("Captcha.solve", {"type": "geetest"})
print(result["status"], result.get("usage"))

const result = await browser.send("Captcha.solve", { type: "geetest" });
console.log(result.status, result.usage);

success means the widget passed; the site checks it when the form is sent, so wait for the protected content. solution holds the token as a JSON string, for a client that sends the form itself. Every GeeTest v4 kind is solved.

Automatic captcha solving

Use the Playwright or Puppeteer lifecycle. Create a page-level CDP session and attach listeners before enabling automatic mode with "geetest" in types:

cdp = await page.context.new_cdp_session(page)
cdp.on("Captcha.solveCompleted", lambda event: print("Completed:", event))
cdp.on("Captcha.solveFailed", lambda event: print("Failed:", event))
await cdp.send("Captcha.autoSolve", {"types": ["geetest"]})
await page.goto(target_url, wait_until="domcontentloaded")

const cdp = await page.context().newCDPSession(page);
cdp.on("Captcha.solveCompleted", event => console.log("Completed:", event));
cdp.on("Captcha.solveFailed", event => console.error("Failed:", event));
await cdp.send("Captcha.autoSolve", { types: ["geetest"] });
await page.goto(targetUrl, { waitUntil: "domcontentloaded" });

browser.cdp.on("Captcha.solveCompleted", lambda event, _: print("Completed:", event))
browser.cdp.on("Captcha.solveFailed", lambda event, _: print("Failed:", event))
await browser.send("Captcha.autoSolve", {"types": ["geetest"]})
await browser.goto(target_url, wait_until="domcontentloaded")

browser.cdp.on("Captcha.solveCompleted", (event) => console.log("Completed:", event));
browser.cdp.on("Captcha.solveFailed", (event) => console.error("Failed:", event));
await browser.send("Captcha.autoSolve", { types: ["geetest"] });
await browser.goto(targetUrl, { waitUntil: "domcontentloaded" });

Replace the target URL with your page. Add a bounded wait for the form result or protected content after navigation. {"status": "started"} only confirms that automatic mode started.

Understanding GeeTest challenge types

GeeTest ships two active generations with different bypass considerations:

v3 — the page loads a gt and challenge parameter pair; the classic version.
v4 — the page loads only a captcha_id with scripts served from /v4/ paths; adds more challenge variants and encrypts interaction data into a signed payload before validation.

Within either version, the widget itself can present as more than a slider:

Type	What it asks for
Slider puzzle	Drag a puzzle piece into a cutout in a background image
Icon CAPTCHA	Click or drag icons matching a shown condition
IconCrush (v4 only)	Match-three style board with matching symbols
Gobang / Space	Board or coordinate placement variants
OneTap / no challenge	A single “Verify” click, or no visible widget at all, when GeeTest already trusts the session from prior signals

See Manual captcha solving for the kinds that are answered.

Verify bypass worked

Check the challenge version and the actual page flow. A GeeTest widget may appear only after a form action. Start the automatic solver before that action, then wait for the site to accept the result. Keep the CDP connection open while solving. Avoid running a second solver against the same challenge. If verification completes but the page is still blocked, inspect the next network response or form validation error.

Troubleshooting

If nothing happens, confirm that "geetest" is in types and the challenge is present. Observe failure events before retrying. See CAPTCHA troubleshooting for shared errors and DevTools to inspect a running attempt. Stop the browser after the job completes.

GeeTest bypass FAQ

Can I send GeeTest to Captcha.solve for manual solving?

Yes, for GeeTest v4.

How do I know if a site is running GeeTest v3 or v4?

Check the page source or network requests. If you see a gt and challenge parameter pair, it’s v3. If you only see captcha_id with scripts loading from /v4/ paths, it’s v4. Only v4 is solved.

Why didn't the GeeTest widget appear at all?

Why does {'status': 'started'} not mean the job succeeded?

It only confirms automatic mode began — not that a challenge was found, solved, or accepted. Attach Captcha.solveCompleted and Captcha.solveFailed listeners and wait for the actual page result before treating the job as done.

Questions? Contact support.

Get started

Connect your tools

Browser sessions

Browser actions

CAPTCHA guides

Debugging

Performance and limits

About Surfsky

GeeTest Captcha Bypass - Automatic Solver

Before you start

Manual captcha solving

Automatic captcha solving

Understanding GeeTest challenge types

Verify bypass worked

Troubleshooting

GeeTest bypass FAQ

​Before you start

​Manual captcha solving

​Automatic captcha solving

​Understanding GeeTest challenge types

​Verify bypass worked

​Troubleshooting

​GeeTest bypass FAQ

Before you start

Manual captcha solving

Automatic captcha solving

Understanding GeeTest challenge types

Verify bypass worked

Troubleshooting

GeeTest bypass FAQ