Puppeteer Captcha Solver

Why Not puppeteer-extra-plugin-recaptcha?

The popular plugin runs solving logic inside the automated browser. That leaves a detectable footprint, breaks whenever Google ships a reCAPTCHA update, and struggles with Enterprise score-based challenges. A server-side solving API decouples you from the cat-and-mouse game: your bot just asks for a token and injects it — the same technique used by large-scale scraping teams.

Install

npm install puppeteer axios
# Recommended companion:
npm install puppeteer-extra puppeteer-extra-plugin-stealth

reCAPTCHA Token Flow in Node.js (Planned)

This flow goes live when reCAPTCHA support launches — see /recaptcha-solver. The image-captcha flow below works today.

const puppeteer = require('puppeteer-extra');
const StealthPlugin = require('puppeteer-extra-plugin-stealth');
const axios = require('axios');

puppeteer.use(StealthPlugin());

const API_KEY  = 'ck_your_api_key_here';
const PAGE_URL = 'https://example.com/register';

async function solveRecaptchaV2(sitekey, pageUrl) {
    const { data } = await axios.post('https://captchakings.com/api', {
        api_key: API_KEY,
        captcha_type: 'recaptcha_v2',
        sitekey: sitekey,
        page_url: pageUrl
    });
    if (!data.token) throw new Error('Solve failed: ' + JSON.stringify(data));
    return data.token;   // valid g-recaptcha-response (planned flow)
}

(async () => {
    const browser = await puppeteer.launch({ headless: 'new' });
    const page = await browser.newPage();
    await page.goto(PAGE_URL, { waitUntil: 'networkidle2' });

    // 1. Extract the sitekey
    const sitekey = await page.$eval('[data-sitekey]', el => el.dataset.sitekey);

    // 2. Solve server-side
    const token = await solveRecaptchaV2(sitekey, PAGE_URL);

    // 3. Inject + submit
    await page.evaluate((t) => {
        document.getElementById('g-recaptcha-response').innerHTML = t;
    }, token);
    await Promise.all([
        page.waitForNavigation({ waitUntil: 'networkidle2' }),
        page.click('button[type=submit]')
    ]);

    console.log('Passed:', page.url());
    await browser.close();
})();

Image & Text CAPTCHAs via Screenshot

const el = await page.$('#captcha-img');
await el.screenshot({ path: 'captcha.png' });

const FormData = require('form-data');
const fs = require('fs');
const form = new FormData();
form.append('captcha', fs.createReadStream('captcha.png'));
form.append('api_key', API_KEY);

const { data } = await axios.post('https://captchakings.com/api/process.php', form, {
    headers: form.getHeaders()
});
console.log('Answer:', data.prediction, '| confidence:', data.confidence);

Production Checklist for Puppeteer Bots

1. Stealth + solver, not stealth alone. Stealth reduces how often you're challenged; the solver handles the challenge when you are.
2. Match your proxy IP. The token is bound to the visiting IP. Route the browser through the same proxy you register with the solver — or use the CaptchaKings IP Rotator.
3. Cache sessions. Save page.cookies() after passing and reuse them; only re-solve when the session dies.
4. Never pay for failures. CaptchaKings only bills successful solves — report bad tokens for instant credit-back.

Cost at Scale

Flat pay-as-you-go rates — $0.80 per 1,000 image/text solves and $1.00 per 1,000 token solves. No volume tiers, no subscription.

Frequently Asked Questions

Does this work with puppeteer-extra-plugin-stealth?

Yes — it's the recommended pairing. Stealth masks automation signals while CaptchaKings clears the challenge server-side.

Can I use it with Puppeteer cluster / concurrent browsers?

Yes. The API is stateless and handles high concurrency, so puppeteer-cluster workers can request tokens in parallel without rate issues on paid plans.

What if the injected token gets rejected?

Report it via the API for an automatic refund, then request a new token — failed solves are never billed. Note: the reCAPTCHA token flow is planned, not yet live — see /supported-captchas and /recaptcha-solver.

Related Integration Guides