Every paid Webflow site plan includes unlimited form submissions, native bot blocking and spam filtering at no extra charge, while the free Starter plan stops collecting after 50 submissions for the life of the site (Webflow pricing page and Help Center, opened 7 November 2026). That is the first fact to know about Webflow forms, because most complaints about them come from a site still on the free plan, or from a form whose custom action silently bypasses everything Webflow does.
This guide covers the three ways to run a lead form on a Webflow site, what each does with spam and attribution, and the launch test we would run first. Every limit comes from Webflow's, HubSpot's, Google's or Cloudflare's own documentation.
What Webflow forms do natively, and where the native path stops
A Webflow form is an ordinary HTML form that Webflow's servers process on submit. Each form can send its submission to several destinations at once: Webflow's store, email notifications, a webhook, or an app such as HubSpot, Zapier or Make. The exception is the custom action, which posts the form straight to a URL you choose, skips Webflow's processing, and cannot be combined with the others.
| Capability | Starter (free) | Basic ($15/mo) | Premium ($25/mo) |
|---|---|---|---|
| Submissions | 50 in total, never resets | Unlimited | Unlimited |
| Notification recipients | 5, all Workspace members | Any addresses | Any addresses |
| File upload | No | No | Yes, 10 MB per file |
| CSV export and spam inbox | Yes | Yes | Yes |
| Webhook, Apps, custom action | Yes | Yes | Yes |
| Custom domain | No | Yes | Yes |
Source: Webflow pricing page and Help Center, read 2026-11-07. Prices are billed yearly.
The store and the inbox. Submissions sit under Site settings > Forms, one table per form, with CSV export. With spam filtering on, suspected spam goes to a separate spam inbox rather than disappearing. Name every form: the default is "Email Form", and two unnamed forms share one table.
Notifications. Each form has its own recipients, sender name, reply-to, subject and body, with variables for the form data. Webflow recommends a named mailbox over admin@ or info@, because role addresses are filtered more often. An unbranded sender address needs a Growth Workspace.
Webhooks. A form can post to one or more webhook URLs. Each request carries an x-webflow-signature header, a SHA-256 HMAC you verify with the secret Webflow shows once at creation. Anything other than a 200 is retried three more times at ten-minute intervals, then dropped; a webhook that keeps failing is deactivated.
Where native stops. Webflow validates required fields and input types, but has no conditional logic, multi-step state or routing, and nothing native writes to a CRM on its own. That is what the app, webhook or custom action is for.
Three ways to run a lead form on a Webflow site
For a B2B marketing site the choice is between a native Webflow form, a HubSpot form, and a native form posting to an endpoint you own. We build marketing sites in Webflow, so read our view with that bias.
| Question | Native Webflow form | HubSpot form in Webflow | Custom endpoint |
|---|---|---|---|
| Where the lead lands | Webflow store, email, webhook or app | HubSpot contact record | Wherever you send it |
| Who styles it | Webflow Designer | HubSpot editor, or CSS with a Professional plan | Webflow Designer |
| Spam layer | reCAPTCHA v2, bot blocking, spam filtering | HubSpot's own filtering | Turnstile or reCAPTCHA, your rules |
| UTM capture | Hidden fields, passed to webhooks and most apps | Hidden fields on the HubSpot form | Anything you read from the URL or cookies |
| Running cost | Site plan only | HubSpot plan; Professional for developer embed | A small serverless function |
| Fits when | Contact, newsletter, gated content | HubSpot is the system of record and marketing owns the forms | Routing, enrichment, consent logic or two systems of record |
Source: Webflow Help Center, HubSpot Knowledge Base, Cloudflare Turnstile plans, read 2026-11-07.
The native form. The default for a contact page, a newsletter box and a gated download. Build it in the Designer, name it, point it at a webhook or an app, and add the spam layers below. Our post on Webflow apps a B2B marketing team needs covers which apps carry form data.
The HubSpot form. When HubSpot is the system of record, a HubSpot-built form avoids a mapping step: fields are contact properties, hidden fields read URL parameters such as utm_campaign into properties, and the submission carries the visitor's tracking cookie. The cost is styling. The standard embed is styled in HubSpot's editor; the developer code that lets you style it with your own CSS needs a Marketing Hub or Content Hub Professional or Enterprise subscription. The site's domain must also be added to HubSpot's tracking settings, or its submissions are marked as spam. Our HubSpot Webflow Integration guide covers the four connection paths in detail.
The custom endpoint. A native Webflow form with a custom action pointed at a small server you run, or a Webflow webhook feeding the same server. It is the right answer when a lead has to be enriched, routed to a territory, written to two systems, or checked against a consent rule before anyone sees it. Of the two wirings we would prefer the webhook: Webflow's store, notifications, spam settings and retries stay in the path, and a lead stored in two places beats a lead stored in none. The custom action is only needed when the server has to decide what the visitor sees next.
Spam: four layers, what each one costs
Webflow's Help Center lists four spam methods: CAPTCHA, bot blocking, spam filtering and the honeypot. Two of the four are a toggle.
| Layer | How it is enabled | What it does | Visible to the visitor | Cost |
|---|---|---|---|---|
| Bot blocking | Site settings > Apps & Integrations > Cloudflare Turnstile spam protection | Analyses mouse movement and inputs, blocks bot submissions on every form | Submit button disabled while the check loads | Included |
| Spam filtering | Same setting, second toggle | Checks submitted data, routes spam to the spam inbox | No | Included |
| reCAPTCHA v2 checkbox | reCAPTCHA element in each form plus keys under Apps & Integrations | Google challenge before submit | Yes, a checkbox | Free to 10,000 assessments a month per organisation |
| Honeypot | Hidden field plus custom code | Discards submissions where a bot filled the hidden field | No | Developer time |
| Turnstile on a custom endpoint | Widget in the form, siteverify on your server | Cloudflare challenge, usually invisible | Rarely | Free, 20 widgets per account |
Source: Webflow Help Center, Google Cloud reCAPTCHA pricing, Cloudflare Turnstile plans, read 2026-11-07.
Two rules follow from Webflow's documentation. First, reCAPTCHA validation is site-wide: once the keys are saved, every form without a reCAPTCHA element fails to submit, immediately, whether or not you republish. Second, Webflow supports only the v2 "I'm not a robot" checkbox; v3 keys produce an "Invalid site key" error.
What the free tier covers. Google gives 10,000 reCAPTCHA assessments a month free per organisation, then a flat $8 for 10,001 to 100,000 and $1 per 1,000 above that. A single site rarely reaches the paid band; an agency pooling many clients under one Google organisation can.
Our order of operations. We would turn on bot blocking and spam filtering on every site at launch, since both are free and invisible, and add reCAPTCHA only where spam continues. On a custom endpoint we would use Turnstile: free for up to 20 widgets with 10 hostnames each, a checkbox shown only to risky visitors in managed mode, and a server-side check that is one POST to siteverify with a token that lives 300 seconds and verifies exactly once.
Attribution: getting the campaign from the URL to the CRM
A form that works but loses its UTM values is the most expensive failure: the paid campaign keeps spending with no credit. Where the values end up depends on the path.
Native form to webhook or app. Add hidden inputs for utm_source, utm_medium, utm_campaign, gclid and the landing page, fill them from the URL or a first-touch cookie with a few lines of custom code, and they travel with the submission.
Native form to HubSpot's non-HubSpot forms tool. This is the path the HubSpot app uses for native Webflow forms, and it has hard rules: static HTML present at page load, an email input of type email, a standard submit button, no iframe, no single-page app, no JavaScript bound to submit. The rule that bites: "The form must not contain hidden fields. The tool does not collect information from any hidden fields." Your UTMs have to arrive another way, for example through a parallel webhook. HubSpot also records a submission for every click of the submit button, including ones that fail validation.
HubSpot form. Hidden fields on a HubSpot-built form do capture URL parameters into contact properties, with one restriction: a required field cannot be hidden, and the pre-populate option for returning visitors can overwrite a hidden value.
Custom endpoint to HubSpot's Forms API. The unauthenticated submission endpoint takes the portal ID and form GUID in the path, up to 1,000 fields, and a context object with the hutk tracking cookie, page URI and page name. Pass hutk and HubSpot ties the submission to the visitor's existing timeline.
Measuring the form itself. GA4's enhanced measurement adds form_start, fired the first time a visitor interacts with a form in a session, and form_submit, with the parameters form_id, form_name, form_destination and form_submit_text. Those parameters only appear in reports once you create custom dimensions for them, so do that before launch. Our analytics stack for a four-week build covers the rest.
Field count and friction: what the data says
Zuko's benchmark across 321,937 contact-form sessions puts completion at 47.4%, with desktop at 51.2% and mobile at 39.4%; lead generation forms, which Zuko labels enquiry forms, sit at 42.7%. The desktop-to-mobile gap is the number to act on: test the form on a phone with the keyboard open, use the phone input type so the numeric keypad appears, and keep labels outside the fields, since placeholders disappear on typing and are not read by screen readers.
The field count debate is covered in our web form conversion statistics post, and our demo request conversion rates post shows top-performing demo forms converting about as well with thirteen fields as with two. Ask for what sales will use in the first call; the hard questions belong in the CRM or a booking step.
A launch checklist for a Webflow form
- The site is on a paid site plan, or the 50-submission cap is monitored under Site settings > General.
- Every form has a unique name and its own notification recipients at a named mailbox, with reply-to set to the submitter's email.
- Bot blocking and spam filtering are on, and the submit button's disabled state is styled.
- If reCAPTCHA is on, every form has the element, and the keys are v2 checkbox keys registered for the custom domain and the webflow.io subdomain.
- Hidden attribution fields exist, and the path that carries them was chosen with the HubSpot hidden-field rule in mind.
- A test submission from a UTM-tagged URL on the published site shows up in the CRM with the campaign attached, in GA4 as form_submit, and in the inbox.
- The webhook signature is verified, and file uploads, if used, have "Restrict uploaded file access" set deliberately, since by default only people logged into Webflow can open the link.
What this means for a B2B team choosing a form path
Start native. A named Webflow form with bot blocking, spam filtering and a webhook covers a contact page, a newsletter and a gated asset, costs nothing beyond the site plan, and keeps a copy of every lead in Webflow's store. Move the form into HubSpot when marketing owns the forms and HubSpot is the system of record, and budget for a Professional plan if it must match the design exactly. Build a custom endpoint when a lead needs routing, enrichment or two destinations, fed by Webflow's webhook so the native store and retries stay in the path. The launch test is always the same: one submission from a UTM-tagged URL, traced to the CRM. Our Webflow development service page explains how we scope forms, tracking and integrations inside a four-week build.


