Troubleshooting
Contact Form 7 Submit Button Not Working: Causes and How to Fix It

Short answer
The Contact Form 7 submit button usually fails because an unticked acceptance checkbox keeps it disabled, the plugin script is not loading, the REST API is blocked, or caching and conflicts break the request. Check the console and Network tab to see which one applies.
Key takeaways
- Acceptance checkboxes disable the button until ticked.
- A missing script makes clicks do nothing.
- An endless spinner often means a blocked REST API.
- Exclude the plugin scripts from delay and minify.
- Overlays can silently block clicks on the button.
- Test logged out on desktop and mobile.
Why is the Contact Form 7 submit button not working?
The Contact Form 7 submit button usually fails because an unchecked acceptance box keeps it disabled, the plugin's JavaScript is not loading, the REST API is blocked, or a cache, theme or plugin conflict stops the request.
Contact Form 7 is one of the most installed form plugins on WordPress. Its submit button depends on a small script and a call to the WordPress REST API.
Problems tend to look like one of these:
- The button is greyed out and cannot be clicked.
- Clicking does nothing at all.
- The spinner appears and keeps spinning forever.
- The page reloads and the form clears, but no message appears.
- A red error banner says there was an error trying to send your message.
If the button works but emails never arrive, that is a different problem. See our guide on fixing Contact Form 7 not sending instead.
What are the common causes at a glance?
Each symptom points to a different layer, so identify what the button does when clicked before changing settings.
| What you see | Likely cause | First fix |
|---|---|---|
| Button greyed out | Acceptance checkbox not ticked | Tick it or make it optional |
| Nothing happens on click | JavaScript error or script not loaded | Check browser console |
| Spinner never stops | REST API blocked or erroring | Test the REST API |
| Page reloads, no message | Script missing, form submits normally | Check theme footer and optimisation |
| Error banner after submit | Server or mail error | Check mail settings and logs |
| Button hidden or unclickable | CSS overlay or styling issue | Inspect the element |
Start with the row that matches, then follow the section below.
Is an acceptance checkbox disabling the button?
Yes, this is the most common reason, because a Contact Form 7 acceptance field disables the submit button until the visitor ticks the box.
The acceptance checkbox is often used for consent or terms. By default the submit button stays inactive until it is checked.
If visitors miss the box, they think the button is broken. You can fix this in a few ways:
- Make the acceptance text clearer and place it right above the button.
- Add the optional option to the acceptance tag if consent is not mandatory.
- Style the disabled button so it is obvious why it cannot be clicked.
If the checkbox itself does not appear, our guide on checkboxes not appearing in Contact Form 7 covers theme and CSS causes.
Is the Contact Form 7 script loading?
If clicking the button does nothing, or the page reloads without a message, the plugin's JavaScript is probably missing or broken, so check the browser console and the page source.
Contact Form 7 submits forms in the background with its own script. Without it, the form falls back to a normal page submit or does nothing.
How to check:
- Open the page with the form.
- Open developer tools and select the Console tab. Google's Chrome DevTools console guide explains how.
- Click Submit and look for red errors.
- Search the page source for contact-form-7 to see whether its script file is included.
If the script is missing, your theme may not call the standard footer hook. Themes must include wp_footer() so plugins can add scripts. Switch to a default theme briefly to test.
Contact Form 7's own page on why an AJAX form may not work lists the same checks.
Is the WordPress REST API blocked?
If the spinner keeps turning, the form's request to the REST API is probably being blocked or returning an error, so confirm the REST API works and is not disabled by a plugin or firewall.
Modern versions of Contact Form 7 send submissions through a REST API route. Security plugins sometimes disable the REST API for visitors, which breaks this.
Things to check:
- Visit your site address with /wp-json/ added. You should see a JSON response, not an error.
- Look in security plugins for options like disable REST API and allow Contact Form 7's routes.
- Check the Network tab in developer tools for a failed request with a 401, 403 or 500 status.
- Check Site Health in WordPress for REST API warnings.
Our guide on enabling the REST API in WordPress covers the settings that switch it off.
If Site Health shows warnings, see our guide on fixing REST API errors in Site Health.
The REST API handbook on developer.wordpress.org explains how the API works.
Is caching or script optimisation breaking the form?
Yes, minifying, combining or delaying JavaScript can stop Contact Form 7 from running, and page caching can serve outdated form markup, so exclude the plugin's scripts and test again.
Optimisation plugins often delay scripts until the user moves the mouse or scrolls. If the form script is delayed, the button may not respond in time.
Steps to try:
- Exclude Contact Form 7 scripts from minify, combine and delay settings.
- Purge all caches, including server and CDN caches.
- Test the page with optimisation turned off.
Our guide on clearing cache in WordPress shows how to purge each layer.
Could reCAPTCHA be blocking submissions?
Yes, a misconfigured reCAPTCHA v3 integration can stop submissions or flag real visitors as spam, so check your keys and test with the integration paused.
Contact Form 7 integrates with Google reCAPTCHA v3. If the keys are wrong, the domain is not registered, or the script is blocked by a cookie banner, submissions fail.
Quick checks:
- Confirm the site key and secret key belong to the current domain.
- Make sure cookie consent tools do not block Google's script.
- Temporarily remove the keys to see whether the button starts working.
Our guide on Contact Form 7 reCAPTCHA v3 not working goes into more detail.
Is something covering the button?
If the button looks normal but nothing happens when you click it, an invisible element may be sitting on top of it, so inspect the button to see which element receives the click.
This happens with sticky headers, cookie banners, popups and page builder sections that overlap. The click lands on the overlay instead of the button.
To check:
- Right-click the button and choose Inspect.
- See whether the highlighted element is the button or something else.
- Adjust the overlapping element's position or stacking order. MDN explains the z-index property if you need background.
If you have heavily customised the form's look, our guide on styling Contact Form 7 shows safer ways to adjust the button.
Is the form inside a page builder or popup?
Forms loaded inside popups, tabs or page builder widgets sometimes miss the script setup that runs on page load, so test the form on a plain page to see whether it works there.
When a form is added after the page loads, for example inside a popup, Contact Form 7 may not attach its handlers to it.
Try these steps:
- Place the same shortcode on a plain test page.
- If it works there, the builder or popup is the cause.
- Check the builder's documentation for loading forms on open.
Our guide on Contact Form 7 not showing in Elementor covers common builder issues.
Could a plugin or theme conflict be the cause?
Yes, another plugin or your theme can break the submit button, so run a conflict test with a default theme and only Contact Form 7 active.
Follow these steps on a staging site:
- Switch to a default theme.
- Deactivate every plugin except Contact Form 7.
- Test the form.
- Reactivate plugins one at a time until it breaks.
Our plugin conflict guide explains the process in full. Also update Contact Form 7 from the WordPress.org plugin page or your Plugins screen, since fixes ship regularly.
How do you confirm the fix worked?
Submit the form while logged out in a private window, on desktop and mobile, and confirm you see the green success message and receive the email.
A short checklist:
- The button becomes active once required fields and boxes are filled.
- The spinner stops and a message appears.
- The email arrives in the inbox, not spam.
- No errors appear in the console.
Retest after every plugin or theme update. Small changes to scripts or caching can break the button again without warning.
Frequently asked questions
Why is my Contact Form 7 submit button greyed out?
An acceptance checkbox is almost always the reason. Contact Form 7 disables the submit button until the visitor ticks it. Make the checkbox clearer, or mark it optional if consent is not required for that form.
Why does the Contact Form 7 spinner keep spinning?
The background request to the REST API is not completing. A security plugin may be blocking the API, the server may return an error, or a firewall may reject the request. Check the Network tab for the failing request.
Does Contact Form 7 need the REST API?
Yes. Current versions send form submissions through a REST API route. If the API is disabled for visitors, the submit button stops working, so allow the plugin's routes in any security tool you use.
Can a cache plugin break the Contact Form 7 button?
Yes. Delaying, combining or minifying JavaScript can stop the form script from running in time. Exclude Contact Form 7 scripts from these features and purge caches after changes.
Why does my Contact Form 7 form reload the page?
If the page reloads with no message, the plugin script did not run and the browser fell back to a normal submit. Check that your theme includes the footer hook and that no script errors appear in the console.
Sources
- Why isn't my AJAX contact form working correctly? Contact Form 7
- Acceptance checkbox Contact Form 7
- Contact Form 7 plugin WordPress.org
- REST API Handbook WordPress Developer Resources
- Console overview Chrome for Developers
- z-index 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.


