Troubleshooting
Why Is Your WordPress Form Not Working? Causes and Fixes

Short answer
WordPress forms usually fail because of email delivery problems, JavaScript or plugin conflicts, page caching that serves expired security tokens, misconfigured CAPTCHA keys, or a firewall blocking the submission. Match your symptom to the cause, then test as a logged-out visitor.
Key takeaways
- Identify the symptom first: not showing, not submitting or no email.
- Browser console and Network tab reveal most submit failures.
- Missing emails are usually a mail delivery issue fixed by SMTP.
- Caching can break forms for visitors but not admins.
- Wrong reCAPTCHA keys or versions block genuine users.
- Always test logged out in a private window.
Why is your WordPress form not working?
Most WordPress form problems come from email delivery failures, JavaScript or plugin conflicts, caching, spam protection settings, or a security rule blocking the submission.
Not working can mean several different things, and each has a different fix. Start by working out which one you have:
| Symptom | Most likely cause | Jump to |
|---|---|---|
| Form does not appear on the page | Wrong shortcode, block or form ID | Form not showing |
| Spinner keeps spinning, nothing happens | JavaScript error or blocked AJAX request | Form not submitting |
| Success message shows but no email arrives | Mail delivery problem | Emails not arriving |
| Error about CAPTCHA or spam | reCAPTCHA or Turnstile keys or settings | Spam protection |
| Works when logged in, fails for visitors | Page caching or expired nonce | Caching |
| 403 Forbidden on submit | Firewall or security plugin | Security rules |
This guide applies to most form plugins, including Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Forminator and builder forms in Elementor or Divi. Plugin-specific menu names differ, but the causes are the same.
Is the form actually showing on the page?
If the form does not appear at all, the shortcode or block is usually wrong, the form was deleted or unpublished, or the page builder is not rendering shortcodes in that spot.
Check these in order:
- Shortcode ID. Copy a fresh shortcode from the form plugin's list. Old IDs break after imports or migrations.
- Form status. Some plugins let you disable or trash a form. A disabled form renders nothing.
- Where you pasted it. Use a shortcode block or the builder's shortcode widget, not a plain paragraph or code block.
- Conditional display. Some plugins hide forms by date, entry limit or login status.
- Theme output. A few themes do not run shortcodes in custom fields or widgets.
If you see the raw shortcode text on the page, the form plugin is probably deactivated. Reactivate it under Plugins.
Using Gravity Forms? Our guide to Gravity Forms not showing on page covers the cases specific to that plugin.
Forminator users can follow Forminator not showing for the same problem.
Why does the form not submit?
A form that spins forever or does nothing on submit almost always has a JavaScript error, a plugin conflict, or a blocked AJAX or REST API request.
Most modern form plugins submit in the background using AJAX or the WordPress REST API. If that request fails, you see no error, just a stuck spinner.
To find the cause:
- Open the page in a private window.
- Open your browser's developer tools and switch to the Console tab.
- Submit the form and watch for red errors.
- Check the Network tab for a failed request, often to admin-ajax.php or a wp-json URL.
The status code tells you a lot.
A 403 means something blocked the request. A 500 means a PHP error on the server. A 404 on a wp-json URL means the REST API is disabled or your permalinks need refreshing.
For 500 errors, turn on debugging as explained in the WordPress debugging documentation and read the log. Our guide on reading the WordPress debug log helps you spot the plugin at fault.
If the REST API looks broken, see how to fix REST API errors in Site Health.
Could a plugin or theme conflict break the form?
Yes, conflicts are one of the most common causes, especially with optimisation plugins that combine or delay JavaScript and with themes that load an old copy of jQuery.
The usual suspects are:
- Performance plugins that minify, combine, defer or delay JavaScript.
- Other form or popup plugins that load their own scripts.
- Page builders that wrap forms in their own markup.
- Themes that dequeue core scripts or load outdated libraries.
The quickest test is a staging copy of your site. Switch to a default theme and deactivate all plugins except the form plugin. If the form works, turn things back on one at a time until it breaks.
Our guide on how to fix a plugin conflict walks through this method without taking your live site down.
If a performance plugin is to blame, exclude the form plugin's scripts from minification and delay settings rather than turning off optimisation entirely.
Why does the form submit but no email arrives?
The form is working, but WordPress cannot deliver the email, usually because your host's PHP mail is blocked or the message fails sender checks and lands in spam.
This is the single most common complaint. WordPress sends mail through the wp_mail function, which by default relies on your server's mail setup. Many hosts limit it, and big inbox providers distrust it.
Fixes, from most to least effective:
- Set up SMTP. Send through a real mailbox or a transactional email service. A plugin like WP Mail SMTP handles the connection.
- Use a From address on your own domain. Sending as a Gmail or Yahoo address from your server fails authentication.
- Add SPF, DKIM and DMARC records for your domain at your DNS provider.
- Check the notification settings. Make sure the To address is correct and the notification is turned on.
- Check spam folders and any email filtering rules.
Most form plugins also store entries in the database. If entries are saved but no email arrives, you know the problem is mail delivery, not the form.
See how to set up SMTP in WordPress for a full walkthrough.
For more delivery checks, read how to fix a contact form not sending email.
Is spam protection blocking real submissions?
It can be: wrong reCAPTCHA keys, a mismatch between reCAPTCHA versions, a low score threshold, or two CAPTCHA tools on one page will reject genuine visitors.
Check the following:
- Keys match the version. reCAPTCHA v2 keys do not work in a v3 setting, and the reverse. The reCAPTCHA v3 documentation explains how scores work.
- Domain is registered. The keys must list your exact domain, including any staging domain you test on.
- Only one CAPTCHA loads. A security plugin and a form plugin both adding reCAPTCHA cause conflicts.
- Score threshold is sensible. A strict v3 threshold can block real users on VPNs or new browsers.
- Honeypot fields stay hidden. Some themes or autofill tools fill hidden fields, which flags the entry as spam.
If you switch tools, Cloudflare Turnstile and simple honeypots are lighter options many sites use. Our guide on stopping contact form spam in WordPress compares the main approaches.
Can caching break WordPress forms?
Yes, page caching can serve an old copy of the form with an expired security token, so submissions fail for visitors while they still work for logged-in admins.
Many forms include a nonce, a short-lived token that proves the request came from your page. WordPress nonces stay valid for a limited time. If your cache keeps the page longer than that, visitors get a stale token and the form rejects them.
Signs that caching is the cause:
- The form works when you are logged in, because admins usually bypass the cache.
- It fails for visitors, often with a vague invalid request or session expired message.
- It starts working right after you clear the cache, then breaks again later.
Fixes:
- Exclude the form page from page caching, or
- Shorten the cache lifespan below the nonce lifetime, or
- Turn off the nonce check if your form plugin offers that option for cached sites.
After any change, clear the cache in WordPress and test as a logged-out visitor.
Could a firewall or security plugin block the form?
Yes, a web application firewall at your host, Cloudflare or a security plugin can flag form submissions as attacks and return a 403 error.
This often happens when a message contains code-like text, links, or certain keywords. It also happens when a security plugin blocks admin-ajax.php or the REST API for logged-out users.
What to try:
- Check the security plugin's log for blocked requests at the time you submitted.
- Ask your host whether ModSecurity or another firewall rule fired.
- Review Cloudflare's security events if your site uses it.
- Allow the specific rule or URL rather than disabling the firewall.
What other causes should you check?
Less common causes include file upload limits, required fields hidden by conditional logic, server timeouts on integrations, and PHP version problems.
A few more to rule out:
- File uploads fail. The file exceeds the form's limit or the server's upload_max_filesize.
- Hidden required field. Conditional logic hides a field that is still marked required, so the form never validates.
- Slow integrations. Sending entries to a CRM or email list on submit can time out.
- Old plugin on new PHP. An outdated form plugin may throw fatal errors after a PHP upgrade.
- Mixed content. A form posting to an http URL from an https page gets blocked by browsers. The MDN guide to forms explains how form submissions work in the browser.
Update the form plugin, WordPress and your theme before deeper digging. Many form bugs are already fixed in newer versions.
How do you test a WordPress form properly?
Test as a logged-out visitor in a private window, on desktop and mobile, with a real email address, and confirm both the entry and the notification email.
A simple test routine after any fix:
- Clear all caches.
- Open the form page in a private window.
- Fill in every field, including any file upload.
- Submit and note the message shown.
- Check the entries screen in your form plugin.
- Check the inbox and spam folder for the notification.
- Repeat on a phone using mobile data.
Run this test again after plugin updates. Forms are one of the first things to break quietly, and a monthly check catches problems before customers notice.
Frequently asked questions
Why does my WordPress form work for me but not for visitors?
You are probably logged in, so you bypass the page cache. Visitors get a cached page with an expired security token, and the form rejects their submission. Exclude the form page from caching or shorten the cache lifespan, then test in a private window.
Why do I get form entries but no email notifications?
The form is saving data correctly, but WordPress cannot deliver the email. Your host may block PHP mail, or the message fails sender checks and goes to spam. Set up SMTP with a From address on your own domain and add SPF and DKIM records.
How do I find out what is breaking my form?
Open the browser developer tools, submit the form and check the Console and Network tabs for errors. Then test on a staging copy with only the form plugin active and a default theme, turning other plugins back on one at a time.
Can a cache plugin stop a contact form from working?
Yes. Page caching and JavaScript optimisation settings such as combine, defer or delay can both break forms. Exclude the form page from the page cache and exclude the form plugin's scripts from minification and delay rules.
Why does my form show a 403 error on submit?
A firewall or security plugin is blocking the request, often because the message looks like an attack or because the AJAX or REST endpoint is restricted. Check the security plugin's logs, your host's firewall and any Cloudflare events, then allow that rule.
Sources
- wp_mail() WordPress Developer Resources
- Debugging in WordPress WordPress Developer Resources
- WP Mail SMTP WordPress.org
- reCAPTCHA v3 Google for Developers
- Web forms 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.


