How to Fix CAPTCHA Not Working on Websites

Start here: update your browser, enable JavaScript, temporarily disable extensions or plugins, reload the page, and try the CAPTCHA in another supported browser. Complete the challenge near the end of your form or checkout because verification can expire. If it fails only on one website, the site’s CAPTCHA integration may be misconfigured and its support team needs to investigate.

Identify the CAPTCHA failure

Symptom	Likely area	First action
CAPTCHA is not showing	Browser, JavaScript, extension, or blocked script	Update the browser, enable JavaScript, disable extensions temporarily, then reload
CAPTCHA keeps spinning	Connection, cookies, VPN, security software, or a site timeout	Try another supported browser and a different connection if available
Challenge expired	Too much time or inactivity	Select the checkbox again and finish the task promptly
“Computer or network may be sending automated queries”	Shared or suspicious IP reputation, or an attack on the destination site	Retry later and follow Google’s unusual-traffic guidance
Verification fails on one site only	Invalid key, unsupported domain, integration bug, or site outage	Contact that website’s support team

Fix a CAPTCHA that is not showing

Use a supported, current browser. Google lists the two latest major versions of Chrome, Firefox, Safari, and Chromium Edge on desktop. On mobile, its supported list includes Chrome, Safari, and the Android native browser; the version window changes as browsers update. See Google reCAPTCHA Help.
Enable JavaScript. CAPTCHA widgets require client-side scripts. Check the browser’s site settings, then reload the page.
Temporarily disable extensions and plugins. Content blockers, privacy tools, script managers, and security extensions can prevent the widget or challenge from loading. Disable them briefly, reload, and re-enable one at a time to find a conflict.
Allow required cookies. reCAPTCHA uses the _GRECAPTCHA cookie for risk analysis. If you block it, the site owner may need to use Google’s www.recaptcha.net endpoint where www.google.com is inaccessible; visitors should not change the site’s CAPTCHA code themselves. See the reCAPTCHA FAQ.
Reload without stale page state. Open a private window or clear cookies for the affected site, then load the form again.

Fix a CAPTCHA that is not loading or keeps spinning

Try another supported browser. This comparison helps show whether the problem follows one browser or remains site-specific; it is a diagnostic clue, not proof of a single cause.
Check the connection. A brief outage, unstable Wi-Fi, VPN, proxy, or security product can interrupt CAPTCHA requests.
Disable one suspected network or security control at a time, test, then restore anything unrelated. Chrome’s connection guidance lists cookies, extensions, memory pressure, unstable connectivity, VPNs, and security software among possible causes of loading errors (Chrome Help).
Try another network or device if available. If the same website fails everywhere while other sites work, treat it as a possible site integration or service problem.

Fix “challenge expired” and repeated verification

Verification can expire after inactivity or a timeout. Google reCAPTCHA Help displays the message Verification challenge expired, check the checkbox again for a new challenge. Select the checkbox again and complete the challenge close to the end of the form, payment, login, or submission. Avoid opening the page and leaving it idle while you gather information.

If reCAPTCHA repeatedly asks you to verify, check for a shared network, a recently assigned IP address with poor reputation, or an attack against the destination site. Google says legitimate users can see unusual-traffic warnings for these reasons; retry later and consult its unusual-traffic help.

When the website owner must fix it

Browser troubleshooting cannot correct a server-side integration error. Ask the site owner to check:

the site key and secret key are valid and belong to the correct environment;
the current hostname is listed as an allowed domain;
the CAPTCHA script, challenge requests, and callback requests are not blocked by the site’s content-security policy, proxy, firewall, or frontend code;
client-side requests are not timing out;
the verification token is sent to the server and verified before it expires;
the implementation matches the selected reCAPTCHA version and API.

Google documents invalid keys, unsupported domains, client-side network failures, and timeouts in its reCAPTCHA integration troubleshooting guide. Include the exact error text, browser and version, time, affected URL, and whether another browser works when contacting support. Do not send passwords or secret keys.

A practical isolation checklist

Record the exact symptom: missing widget, spinner, expired challenge, rejected answer, or unusual-traffic warning.
Update the browser and confirm JavaScript is enabled.
Disable extensions or plugins temporarily and reload.
Try another supported browser.
Try another device or network if available.
Compare another website that uses CAPTCHA.
If only one site fails, send the site owner the error details and test results.

Or skip the browser setup

If your goal is to capture a page for documentation, monitoring, or debugging rather than interact with its CAPTCHA, ScreenshotNeo provides a direct screenshot API. It can remove cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing result.

See the ScreenshotNeo API documentation for all options.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo also offers an MCP server for Claude, Cursor, and other MCP clients, so AI agents can call take_screenshot, get_page_info, and capture_pdf. The Free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000 shots. Capture only what you need, use a chosen cache TTL for repeat pages, and use async jobs or bulk capture for larger batches.

Create a free ScreenshotNeo account and get 1,000 screenshots per month with no card.

Performance, reliability, and cost notes

Finish interactive CAPTCHA challenges near submission time to avoid expiration.
For a site owner, set practical client and server timeouts and log provider errors without exposing secret keys.
Run one-variable tests: change browser, extension state, network, or device separately so the result is useful.
Do not buy hardware or a VPN expecting it to repair a site integration; the documented fixes are browser, network, retry, and support checks.
For automated screenshots, caching can reduce repeat work; ScreenshotNeo bills only clean shots and exposes billing status in headers.

FAQ

Why does CAPTCHA work in one browser but not another?

The failing browser may be outdated, have JavaScript disabled, or have an extension, cookie policy, or security control interfering with the widget. Compare settings and re-enable extensions individually.

Can clearing cookies solve CAPTCHA problems?

It can remove stale site state, but it will not fix an invalid key, unsupported domain, or broken integration. Clear cookies for the affected site, then test again.

Why am I seeing repeated challenges on a normal home connection?

Google says shared-network abuse, suspicious IP assignment, or an attack on the destination site can trigger unusual-traffic checks even for legitimate users. Retry later and follow Google’s guidance.

Should I change the CAPTCHA code as a visitor?

No. Endpoint and key changes belong to the website owner. Visitors should update the browser, check JavaScript and extensions, retry, and contact the site when the issue is site-specific.

What information should I give support?

Provide the exact message, affected URL, browser and version, approximate time, device, and whether another browser or network succeeded. Never include credentials or secret keys.