QAlaunch

Webflow form: “Oops! Something went wrong while submitting the form”

Webflow shows “Oops! Something went wrong while submitting the form” when the submission is rejected. The most common causes are reCAPTCHA switched on in Site settings while the form has no reCAPTCHA element, the plan’s form submission limit being reached, the site being exported and hosted elsewhere so Webflow never receives the form, or a misconfigured custom action URL. Check those in order, then publish and test the live form with the Network tab open.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

A visitor fills in a Webflow form, clicks submit and the form switches to its error state with the default “Oops! Something went wrong” message. Sometimes every form on the site starts failing at once, or the submit button looks disabled and cannot be clicked at all.

Why it happens

1. reCAPTCHA is on but missing from the form

When reCAPTCHA validation is enabled in Site settings, Webflow expects every form to include a reCAPTCHA element. Forms without one fail to submit, which is why turning it on can break all forms at once.

2. The plan’s submission limit is used up

Site plans include a set number of form submissions. Once a lower-tier site reaches its limit, further submissions are not processed until the plan changes.

3. The site is not hosted on Webflow

Exported code hosted elsewhere keeps the form markup but not Webflow’s form handling. Submissions have nowhere to go unless you connect your own endpoint.

4. A custom action or bot protection is misconfigured

A form pointed at a third-party Action URL with the wrong method or a broken endpoint returns an error. Bot protection such as Cloudflare Turnstile can also leave the submit button disabled if its check never completes.

How to fix it

  1. Open Site settings > Apps & Integrations and look at reCAPTCHA validation. If it is enabled, add a reCAPTCHA element inside every form on the site, or turn validation off.
  2. Open Site settings > Forms and compare the submission count with your plan’s limit. If you have hit it, upgrade or wait for the reset.
  3. If you exported the site, connect the forms to your own handler or a form service; Webflow will not process them from another host.
  4. Select the form block in the Designer and check the Action and Method fields in Settings. If you use a custom Action URL, confirm the endpoint works and accepts that method, and note Webflow’s notification emails no longer apply.
  5. Publish, open the live page in a private window with DevTools > Network open, submit test data and inspect the submit request’s status and response.
  6. Edit the form’s Error state to say something useful and include an email address, so a visitor who hits it still has a way to reach you.

How to check it's fixed

  • Submit test data on the published domain and confirm the Success state appears.
  • Check the submission is listed in Site settings > Forms and that the notification email arrives.
  • Repeat on a phone, where bot-protection checks sometimes behave differently.

What a QAlaunch scan shows for this

  • Whether submitting the form empty shows validation feedback or the error state.
  • JavaScript errors and failed requests on the page, including reCAPTCHA or Turnstile scripts that did not load.
  • A submit button that is visible but disabled in the screenshots.
  • The scan never submits real data and cannot see your plan limits or notification emails, so those you check in Site settings.

See exactly what a full report contains in the sample report.

Frequently asked questions

Why did all my Webflow forms stop working at the same time?

A site-wide setting changed. Enabling reCAPTCHA without adding the element to every form, or reaching the plan’s submission limit, both affect every form at once.

Can I use Webflow forms on an exported site?

Not with Webflow’s own handling. Exported sites need a form backend of your own or a third-party service set as the form’s Action.

Can I change the “Oops” message?

Yes. Select the form block, switch to the Error state in the settings and edit the text like any other element. Adding a contact email there is good practice.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the Webflow-specific issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Webflow: all Webflow fixes

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Webflow Help: how to add forms · Webflow community: Oops! Something went wrong · Webflow community: all forms suddenly stopped working · Webflow community: submit button disabled with Turnstile