Usually because the form asks for too much, sits too far down the page, and gives the visitor no reason to trust it. The form element itself is rarely the problem. Webflow forms work fine out of the box. What fails is the decision to ask a stranger for eight pieces of information at once.
We rebuild a lot of Webflow sites, and the contact form is the part clients complain about most. They assume something is broken. Almost always the form is submitting perfectly and the problem is that nobody wants to fill it in.
So this guide is half technical and half about what you are asking people to do. Both halves matter.
A Webflow form is a native element that collects submissions and stores them in your site settings without any backend code. Webflow captures each submission, sends notification emails, and lets you download everything as a CSV. You can also accept file uploads. Nothing needs to be wired up before it works.
This is genuinely useful for small sites. There is no database to configure, no server to maintain, and no endpoint to secure. For a marketing site that needs a contact form and a newsletter signup, the built-in handling is enough on its own.
The tradeoff is that Webflow owns the storage. If you need submissions in a CRM, in a spreadsheet, or triggering a workflow, you connect that separately. We cover how below.
Fewer than you think, and fewer than you currently have. Baymard Institute research published in June 2024 found that the number of form fields matters more to user experience than the number of steps in a flow. Their benchmark put the average checkout at 5.1 steps and 11.3 form fields, which they describe as too many.
Baymard also reported that 17 percent of users have abandoned a checkout because it felt too complex. That research is about ecommerce checkout rather than lead forms, so do not transplant the number directly. The principle transfers cleanly though: every field you add is a reason to leave.
For a lead form, we start at name and email and then argue about anything else. Phone number costs you submissions because it feels like a commitment to being called. A message box is usually worth keeping, because it filters out people who are not serious and gives your sales reply something to respond to.
Company size, budget range, and how did you hear about us are the three fields we remove most often. They exist because someone in marketing wanted the data, not because the visitor gets anything from answering.
Put the form where the decision happens, not at the bottom by default. On a contact page it goes above the fold. On a long landing page it should appear once near the top for people who are already convinced, and again after the proof section for people who needed persuading. One form, two placements.
The reason is simple. Readiness to convert is not evenly distributed down a page. Some visitors arrive knowing what they want. Making them scroll past your whole pitch to find the form is a tax on your best leads.
In Webflow this is easy to keep consistent. Build the form once as a component, then place that component wherever you need it, which is one of the practical wins we describe in our guide to Webflow components. Edit it in one place and every instance updates.
Webflow supports adding Google reCAPTCHA v2 to forms natively, which handles most automated spam. You enable it in site settings and add the reCAPTCHA element to the form itself. Check every form on the site after turning it on, because a form left without the element is an easy thing to miss.
The bigger design question is how much friction you are willing to add. A challenge that makes people identify traffic lights will stop bots and also annoy a share of real visitors. We think that tradeoff is worth it on high-value forms and not worth it on a newsletter signup.
A honeypot field is the quieter option. You add a field that is hidden from humans with CSS, and reject any submission that fills it in. Bots complete every field they find. Real people never see it, so real people never feel the check happening.
If spam is severe, Cloudflare Turnstile is worth looking at as a less intrusive alternative to a visual challenge. It runs through custom code rather than the native integration, so it is more work to set up.
Webflow stores the submission against your site and can email a notification. What the visitor sees next is entirely up to you, and this is the part most teams neglect. The default success state is a small green message that replaces the form. It works, and it is forgettable.
We treat the success state as part of the conversion, not the end of it. Tell people what happens next and when. A line saying you will hear from a real person within one business day does more for trust than anything on the page before it, because it is the first promise you make after they commit.
Redirecting to a dedicated thank you page is worth doing when you need to track conversions cleanly, since a page load is easier to measure than a state change. It also gives you room to offer a next step, like a case study or a calendar link, while interest is still high.
Three routes, in order of effort. The simplest is Webflow''s built-in email notifications, which is fine if a human reads every lead. The middle route is an automation tool like Zapier or Make listening for new submissions and pushing them into HubSpot, Airtable, Slack, or a Google Sheet. The heaviest is a custom endpoint.
Most teams should stop at the middle option. Automation platforms handle retries, formatting, and routing without anyone maintaining code. The failure mode to watch is silent breakage, where a connection stops working and nobody notices for weeks because leads simply stop arriving.
We set up a duplicate notification for that reason. The automation writes to the CRM and Webflow still emails a person. If the two ever disagree, you find out the same day rather than at the end of the quarter.
Going the custom route means changing the form action to point at your own endpoint, which means you also take on validation, storage, and spam handling. Only worth it when you have a real requirement Webflow cannot meet.
The main one is on the free tier. Webflow''s pricing page lists 50 form submissions per site on the free Starter plan, and that allowance does not reset. Paid site plans starting with Basic list unlimited form submissions. If you launch on Starter and forget, your form quietly stops collecting once you hit fifty.
This catches people during soft launches. The site is live, the form looks fine, and submissions are being dropped because the site is still on the free plan. Check your plan before you drive any traffic at a form.
Beyond that, remember Webflow''s form storage is a record, not a CRM. There is no pipeline, no assignment, and no follow-up tracking. It tells you what came in. Deciding who owns each lead is your job somewhere else.
Make the fields big enough to tap, label them above rather than inside, and never rely on placeholder text as the label. Placeholder-only labels disappear the moment someone starts typing, which forces people to remember what each box was for. That single choice causes a lot of abandoned forms on mobile.
Mark both the required fields and the optional ones explicitly. Baymard Institute reported that as of its 2021 benchmark only 14 percent of ecommerce checkouts marked both, up from 9 percent in 2012. Baymard links that failure to unnecessary validation errors, confusion about what must be filled in, and abandonment.
Marking only one of the two is where teams go wrong. If you flag just the required fields, visitors assume everything unmarked is also required. If you flag just the optional ones, they cannot tell whether an unmarked field was an oversight. Label both and the ambiguity disappears.
Show validation errors next to the field that has the problem, in plain language, at the moment it happens. A single red banner at the top saying the submission failed is the worst version of this, because it makes the visitor hunt for their own mistake.
Finally, make the button say what it does. Submit is a word from software, not from people. Send message, book a call, and get the guide all outperform it because they describe the outcome, which is the same argument we make in our piece on designing calls to action that convert.
Open your main form and delete every field that is not name, email, and message. Move the form higher on the page. Rewrite the button to describe the outcome. Then check whether your site plan actually allows the submissions you expect. Those four changes take under an hour and usually move the number more than a redesign would.
Forms are where a marketing site either does its job or does not, which is why we treat them as a conversion problem rather than a build detail. The same thinking runs through how we approach high-converting landing pages, because a landing page is really just a form with an argument in front of it.
If your Webflow forms are getting traffic but no submissions and you cannot work out why, we are happy to take a look with you. Reach out at phoenix.studio and we will go through it.
Tell us where you want to go. We'll tell you how we'd get you there.