Webflow's form designer is genuinely good — no reason to give it up. What you might want to change is where submissions go: by default Webflow stores them and meters them per site plan. A Webflow form can post to any endpoint instead. It's one setting, your design stays exactly as it is.
You only need the delivery address here, not the whole
HTML. Build a form in the free hform builder
with roughly the same fields as your Webflow form, press
Finish, and copy the address from the generated
HTML's action attribute — it looks like
https://hform.com/s/your-form-id.
In the Webflow Designer, select your Form element and open its settings. In Action, paste your hform address; set Method to POST.
Each input's name attribute becomes the label
you'll see in messages — make them meaningful: name,
email, message, not field-2.
Set them in each field's settings panel.
Publish and submit the form once. With a custom action, the browser follows the post — your visitor lands on the thank-you page (or any address you choose in your form's settings), rather than seeing Webflow's inline success message. When it works, a submission shows your visitor a clean thank-you page (or any page you choose), and the message lands in your email inbox with reply-to set to the sender — answer it like any other email. A copy stays in your hform inbox, downloadable as a spreadsheet.
The other route is Webflow's Embed element with the full HTML from the builder. It works, but custom-code embeds require a paid Webflow site plan, and you give up the Designer for that element. Setting the Action on a native Webflow form is usually the better move.
To be fair to Webflow: its own form handling is fine if your plan's submission allowance covers you and you're happy managing submissions there. Redirecting to your own endpoint is for when the limits chafe or you want messages stored in a place you control — EU-hosted, with reply-to and CSV export.
Form submissions are personal data. If EU residents can submit your form, GDPR expects you to say near the form what the data is used for, ask only for what you need, and delete what you no longer use. With hform your messages are stored in the EU (Sweden) with automatic retention limits — and a one-line privacy note under the form ("We use your details only to reply to your message") covers the common small-business case. The full picture, without legalese: GDPR and web forms in plain language.
Yes. Submissions go straight from the visitor’s browser to hform, so they never count against Webflow’s per-plan submission allowance. They count against your hform plan instead — the free tier includes 100 messages a month.
No — with a custom Action the browser follows the post, and your visitor lands on a clean thank-you page (or any address you configure). Webflow’s inline success and error states only apply to forms Webflow itself handles.
Setting a form’s Action is part of the Designer. It’s the Embed-element route (pasting whole custom HTML) that requires a paid site plan — one more reason the Action route is the clean one.
The hform builder gives you clean, accessible form HTML with delivery wired in — press Finish and paste it into Webflow with the steps above. Free plan included; honest pricing if you outgrow it.
More platforms: WordPress · Shopify · Wix · Squarespace · Static sites — or see all guides.