Troubleshooting
Gravity Forms Captcha Not Working: Causes and How to Fix It

Short answer
A Gravity Forms CAPTCHA usually fails because the site and secret keys do not match the reCAPTCHA version, your domain is missing from the Google key, or a caching plugin delays the reCAPTCHA script. Re-enter matching keys, add your domain, exclude the script from optimization and clear every cache.
Key takeaways
- Google v2 and v3 keys are not interchangeable, so match the key type to your setup.
- Add every domain that shows the form to the key's domain list in Google.
- Script delay, defer and combine settings often hide the reCAPTCHA box.
- Two plugins loading reCAPTCHA on one page usually break each other.
- A strict v3 score threshold can send real entries to spam.
- Always test logged out in a private window after clearing caches.
Why is the Gravity Forms CAPTCHA not working?
Most Gravity Forms CAPTCHA problems come from wrong or mismatched Google keys, a domain missing from the key settings, or a caching or script optimization plugin that breaks the reCAPTCHA script.
The symptoms vary.
Some people see a blank space where the checkbox should be. Others see an error saying the reCAPTCHA was invalid, even after ticking the box. Some forms submit fine but every entry lands in spam.
Each symptom points to a different cause. That is why it helps to know which CAPTCHA you are using before you change anything.
Gravity Forms supports a few options:
- The core CAPTCHA field. It sits under Advanced Fields and uses Google reCAPTCHA v2 (checkbox or invisible).
- The reCAPTCHA Add-On. It adds reCAPTCHA v3, which runs in the background and scores each visitor.
- Math or simple text CAPTCHA. These need the free Really Simple CAPTCHA plugin.
- Third-party options. Some sites use Cloudflare Turnstile or hCaptcha through add-ons.
The Gravity Forms CAPTCHA field documentation lists the field options. If you are new to the plugin, our guide on how to use Gravity Forms covers the basics first.
How do you check that your reCAPTCHA keys are correct?
Open Forms > Settings > reCAPTCHA and confirm the site key and secret key come from the same Google key pair, of the type your form uses.
This is the single most common cause. Google issues separate keys for v2 and v3. A v3 key will not work in a v2 CAPTCHA field, and a v2 I'm not a robot key will not work for the v3 add-on.
Follow these steps:
- Sign in to the Google reCAPTCHA admin console with the account that created the keys.
- Open the key and note its type: v2 checkbox, v2 invisible or v3.
- In WordPress, go to Forms > Settings > reCAPTCHA.
- Paste the site key and secret key again. Watch for extra spaces at the start or end.
- Pick the matching type and save the settings.
Gravity Forms validates the keys when you save. If it reports a problem, generate a fresh pair instead of trying the old one again.
Google explains the key types in its reCAPTCHA developer guide. The Gravity Forms reCAPTCHA Add-On setup guide shows where the v3 keys go.
Is your domain listed in the Google reCAPTCHA settings?
Your exact domain must be in the key's domain list, or Google refuses to load the widget and shows an invalid domain error.
This often breaks after a move. You build on a staging site, launch on the live domain, and forget the live domain was never added. It also breaks when a site switches from one domain to another.
In the reCAPTCHA admin console, open the key's settings and look at the Domains list. Add each domain that shows the form. That includes staging copies if you test forms there.
You do not need to add www separately in most cases, because Google treats subdomains of a listed domain as allowed. Check Google's own notes if you use an unusual setup.
If you recently changed your site address, our guide to changing the domain of a WordPress site lists other settings that need updating at the same time.
Can caching or optimization plugins break the CAPTCHA?
Yes, delaying, deferring or combining JavaScript is a leading cause of a missing or broken reCAPTCHA in Gravity Forms.
Speed plugins often hold back scripts until the visitor scrolls or clicks. reCAPTCHA needs its script to load before the form appears. When the script is delayed, the box never shows or the token is empty when the form is sent.
Page caching can cause a second problem. Gravity Forms adds a security token to each form. If a cached copy of the page is served for days, that token can expire and the submission fails.
Try these fixes:
- Exclude the reCAPTCHA script from delay and defer settings. The script address usually contains recaptcha or gstatic.
- Exclude Gravity Forms scripts from JavaScript combining.
- Exclude the form page from page caching if errors persist.
- Turn off Rocket Loader in Cloudflare, or exclude the page from it.
After each change, clear every cache layer. Our guide on how to clear cache in WordPress covers plugin, server and CDN caches.
Could another plugin be loading reCAPTCHA twice?
Yes, when two plugins load Google's reCAPTCHA script on the same page, one usually overwrites the other and the Gravity Forms field fails.
Security plugins, login protection tools and other form plugins often add their own reCAPTCHA. If one loads v3 and Gravity Forms loads v2, Google gets confused about which widget to render.
To test this, open the page, view the source, and search for recaptcha/api.js. If you see it more than once with different settings, you have found a conflict.
You can then:
- Turn off reCAPTCHA in the other plugin for front-end pages.
- Limit the other plugin to the login page only.
- Switch one of them to a different CAPTCHA service.
If you cannot spot the clash, run a normal conflict test. Our guide to fixing a plugin conflict walks through it safely, ideally on a staging copy.
Why are good entries marked as spam with reCAPTCHA v3?
reCAPTCHA v3 gives each visitor a score, and if your threshold is too strict, real people fall below it and Gravity Forms flags their entries as spam.
Scores run from 0.0 to 1.0. A higher number means Google thinks the visitor is more likely human. The reCAPTCHA Add-On lets you set the score below which an entry is treated as spam.
Some visitors get low scores for harmless reasons. Privacy browsers, VPNs, new devices and blocked cookies all lower the score.
Here is a sensible approach:
- Start with a moderate threshold. Google's documentation suggests 0.5 as a common starting point.
- Check the spam folder under Forms > Entries for a week.
- Lower the threshold if real entries keep landing there.
- Add a second layer such as the honeypot instead of pushing the score higher.
Google describes how scores work in the reCAPTCHA v3 documentation.
What does each CAPTCHA symptom usually mean?
Match the symptom to its most likely cause to save time, then work through the matching fix first.
| Symptom | Most likely cause | First fix to try |
|---|---|---|
| Box does not appear | Script delayed or blocked | Exclude reCAPTCHA from JS delay |
| Invalid domain message | Domain missing in Google | Add the domain to the key |
| reCAPTCHA was invalid on submit | Wrong key type or expired token | Re-enter matching keys, clear cache |
| Entries go to spam | v3 threshold too strict | Lower the score threshold |
| Works logged in, fails logged out | Page cache serving stale form | Exclude the form page from cache |
| Works on one page only | Duplicate script on other pages | Find the second reCAPTCHA source |
Do browser settings or privacy tools affect the CAPTCHA?
Yes, ad blockers, strict tracking protection and cookie consent tools can block Google's scripts, so the CAPTCHA fails for some visitors only.
If the form works for you but a few visitors complain, this is a likely reason. Test in a private window with extensions turned off. Then test with a privacy extension turned on.
Cookie banners deserve a closer look. Some consent tools block all Google scripts until the visitor accepts. That stops reCAPTCHA from loading on the first visit.
Most consent plugins let you mark reCAPTCHA as a necessary script. Whether that is allowed depends on your region and setup, so treat this as general information, not legal advice.
A Content Security Policy can also block Google. If your site sends CSP headers, allow the domains that reCAPTCHA uses. Your browser console will name any blocked address.
Should you switch to a different CAPTCHA or spam method?
If reCAPTCHA keeps failing or hurts conversions, switching to the honeypot, Cloudflare Turnstile or a spam filter is often a better fix than more tweaking.
Gravity Forms has a built-in honeypot setting in each form's settings. It adds a hidden field that bots fill in and people do not. It costs nothing and adds no friction.
Other options include:
- Cloudflare Turnstile. A privacy-friendly checkbox alternative. Our guide to Cloudflare Turnstile on WordPress explains the setup.
- Akismet. Gravity Forms can pass entries to Akismet for spam checks.
- Anti-spam rules. Block entries with links or certain words using validation hooks.
For a wider plan, see our guide on how to stop contact form spam in WordPress.
How do you test the fix properly?
Test the form logged out, in a private window, on desktop and mobile, after clearing every cache layer.
Logged-in admins often bypass caching and some scripts. That means the form can work for you and still fail for visitors. Always test as a visitor.
Run through this short checklist:
- Clear plugin, server and CDN caches.
- Open the form in a private window.
- Open the browser console and look for red errors.
- Submit a real test entry.
- Confirm it appears under Forms > Entries and not in spam.
- Confirm the notification email arrives.
If entries arrive but emails do not, the CAPTCHA is fine. That is a separate problem covered in our guide to fixing Gravity Forms notifications not sending.
Keep the Gravity Forms core and reCAPTCHA Add-On updated. The reCAPTCHA Add-On changelog lists compatibility fixes that may already solve your issue.
Frequently asked questions
Why does Gravity Forms say the reCAPTCHA was invalid?
This message usually means Google rejected the token sent with the form. Common reasons are a secret key that does not match the site key, the wrong key type for the field, a domain missing from the key, or a cached page with an expired token. Re-enter matching keys and clear your caches.
Does Gravity Forms support reCAPTCHA v3?
Yes, through the official reCAPTCHA Add-On, which is available on Gravity Forms license levels that include it. The core CAPTCHA field handles reCAPTCHA v2 checkbox and invisible modes. Check the Gravity Forms add-ons page for which licenses include the add-on today.
Why does the CAPTCHA work for me but not visitors?
Logged-in administrators often skip page caching and some script optimizations. Visitors get the cached, optimized page, where the reCAPTCHA script may be delayed or the form token stale. Test in a private window while logged out to see what visitors see.
Can I use Gravity Forms without a CAPTCHA?
Yes. Many sites rely on the built-in honeypot setting plus Akismet or other spam filters. This avoids visitor friction and the privacy questions that come with Google scripts. Add a CAPTCHA only if spam still gets through.
Do I need new reCAPTCHA keys after moving my site?
Not always. You can add the new domain to the existing key in the Google reCAPTCHA admin console. Create new keys only if you no longer have access to the Google account that owns the old ones.
Sources
- CAPTCHA field Gravity Forms Documentation
- Setting up the reCAPTCHA Add-On Gravity Forms Documentation
- reCAPTCHA Add-On changelog Gravity Forms Documentation
- reCAPTCHA v3 Google for Developers
- Introduction to reCAPTCHA Google for Developers
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.


