Webflow Form Not Working?
A Webflow form problem can cost real enquiries, so check the form setup, notification path, required fields, integrations and live submission behaviour first.
Webflow form not working: quick answer
If your Webflow form is not working, test a real submission on the published site and check form settings, notifications, required fields, spam settings, integrations and the confirmation experience.
A form can appear on the page and still fail as a business tool. Visitors may not be able to submit it, the business may not receive the email, integrations may fail, or the form may be so awkward on mobile that people abandon it.
If the issue affects several pages, start with the wider Webflow AI website repair process rather than making another isolated designer edit.
What the problem looks like
Symptoms include submissions failing, no confirmation message, notification emails not arriving, required fields blocking users, spam filtering interfering, hidden submit buttons, broken integrations or form data not reaching the right follow-up process.
Sometimes the form works once but not reliably. It may work in one browser and fail in another, or work on desktop while mobile users struggle with fields, spacing or unclear button text.
Common causes
The cause may be form configuration, notification settings, project or site plan limits, spam protection, required field choices, custom code, third-party integrations, automation routing, hidden fields, confusing labels or a contact section placed too late in the page.
The visible symptom is not always the root cause. A mobile spacing problem may come from a fixed width, an overcomplicated component, content that no longer fits, or an interaction that behaves differently on the published site. A CMS issue may be a collection field problem, a template problem or a publishing problem. Good repair starts by separating those possibilities.
What to check first
Submit a test enquiry from the live site using a different email address from the receiving inbox. Check Webflow submissions, notification emails, spam folders, integrations, confirmation messages and the mobile form layout.
Open the published URL in a private browser window and work through the site like a new visitor. Check the first screen, navigation, primary CTA, CMS pages, forms, footer and mobile version. Record the exact page, browser and viewport width where each issue appears.
If a Webflow form looks right but delivery, validation or integrations fail, test the complete form journey before rebuilding it.
- Submit a live test enquiry.
- Check Webflow form submissions.
- Check notification inbox and spam.
- Review required fields.
- Test integrations or automations.
- Complete the form on mobile.
What not to do
Do not assume the form works because it looks correct in Designer. Do not change several form settings at once without testing. Do not add duplicate forms before identifying whether the issue is delivery, layout, settings or visitor trust.
Do not keep asking AI to rewrite or rearrange sections until you know what is failing. That can make the page look different without making it more reliable. Do not rebuild immediately just because one issue is frustrating; many Webflow AI sites can be repaired or restructured without throwing away useful work.

When to stop editing and get help
Get help when enquiries matter to the business, when submissions are inconsistent, or when you cannot confirm where form data is going.
Stop when form issues affect live enquiries or mobile contact paths. If customers cannot reliably contact you, repair the enquiry flow as part of the wider site.
Practical checklist
Form repair should cover both technical delivery and the visitor journey around the form.
Work through the checklist on the live site, not only inside Designer or preview.
- Fields are labelled clearly.
- Required fields are sensible.
- Submit button is visible.
- Confirmation message appears.
- Notifications arrive.
- Submissions are stored or routed.
- Mobile form is usable.
- Privacy note remains visible where needed.
How to check the whole enquiry flow
A form is only one part of the enquiry path. The visitor needs to notice the CTA, understand what they are asking for, complete the form comfortably, see a useful confirmation and trust that someone will respond.
After technical form repair, review the surrounding section. Vague copy, hidden contact details or a weak CTA can make a working form produce few enquiries.
If the form connects to an automation, CRM or email marketing tool, test that handoff as part of the repair. A Webflow submission can be recorded while the follow-up process still fails somewhere else.
Keep a screenshot or note of the successful test submission, receiving inbox and confirmation message. That makes it easier to prove the repair worked and to diagnose future delivery changes.
That evidence matters if several people manage the Webflow site or inbox.
- Test the CTA before the form.
- Check form fields and confirmation.
- Confirm where the enquiry lands.
- Review mobile spacing around the form.
Short conclusion
A Webflow form problem can be technical, structural or conversion-related, so test the whole enquiry path before assuming the form block alone is broken.
The safest route is to diagnose the live website first, then repair the specific layout, CMS, form, SEO, publishing or conversion issues that are stopping the site from doing its job.