Fix a form that will not submit

We'll check required fields and validation, rule out JavaScript errors and extensions, then isolate the cause—client-side validation, server error, or blocked request—or tell you when to escalate.

Category
Troubleshooting · Home maintenance
Time
10–20 min
Last reviewed
What you'll need
  • Browser with DevTools (F12)
  • The form that will not submit

Step-by-step diagnostic

Step 1 of 9
Show full guide

Steps

Goal: Check required fields and validation, then rule out JavaScript errors and extensions.

  • Fill all required fields (look for asterisks). Check format (email, phone) and length. Ensure required checkboxes are checked.
  • Good: No red highlights or inline errors. Bad: Validation errors—fix them and retry. Proceed to DevTools if validation passes but Submit does nothing.

DevTools Console and Network

Goal: Use DevTools to find JavaScript errors or failed HTTP requests.

  • Press F12. Open the Console tab. Click Submit and watch for red error messages.
  • Open the Network tab. Clear it, click Submit. Look for red (failed) requests. Click one and check Status and Response.
  • Good: You find the cause—Console error or Network status (400, 422, 500, CORS). Bad: No errors and no failed request—proceed to Extensions.

Extensions and incognito

Goal: Rule out extensions that block form submission.

  • Open an incognito or private window (extensions are usually disabled). Try the form.
  • Good: The form submits in incognito—an extension is blocking. Disable extensions one at a time to find it. Bad: Still fails—try another browser or escalate.

When to get help

If you have checked validation, Console, Network, extensions, and cache and the form still fails, capture: browser and version, Console errors, Network status codes, and the URL. Contact the site owner or support. If the form works in incognito, an extension is likely blocking—mention that.

Verification

  • The form submits and you see a success message or redirect.
  • No red errors in the Console when you click Submit.
  • Network tab shows a successful request (status 200 or 3xx) when the form submits.

Escalation ladder

Work from the device outward. Stop when the problem is fixed.

  1. Validation Fill all required fields; fix format and length errors.
  2. Console and Network Check DevTools for JavaScript errors and failed HTTP requests.
  3. Extensions Try incognito or disable extensions; retry.
  4. Cache and browser Clear cache and cookies; try a different browser.
  5. Escalate Capture Console errors, Network status, URL; contact site support.

What to capture if you need help

Before calling support or posting for help, have these ready. It speeds everything up.

  • Browser and version
  • Console error messages (full text)
  • Network tab: failed request URLs and status codes
  • Whether the form works in incognito or another browser
  • Steps already tried

Are all required fields filled and valid?

Required fields often have asterisks. Check format (email, phone) and length.

Look for required fields and inline error messages. Fill everything and fix any format errors. Good: no red highlights or errors. Bad: validation errors—fix them and retry.

You can change your answer later.

Fix validation errors

Complete all required fields. Fix email format, phone format, and length. Check checkboxes (e.g. terms). Retry Submit.

Are there JavaScript errors in the Console when you click Submit?

Open DevTools (F12) > Console. Click Submit and watch for red errors.

Press F12, open Console, click Submit. Errors: note the message—often points to the cause. No errors: proceed to Network tab.

You can change your answer later.

Fix or work around the Console error

JavaScript errors can block submission. If the error mentions CORS, mixed content, or a blocked script, the site or your network may be the cause. Try incognito or another browser. If it works there, an extension or cache may be blocking.

Does the Network tab show a failed request (red) when you submit?

Network tab shows HTTP requests. Red = failed.

Open Network tab, clear it, click Submit. Look for red entries. Click one and check Status (400, 403, 422, 500). 400/422: validation—check the response body for field errors. 500: server error—contact site support. CORS: server blocks request—contact site owner.

You can change your answer later.

Check the failed request status

400 or 422: server rejected validation—read the response for field errors. 403: forbidden—may be blocked by extension or server. 500: server error—contact support. CORS error: server must allow your origin—contact site owner.

Does the form submit in incognito or with extensions disabled?

Extensions can block form POST requests.

Try incognito/private mode (extensions usually off). Or disable extensions one at a time. Works in incognito: an extension is blocking—find and disable it. Still fails: try another browser or escalate.

You can change your answer later.

An extension is blocking

The form works in incognito. Disable extensions in a normal window one at a time to find the blocker. Ad blockers and privacy tools are common culprits. Whitelist the site if the extension allows.

Escalate with evidence

Capture: browser and version, Console errors, Network status codes, URL. Contact the site owner or support. Mention if it works in incognito or another browser.

Reviewed by Blackbox Atlas

Frequently asked questions

Why would a form not submit?
Common causes: required fields missing or invalid, JavaScript errors blocking submission, extensions blocking the request, network or CORS errors, or a server-side error. Check the Console and Network tabs in DevTools first.
How do I see why a form failed?
Open DevTools (F12). Console tab shows JavaScript errors. Network tab shows HTTP requests—look for red (failed) requests and their status codes. A 400 or 422 often means validation failed; 500 means server error.
Can an extension block form submission?
Yes. Ad blockers, privacy tools, and security extensions can block form POST requests or scripts. Try incognito/private mode with extensions disabled, or disable extensions one at a time and retry.

Rate this guide

Was this helpful?

Thanks for your feedback.

Continue to