Troubleshooting
WPForms reCAPTCHA Not Working: Causes and How to Fix It

Short answer
WPForms reCAPTCHA usually fails because the keys do not match the selected reCAPTCHA type, your domain is missing from the key, another plugin loads its own reCAPTCHA, or caching delays the script. Check the CAPTCHA settings, turn on No-Conflict Mode and exclude reCAPTCHA scripts from optimisation.
Key takeaways
- Keys must match the reCAPTCHA type selected in WPForms settings.
- Every domain and subdomain must be listed for your key in Google.
- Enable reCAPTCHA on each form, not just in global settings.
- No-Conflict Mode stops other plugins loading duplicate reCAPTCHA scripts.
- Exclude reCAPTCHA scripts from JavaScript delay and defer options.
Why is WPForms reCAPTCHA not working?
WPForms reCAPTCHA usually fails because the keys do not match the reCAPTCHA type, the domain is not registered, another plugin loads a second reCAPTCHA script, or a cache or optimisation plugin breaks the script.
The symptoms vary. The checkbox may not appear at all, the form may refuse to submit, or you may see a message saying verification failed.
The good news is that almost every case comes down to settings, not code. Work through the checks below in order and test the form after each one.
If your form is not loading at all, not just the CAPTCHA, start with our guide on WPForms not loading instead.
Do your keys match the reCAPTCHA type?
Google issues separate keys for each reCAPTCHA type, so v2 keys will not work if WPForms is set to v3, and the reverse is also true.
This is the most common cause by far. Go to WPForms > Settings > CAPTCHA and check which type is selected:
- Checkbox reCAPTCHA v2 shows the familiar I'm not a robot box.
- Invisible reCAPTCHA v2 runs in the background and only shows a challenge when needed.
- reCAPTCHA v3 never shows a challenge and gives each visitor a score instead.
Now open the Google reCAPTCHA admin console and check the type of the key you created. If they differ, create a new key of the right type or change the WPForms setting to match.
Also check that you copied the site key and secret key into the right boxes. Swapping them is an easy mistake that stops verification every time.
WPForms explains the setup in its guide to setting up Google reCAPTCHA.
Is your domain registered for the key?
reCAPTCHA keys only work on the domains listed in the Google admin console, so a new domain, subdomain or staging site will fail until you add it.
Open your key's settings in the Google console and look at the Domains list. Add every domain where the form appears.
Common gaps include:
- The www and non-www versions of your site.
- A staging or development subdomain.
- A new domain after a site migration.
- A local development address.
Changes to the domain list can take a little time to apply. Test again after a few minutes.
Is reCAPTCHA turned on for the form?
Adding keys in the global settings is not enough, because you also have to enable reCAPTCHA on each form where you want it.
Open the form in the WPForms builder. Then either add the reCAPTCHA field from the field list, or go to Settings > Spam Protection and Security and turn on the Google reCAPTCHA option.
Save the form and reload the page where it is embedded. If the badge or checkbox now appears, that was the issue.
If you use a page builder, check that the page shows the same form you edited. It is easy to edit a copy while the page embeds an older form.
Is another plugin loading reCAPTCHA too?
When two plugins load their own copies of the reCAPTCHA script, they clash and neither works, which WPForms can fix with its No-Conflict Mode setting.
Themes, login security plugins, comment plugins and other form plugins often add reCAPTCHA. If the page loads two versions, the browser can only use one.
Go to WPForms > Settings > CAPTCHA and tick No-Conflict Mode. This stops other plugins from loading their reCAPTCHA scripts on pages with WPForms.
If that breaks reCAPTCHA in the other plugin, you may need to pick one plugin to handle CAPTCHA, or use a different CAPTCHA type in one of them. Our guide on fixing a plugin conflict shows how to find which plugin is involved.
Is caching or script optimisation breaking it?
Minify, combine, delay and defer options in cache plugins often break reCAPTCHA, because they change how and when Google's script loads.
Signs of this include reCAPTCHA working while you are logged in but failing for visitors, or the checkbox appearing only after a long delay.
Try these steps:
- Purge all caches and test in a private window.
- Turn off JavaScript delay or defer options and test again.
- If that fixes it, exclude recaptcha and wpforms scripts from those options.
- Purge again and retest.
The exact exclusion setting depends on your plugin. If you use WP Rocket, our guide on WP Rocket delay JavaScript exclusions shows where to add them.
Also note that cached pages can hold an old nonce or token. Most cache plugins handle forms well, but if errors only happen on cached pages, exclude the form page from the cache as a test.
Why does reCAPTCHA v3 block real visitors?
reCAPTCHA v3 gives each visitor a score from 0.0 to 1.0, and if your WPForms score threshold is set too high, real people get rejected as spam.
In WPForms > Settings > CAPTCHA, v3 has a Score Threshold setting. Visitors who score below it fail verification.
If genuine people report errors, lower the threshold a little and watch your spam levels. Google's reCAPTCHA v3 documentation explains how scores work and suggests starting with a moderate value.
Scores can be low for people using VPNs, privacy browsers or strict tracking protection. That is normal and out of your control.
You can also edit the Fail Message in the same settings, so visitors see a clear note telling them what to do.
How do you find the real error?
Open your browser's developer tools on the form page and look at the Console and Network tabs, which usually show the exact reCAPTCHA error.
Right-click the page, choose Inspect, and open the Console tab. Then load the page and try submitting the form.
Useful clues include:
- Invalid site key or invalid key type means a key or type mismatch.
- Invalid domain for site key means the domain is not registered.
- A script blocked or failing to load points to caching, a firewall or a browser extension.
If you are new to these tools, MDN has a clear introduction to browser developer tools.
On the server side, WordPress debug logging can capture PHP errors when the form submits. Our guide on enabling debug mode in WordPress shows how to turn it on safely.
What quick checks fix most cases?
Most WPForms reCAPTCHA problems are solved by matching key types, adding the domain, enabling No-Conflict Mode and excluding scripts from optimisation.
| Symptom | Likely cause | Fix |
|---|---|---|
| Checkbox never appears | Not enabled on form or script blocked | Enable on form, check optimisation settings |
| Invalid key type error | v2 keys with v3 setting or reverse | Create keys of the right type |
| Invalid domain error | Domain missing from key | Add domain in Google console |
| Works logged in, fails for visitors | Cached page or delayed JS | Exclude scripts, purge cache |
| Real visitors rejected on v3 | Threshold too high | Lower score threshold |
| Two badges or errors in console | Duplicate reCAPTCHA scripts | Turn on No-Conflict Mode |
WPForms also has a broader article on fixing reCAPTCHA in WordPress that covers more edge cases.
Should you switch to a different CAPTCHA?
If reCAPTCHA keeps causing trouble, WPForms also supports hCaptcha and Cloudflare Turnstile, and it has built-in spam protection that needs no CAPTCHA at all.
You can choose these from the same CAPTCHA settings tab. Each needs its own site key and secret key from the provider.
Turnstile and hCaptcha are good options if you want to avoid Google services for privacy reasons. Turnstile is also designed to show visitors as few challenges as possible.
WPForms has its own anti-spam token on by default, and you can add other layers too. Our guide to WPForms spam protection settings explains how these options work together.
If forms submit but emails never arrive, the CAPTCHA is not the issue. See our guide on fixing WPForms not sending email for that problem.
Frequently asked questions
Why does WPForms say Google reCAPTCHA verification failed?
The server could not confirm the visitor's token with Google. Common causes are a wrong secret key, keys of the wrong type, an unregistered domain, a v3 score below your threshold, or a cached page serving an old token. Check each of these in order.
Can I use reCAPTCHA v2 keys with v3 in WPForms?
No. Google creates keys for one specific reCAPTCHA type. If WPForms is set to v3, you need v3 keys, and if it is set to a v2 option, you need v2 keys. Create a new key pair when you change type.
What does No-Conflict Mode do in WPForms?
It stops other plugins and themes from loading their own reCAPTCHA scripts on pages that contain WPForms forms. This prevents two copies of the script from clashing, which is a common reason the checkbox or badge fails to work.
Why does reCAPTCHA work for me but not for visitors?
Logged-in users usually bypass page caching and some script optimisation. Visitors get cached pages and delayed scripts, which can break reCAPTCHA. Exclude reCAPTCHA and WPForms scripts from delay and defer settings, then purge the cache.
Is hCaptcha or Turnstile better than reCAPTCHA in WPForms?
Neither is better for every site. Turnstile aims to show few challenges, hCaptcha is popular with privacy-minded sites, and reCAPTCHA is the most familiar. If reCAPTCHA keeps clashing with other plugins, switching provider is a reasonable fix.
Sources
- Setting Up Google reCAPTCHA WPForms
- How to Fix reCAPTCHA Not Working in WordPress WPForms
- reCAPTCHA v3 Google for Developers
- Setting Up hCaptcha WPForms
- What are browser developer tools? MDN Web Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


