Chrome DevTools Network Tab for CAPTCHA Debugging

Chrome DevTools is the fastest way to extract CAPTCHA parameters from a page, monitor challenge loading, and verify that solved tokens are submitted correctly. The Network tab shows every request involved in the CAPTCHA lifecycle.

What You Can Find with DevTools

Finding CAPTCHA Parameters

Opening DevTools

1. Navigate to the page with the CAPTCHA
2. Press F12 or Ctrl+Shift+I (Windows/Linux) / Cmd+Option+I (macOS)
3. Click the Network tab
4. Reload the page (Ctrl+R) to capture all requests from the start

Extracting reCAPTCHA Sitekey

Filter the Network tab to find the reCAPTCHA initialization:

1. In the filter box, type recaptcha
2. Look for a request to google.com/recaptcha/api2/anchor or google.com/recaptcha/enterprise/anchor
3. Click the request and check the Query String Parameters
4. The k parameter is the sitekey

Request URL: https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LcR_RsTAAAAACHE...&co=aHR0c...
                                                              ^^^^^^^^^^^^^^^^
                                                              This is the sitekey

Alternative — Console tab:

// Find reCAPTCHA sitekey from the page DOM
document.querySelector('[data-sitekey]')?.getAttribute('data-sitekey')
// or
document.querySelector('.g-recaptcha')?.getAttribute('data-sitekey')

Extracting Turnstile Sitekey

1. Filter Network tab for challenges.cloudflare.com
2. Look for the Turnstile script loading request
3. Check the page source for the sitekey:

// Find Turnstile sitekey from the page DOM
document.querySelector('[data-sitekey]')?.getAttribute('data-sitekey')
// or check the turnstile render call
document.querySelector('.cf-turnstile')?.getAttribute('data-sitekey')

Extracting hCaptcha Sitekey

1. Filter Network tab for hcaptcha.com
2. Look for requests to hcaptcha.com/checksiteconfig
3. The sitekey parameter is in the query string:

// Find hCaptcha sitekey
document.querySelector('[data-sitekey]')?.getAttribute('data-sitekey')
// or
document.querySelector('.h-captcha')?.getAttribute('data-sitekey')

Monitoring the CAPTCHA Lifecycle

reCAPTCHA Request Sequence

With the Network tab open, interact with the CAPTCHA and watch these requests:

Turnstile Request Sequence

Verifying Token Injection

After solving a CAPTCHA (manually or via API), verify the token is injected correctly:

Check the Hidden Input

// reCAPTCHA token
document.querySelector('#g-recaptcha-response')?.value
// or
document.querySelector('[name="g-recaptcha-response"]')?.value

// Turnstile token
document.querySelector('[name="cf-turnstile-response"]')?.value

// hCaptcha token
document.querySelector('[name="h-captcha-response"]')?.value

Watch the Form Submission

1. Keep the Network tab open
2. Submit the form
3. Click the POST request
4. Check the Payload tab (or Form Data)
5. Verify the token field is present and non-empty

If the field is empty or missing, your token injection failed.

Debugging Common Issues

Token Not Appearing in Form Submission

Use the Console to check if the token was set:

// Check if textarea exists and has a value
const textarea = document.querySelector('#g-recaptcha-response');
console.log('Exists:', !!textarea);
console.log('Value length:', textarea?.value?.length);
console.log('Display:', textarea?.style.display);

Common causes:

• Token injected into wrong element (multiple reCAPTCHA instances on page)
• Token expired before form submission (reCAPTCHA tokens expire in ~120 seconds)
• JavaScript validation re-triggers CAPTCHA after injection

CAPTCHA Widget Not Loading

Check the Console tab for errors:

reCAPTCHA v3 Score Verification

For reCAPTCHA v3, watch the Network tab after token generation:

1. Filter for the site's backend endpoint that verifies the token
2. Check the response from Google's siteverify endpoint (if proxied through the backend)
3. Look for the score field in the response

Using the Preserve Log Feature

By default, the Network tab clears on page navigation. For CAPTCHA workflows that redirect after submission:

1. Check Preserve log at the top of the Network tab
2. Now requests persist across page loads
3. You can see both the form submission and the redirect response

Copying Requests for Reproduction

Right-click any Network request for export options:

Example — Copy a CAPTCHA verification request as cURL:

curl 'https://example.com/submit' \
  -H 'content-type: application/x-www-form-urlencoded' \
  --data-raw 'name=test&email=test%40test.com&g-recaptcha-response=TOKEN_HERE'

This helps reproduce issues outside the browser.

Performance Timing

The Timing subtab for each request shows:

If CAPTCHA widgets load slowly, check whether the bottleneck is DNS, connection, or server response.

Troubleshooting

FAQ

Can I solve CAPTCHAs directly from DevTools?

You can inject a solved token into the DOM using the Console, but you can't solve the CAPTCHA challenge itself from DevTools. Use CaptchaAI to get the token, then inject it via Console for testing.

Does opening DevTools affect CAPTCHA behavior?

Some CAPTCHA providers detect DevTools presence through timing or debugger detection. reCAPTCHA v3 may assign a lower score when DevTools is open. For production debugging, use a proxy tool like Fiddler instead.

How do I find parameters for CAPTCHAs loaded in Shadow DOM?

Shadow DOM encapsulates CAPTCHA elements. In Console, use: document.querySelector('element-tag').shadowRoot.querySelector('[data-sitekey]') to access elements inside shadow roots.

Related Articles

• Chrome Devtools Protocol Captchaai

Next Steps

Once you've extracted the CAPTCHA parameters, submit them to CaptchaAI for solving. The API returns a token you can inject using the same Console techniques shown above.

Related guides:

• Using Fiddler to Inspect CaptchaAI API Traffic
• HTTP Replay for CAPTCHA API Debugging
• CaptchaAI Error Codes Reference