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

Short answer
Forminator reCAPTCHA usually fails because the keys do not match the chosen reCAPTCHA type, your domain is missing from the key, or JavaScript is delayed or blocked. Check the keys in Forminator settings, confirm the domain in Google's console, and exclude reCAPTCHA from optimization.
Key takeaways
- Each reCAPTCHA type needs its own key pair in Forminator settings.
- The form's CAPTCHA field must use the same type as the saved keys.
- Add every live domain to the key in the reCAPTCHA admin console.
- Exclude reCAPTCHA and Forminator scripts from delay and combine settings.
- Consent tools can block Google scripts until visitors accept cookies.
- Lower the v3 score threshold if real visitors are blocked.
Why is Forminator reCAPTCHA not working?
Forminator reCAPTCHA usually fails because the keys do not match the reCAPTCHA type, the domain is missing from the key, JavaScript is delayed or blocked, or a consent tool stops Google scripts.
The symptoms vary. The checkbox may not appear, the form may say the CAPTCHA is invalid, or every submission may fail silently.
Most fixes take a few minutes once you find the cause. Start with the keys, because a mismatch there causes most reports.
Before you change anything, note exactly what you see. Is the box missing, is there an error message under the field, or does the form submit with no result? Each points to a different cause below.
Test in a private browser window with no extensions. Ad blockers and privacy extensions can block Google scripts on your own computer and make a working form look broken.
If you are new to the plugin, our guide on how to use Forminator explains the basic setup.
Do your keys match the reCAPTCHA type?
Each reCAPTCHA type needs its own key pair, so a v3 key will not work in the v2 Checkbox slot and the other way round.
Forminator keeps CAPTCHA keys in Forminator > Settings, in the CAPTCHA section. There are separate fields for:
- reCAPTCHA v2 Checkbox. The I'm not a robot box.
- reCAPTCHA v2 Invisible. No box; it runs when the form is submitted.
- reCAPTCHA v3. No box; it gives each visitor a score.
When you create keys in the reCAPTCHA admin console, you choose the type. Copy those keys only into the matching fields in Forminator.
Then open your form, edit the CAPTCHA field, and make sure it uses the same type. A form set to v3 while only v2 keys are saved will fail.
| reCAPTCHA type | Visible to visitors | Key slot in Forminator |
|---|---|---|
| v2 Checkbox | Yes, checkbox | v2 Checkbox fields |
| v2 Invisible | Badge only | v2 Invisible fields |
| v3 | Badge only | v3 fields |
Is your domain listed on the reCAPTCHA key?
Google only accepts requests from domains listed in the key settings, so a missing domain or a changed domain makes reCAPTCHA fail.
Open the key in the reCAPTCHA admin console and check the Domains list. Add your live domain, such as example.com. Subdomains of a listed domain are usually covered, but check if you use a separate staging domain.
This is a common problem after a migration. Keys made for a staging site or old domain will not work on the new one.
Also check that you copied the site key into the site key field and the secret key into the secret key field. Swapping them is an easy mistake.
Did the keys actually save?
Sometimes the settings page appears to save but the keys or chosen type revert, so reload the page after saving and confirm the values are still there.
Some users report this on the Forminator support forum. Causes include browser autofill, an outdated plugin version, or a security rule blocking the save request.
Try these steps:
- Update Forminator to the latest version.
- Clear the browser cache or use a private window.
- Paste the keys again and save.
- Reload Forminator > Settings and check the fields.
If saving still fails, check your firewall logs. A security plugin or host firewall can block admin requests that contain long strings.
Is a cache or optimization plugin breaking the script?
Delayed, deferred or combined JavaScript can stop the reCAPTCHA script loading in time, so exclude Google reCAPTCHA and Forminator scripts from optimization.
Cache and speed plugins often delay JavaScript until the visitor interacts with the page. reCAPTCHA then loads late or not at all.
Exclude these from delay, defer and combine settings:
recaptchagoogle.com/recaptchagstatic.comforminator
In WP Rocket, add them to the Delay JavaScript execution exclusions. Our guide on WP Rocket delay JavaScript exclusions shows where. LiteSpeed Cache, Autoptimize and others have similar exclusion fields.
Then clear every cache layer and test in a private window. A page cached before your change will still carry the old script tags.
Is a cookie consent tool blocking Google?
Yes, that is common: consent plugins often block Google scripts until visitors accept cookies, which stops reCAPTCHA from loading.
Look at the page with cookies not yet accepted. If the CAPTCHA appears only after accepting, the consent tool is the cause.
Options:
- Configure the consent tool to treat reCAPTCHA as necessary or functional, if that fits your legal position.
- Show a message asking visitors to accept the relevant category to use the form.
- Switch to a CAPTCHA that does not need third-party cookies.
Complianz has a guide on configuring reCAPTCHA and consent in Forminator. This is general information, not legal advice. Check what your local privacy rules require.
Why does reCAPTCHA v3 reject real visitors?
reCAPTCHA v3 gives each visitor a score, and if Forminator's threshold is set too strictly, real people can be marked as bots and blocked.
Scores run from 0.0 to 1.0. Higher scores look more human. In the Forminator CAPTCHA field settings for v3, you can set the score threshold.
If legitimate users are blocked, lower the threshold a little and test again. Google's reCAPTCHA v3 documentation explains that scores need tuning for each site.
New keys also need time to learn your traffic. Scores can be less reliable in the first days.
Could a theme or plugin conflict be the cause?
Yes, another plugin may load its own copy of the reCAPTCHA script, which clashes with Forminator's and breaks one or both forms.
This often happens when a page has more than one form plugin, or when a security plugin adds reCAPTCHA to the login form site-wide.
To test:
- Open the browser console on the form page and look for red errors that mention
grecaptcha. - Deactivate other plugins on a staging site, then reactivate them one at a time.
- Switch to a default theme briefly to rule out the theme.
Common culprits include login protection plugins, other form builders and page builder add-ons that bundle their own CAPTCHA widgets. Check their settings for an option to load reCAPTCHA only on their own forms.
Our general guide to fixing plugin conflicts explains the method in more detail.
Does AJAX loading or a popup affect reCAPTCHA?
It can, because forms loaded inside popups, tabs or with AJAX may render before the reCAPTCHA script is ready, leaving an empty space.
Forminator has a behavior option to load the form with AJAX. Try switching it on or off and test again. If the form sits in a page builder popup, test it on a normal page first.
If it works on a normal page but not in a popup, the issue is timing. Use the v2 Invisible or v3 type, which cope better with late loading, or embed the form directly on the page.
If the form itself does not appear at all, see Forminator not showing.
What if nothing fixes it?
Switch to another CAPTCHA option such as hCaptcha or Cloudflare Turnstile, or use Forminator's honeypot, while you keep troubleshooting reCAPTCHA.
Forminator supports more than one CAPTCHA provider, so your form can stay protected while you investigate. Cloudflare Turnstile works without a checkbox puzzle in most cases. See Cloudflare Turnstile on WordPress.
When you contact support, include your Forminator version, the reCAPTCHA type, console errors and a link to the form. The Forminator documentation is also worth checking for current field options.
Once the form works, confirm that emails arrive too. Our page on Forminator email notifications not working covers the next step.
Frequently asked questions
Can I use reCAPTCHA v3 keys for the v2 checkbox?
No. Google issues keys for one type only. A v3 key pair will not work in the v2 Checkbox or v2 Invisible fields. Create a new key pair of the right type in the reCAPTCHA admin console and paste it into the matching fields.
Why does my form say the CAPTCHA is invalid?
This usually means the secret key is wrong, the domain is not listed on the key, or the token expired before submission. Recheck both keys, confirm the domain, and make sure caching is not serving an old page with stale tokens.
Does reCAPTCHA work on a staging site?
Only if the staging domain is listed on the key, or you create a separate key for staging. Many people forget this and think reCAPTCHA is broken after cloning a site. Add the staging domain or use test keys there.
Which reCAPTCHA type is best for Forminator?
v2 Checkbox is the easiest to understand and debug. v3 is invisible and smoother for visitors but needs score tuning. v2 Invisible sits in between. If you get lots of spam, a checkbox or Turnstile is often more predictable.
Will removing reCAPTCHA let spam through?
It can. If you disable it while troubleshooting, turn on Forminator's honeypot or another CAPTCHA provider so the form keeps some protection. Watch the submissions list for a few days and adjust as needed.
Sources
- Forminator WordPress.org
- Forminator documentation WPMU DEV
- reCAPTCHA v3 Google for Developers
- reCAPTCHA admin console Google
- Configuring reCAPTCHA and consent in Forminator Complianz
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.


