Webflow Forms: What They Do and Their Real Limits

Webflow's built-in form element collects submissions, emails you a notification, and filters spam automatically, with no third-party service required — as long as the site is hosted on Webflow. The limits that actually matter are the free plan's submission cap, a separate feature gate on file uploads, and a hard rule that has nothing to do with plan level: forms stop working the moment you export a site's code to host it elsewhere. Here's what each part of the system does, and where the boundaries actually sit, per Webflow's own help documentation, checked September 2026.

How many submissions can a Webflow form collect?

This is a plan-based limit, and it's a lifetime count, not a monthly one. Webflow's help center states it plainly: "Sites on the free Starter Site plan are limited to 50 total form submissions. This limit doesn't reset," and "form submissions are unlimited on all other Site plans" (Webflow). Once a Starter-plan site hits that 50th submission, "new form submissions will no longer be collected" until you upgrade — visitors can still fill out and submit the form, but nothing more gets recorded.

Webflow's current Site plans (per webflow.com/pricing, checked September 2026, yearly billing) are Starter (free), Basic ($15/mo), and Premium ($25/mo), plus Team and Enterprise Platform plans for organizations — our Webflow pricing guide covers what each tier unlocks beyond forms. Starter's plan card explicitly lists "50 form submissions" as one of its limits; Basic and Premium both list "Unlimited form submissions." If your form is the primary way visitors contact you — a lead form, a waitlist, a job application — that free-plan cap is the first thing to check before you rely on it for anything real.

Where do form submissions actually go?

By default, submissions land inside Webflow itself: "If you've chosen to send a form's submissions to Webflow, you can view and manage them in Site settings > Forms," where you also configure email notifications per form (Webflow). From that same panel you get a submission count and a data table per form, with any uploaded files shown as clickable links rather than embedded attachments.

You can download everything as a CSV: go to Site settings > Forms, find the form, click View submissions, then Export all, and "the CSV file includes all submission data for that form" (same source). If a submission included a file upload, the exported CSV links back to Webflow's own file storage rather than including the file itself — download and save those files separately before you delete any submissions, since "deleting form submissions will also delete the file submissions and make the submitted file URLs inaccessible."

One naming trap worth knowing about: "by default, all form names are set to 'Email Form.'" If you have more than one form on a site and never renamed them, submissions from every form pile into the same bucket in your dashboard with no way to tell them apart after the fact.

How do email notifications work?

Webflow sends a notification automatically: "by default, Webflow sends form notifications to the email address associated with your account," and you can customize the recipient list, sender name, reply-to address, subject line, and message body per form, or set a site-wide default new forms inherit. Notifications come from a Webflow-branded address (no-reply-forms@webflow.com), and — a detail worth knowing if you're troubleshooting deliverability — Webflow specifically recommends against a role-based recipient address like info@ or support@, since "these are typically shared addresses" that can cause delivery issues; a name-based address like jane@ is the documented recommendation.

The free Starter plan also caps who can receive notifications: "form notification emails are limited to five recipients, and all recipients must be Workspace members." Paid Site plans lift that recipient limit and let you notify people outside your Workspace. Separately, if you want the notification itself to drop Webflow's branding entirely and come from an unbranded address, that requires upgrading your Workspace plan (a different purchase from your Site plan) to Growth.

What spam protection does Webflow offer?

Webflow documents four spam-prevention methods for forms, and they can be combined rather than being mutually exclusive (Webflow):

• CAPTCHA — a reCAPTCHA field you add to the form, which "asks site visitors to identify themselves as human before submitting a form." Webflow's own documentation notes the tradeoff directly: CAPTCHA "can negatively impact user experience, and can also be circumvented by more advanced bots."
• Bot blocking — a site-level toggle under Site settings > Apps & Integrations > Cloudflare Turnstile spam protection that "uses AI to analyze mouse movements, inputs, and other signals on your site to separate bots from valid site users," applied automatically across every form on the site once turned on.
• Spam filtering — a second Cloudflare Turnstile setting that "checks all form data sent on your site to determine and filter out spam submissions," again site-wide.
• The honeypot technique — a hidden field added via custom code; if something fills it in, that's treated as a bot and the submission is discarded, since a real visitor never sees or fills in a hidden field.

None of these require a specific paid plan; they're setting toggles available on any Site plan.

Can visitors upload files through a Webflow form?

Not on every plan. File upload is gated to specific tiers: "if your site is on the Premium Site plan (or legacy Business Site plan), Ecommerce Plus Site plan, or Ecommerce Advanced Site plan, you can add a File upload button to your forms" (Webflow). On the current three-tier lineup, that means Premium specifically — Starter and Basic don't include it, which matches Premium's plan card listing "Form file upload" as one of the features it adds on top of Basic.

Where it is available, each upload button "accepts a single file of up to 10MB in size," across a defined list of document, image, audio, video and archive formats, and you can add up to 20 separate upload buttons per form (useful for something like "attach your résumé" and "attach a cover letter" as two distinct fields). Storage is metered separately from the plan itself: "form file upload storage is free up to 10GB, and $0.50/month per GB after that," with a hard ceiling — "we place a hard storage limit at 100GB, at which point form submissions will no longer be collected, and this limit cannot be increased." You can only reclaim that storage by deleting old submissions.

By default, uploaded files require a Webflow login to access, even with the direct link — a real privacy safeguard, but one that will silently break a third-party integration expecting public file URLs unless you turn it off under Site settings > Apps & Integrations > Restrict uploaded file access.

What happens to forms if I export my site's code?

This is the limit that has nothing to do with your plan tier, and it catches people who assume "paid plan" means "fully working forms everywhere." Webflow's export documentation is direct about it: "if you've exported your site for external hosting, Webflow will not process form submissions on your site. You'll need to use a third-party tool to collect form submissions on the exported site or embed a third-party form integration." The form element itself still renders in the exported HTML — it just does nothing when submitted, because it depends on Webflow's own backend to process it.

That's a deliberate design decision, not a bug: Webflow's forms documentation ties it to GDPR compliance, since an exported site no longer has any relationship with Webflow's data-processing infrastructure. Our guide to Webflow's code export covers what a code export does and doesn't include in full, including the third-party form services you'd wire up in place of the native element once you're self-hosting.

What should I check before I rely on a Webflow form?

• Confirm your Site plan — if you're still on the free Starter plan, you have 50 lifetime submissions before the form silently stops collecting new entries.
• Name every form something distinct in the Designer, before launch, so submissions don't all merge into a generic "Email Form" bucket.
• Use a name-based notification address (jane@, not info@) to avoid the deliverability issue Webflow itself flags.
• If the form needs a file upload field, confirm you're on Premium (or a legacy Business/Ecommerce Plus/Ecommerce Advanced plan) before you build it — it's not available on Starter or Basic.
• If you ever plan to export this site's code and self-host it, plan for a replacement form service now. The native form simply stops functioning on export; there's no setting to turn it back on afterward, only a third-party integration to add in its place.

Bottom line: for a site that stays hosted on Webflow, the native form covers submissions, notifications and spam filtering without any extra setup — the only real gates are the free plan's 50-submission lifetime cap and the Premium-only file upload field. The one limit worth planning around from day one, regardless of plan, is that native forms don't survive a code export at all.