Webflow form submission limit: what it is and how to get past it

On the free Starter site plan, Webflow collects 50 form submissions per site in total, the count doesn't reset, and new submissions are not collected after that. Paid site plans list unlimited submissions, and sites exported to another host get no form handling at all. Set a custom action on the Form Block so the form posts to Ikiform, which works on Starter, on paid plans and in exported code.

What's different on Webflow

Webflow's limit is narrower than it used to be. As of October 2026, its pricing page lists 50 form submissions on the free Starter site plan and unlimited submissions on every paid site plan, starting with Basic. Webflow's help center says the Starter count is a total that doesn't reset. Older articles that quote monthly caps for paid plans describe pricing that has since changed.

So who actually hits the wall? Three groups:

• Sites that stay on Starter. A personal site, a side project or an event page published on webflow.io without a site plan. Fifty submissions go fast once a bot finds the form.
• Agencies building on staging. Every test submission while you build counts toward the same 50, before the client has paid for hosting.
• Exported sites. Webflow's code export gives you the HTML, but forms on a site hosted elsewhere aren't processed by Webflow at all. The form posts nowhere useful.

If your site is on a paid plan and you're happy with Webflow's inbox and notifications, you don't need to move. People on paid plans move for other reasons: one place for forms across several sites, signed webhooks to their own tools, spam filtering they can tune, or a form that survives a move off Webflow.

Set the custom action in the Designer

A custom action makes the visitor's browser post straight to the URL you give it. Webflow doesn't process the post, so it isn't one of Webflow's form submissions. The Form Block setting is available on Starter; you don't need custom code for this part.

1. Create a form in the Ikiform dashboard and copy its endpoint.
2. In the Designer, select the form element inside the Form Block, not the block itself, and open Settings.
3. Under Send to, remove Webflow's own destinations, choose a custom action, paste the endpoint into Action and set Method to POST.
4. Select each input and set its Name to a lowercase id: name, email, company, message. Webflow fills names from labels, which would give you Name and Field 2 in Ikiform.
5. Remove any reCAPTCHA element from the form. Ikiform doesn't check it, and its token would arrive as an extra field.
6. Add one more Input named _gotcha, hide it with Display: none, and add the custom attributes tabindex = -1 and autocomplete = off. That's the honeypot.
7. Publish to your-site.webflow.io. Custom actions don't run in the Designer canvas.

https://ikiform.com/f/frm_xxxxxxxxxxxxxxxx

What visitors see after they submit

Webflow's success and error blocks only appear when Webflow handles the post. With a custom action, the browser follows Ikiform's answer instead. Pick one of these:

On Starter, the redirect is the right choice: it needs no code and looks like the rest of your site. The script for paid plans is in the Webflow docs. It posts with fetch, so it can't show Ikiform's human check; leave the Spam check off if you use it.

Exported Webflow sites

When you export code and host it on Netlify, Vercel, Cloudflare Pages or your own server, the form markup comes with it but Webflow's form handling doesn't. Open the exported HTML file that holds the form, set the action and method, rename the inputs, and add a redirect and the honeypot:

<form id="wf-form-Contact" name="wf-form-Contact" data-name="Contact"
  method="post" action="https://ikiform.com/f/frm_xxxxxxxxxxxxxxxx" class="contact-form">
  <label for="name">Name</label>
  <input class="w-input" maxlength="256" name="name" id="name" type="text" required>
  <label for="email">Email</label>
  <input class="w-input" maxlength="256" name="email" id="email" type="email" required>
  <label for="company">Company</label>
  <input class="w-input" maxlength="256" name="company" id="company" type="text">
  <label for="message">Message</label>
  <textarea class="w-input" maxlength="5000" name="message" id="message" required></textarea>
  <input type="hidden" name="_redirect" value="https://studio.example/thanks">
  <input name="_gotcha" type="text" tabindex="-1" autocomplete="off" hidden>
  <input type="submit" class="w-button" value="Send">
</form>

• Keep the w-input and w-button classes so the exported CSS still styles the form.
• _redirect sends the browser to your thank-you page after a successful post. It only works for an https: URL on one of the form's Allowed domains.
• Make the change in the Designer too, as a custom action, so the next export doesn't overwrite it with Webflow's default.
• Submit once from the host and watch the browser's network panel. The post should go to https://ikiform.com/f/ and answer 303 with a redirect, not to a Webflow address.

Allowed domains for Webflow

Add your-site.webflow.io and your custom domain under the form's Allowed domains. Subdomains of a listed domain already match, so example.com covers www.example.com. Don't add webflow.io on its own: that would allow every Webflow site to post to your form. For an exported site, add the domain it's hosted on.

Webflow's file upload field, which its pricing page lists on Premium, has no Ikiform equivalent. File uploads aren't supported yet. A post with a file gets 422 files_not_supported. Remove the upload field from the form, or keep that one form on Webflow.

Check it works on Webflow

1. Under the form's Allowed domains, add your site's domain, plus localhost while you develop. Leave it empty to accept posts from anywhere.
2. Publish to webflow.io and submit the form from the published page, not the Designer.
3. Confirm you land on your thank-you page, or see Webflow's success block if you added the script.
4. Open Submissions in the dashboard. The new submission is there with every field you sent.
5. Read the field names. They should be name, email, company and message, with no Field 2 and no honeypot.
6. Check the inbox of each notification recipient. Each gets an email with the fields, and Reply goes to the submitter when the form has an email field.
7. Open Webflow's form submissions for the site and confirm the test isn't there. Webflow no longer counts it.

Gotchas

Questions