Doesn't count against your plan
Webflow meters native form submissions by site plan at the time of writing. A form in an Embed element posts straight to mailcontact, so Webflow never counts (or caps) it.
integrations · site builder
Webflow's native forms work well, but submissions are metered by your site plan. The monthly allowance depends on which tier the site is on, at the time of writing. The workaround is one Embed element: paste your own form HTML posting to a mailcontact endpoint, and submissions skip Webflow's form handling entirely, landing in a per-project inbox with a ping in Discord, Slack, email, or a webhook.
You keep designing in Webflow. The embed is plain HTML, so you can reuse Webflow's own w-input and w-button classes and the form inherits the styling you already built. Visitors won't see the difference.
And because every mailcontact inbox also comes with a real email address (yourproject@mailcontact.app), messages from your Webflow site and from your other projects end up in one place instead of a separate Forms panel per site.
the snippet
Point the form at your project's mailcontact endpoint. Submissions land in your project inbox. No server, no API route, no email service to wire up.
<form action="https://mailcontact.app/api/forms/your-form-id" method="POST">
<input class="w-input" type="text" name="name" placeholder="Your name" />
<input class="w-input" type="email" name="email" placeholder="you@email.com" required />
<textarea class="w-input" name="message" placeholder="How can we help?" required></textarea>
<button class="w-button" type="submit">Send</button>
</form>how it works
One inbox per site. Name it after your project and you immediately get a form endpoint and a project email address. No DNS, no head code.
In the Designer, drag an Embed element where the form should go, paste the snippet, and publish. The w-input and w-button classes pick up your site's form styling.
Add a Discord, Slack, email, or webhook channel. Every submission pings you, no need to open the site's dashboard to check.
why mailcontact
Webflow meters native form submissions by site plan at the time of writing. A form in an Embed element posts straight to mailcontact, so Webflow never counts (or caps) it.
The embed is your HTML. Give inputs Webflow's w-input class and the button w-button to inherit the form styling you already designed, or target your own classes from custom CSS.
Running several Webflow sites, or Webflow plus other stacks? Each project gets its own inbox and email address, unified in one place instead of a Forms panel per site.
faq
Native Webflow forms come with a monthly submission allowance tied to the site plan at the time of writing (check Webflow's current pricing for exact numbers). A form embedded as your own HTML posting to mailcontact bypasses Webflow's form handling, so those limits don't apply to it.
Webflow gates custom code (including the Embed element) behind paid plans at the time of writing, so check your plan first. If your site plan already allows embeds, the form costs nothing extra and doesn't consume your native submission quota.
Yes, if you tell it to. Add Webflow's w-input class to inputs and w-button to the submit button to inherit the same styling as native Webflow forms, or use your own classes and style them with custom CSS.
The endpoint responds with JSON and doesn't redirect yet, so submit with a few lines of fetch in your embed and swap in an inline thank-you. CORS is open, which means this works from webflow.io staging domains and custom domains alike. A configurable redirect for native form posts is coming with the launch.
related
Forms and a real email address, together, with notifications where you live. Launching soon. Be the first to know.