Use your platform's native builder for a simple form, and a plain HTML form with a hosted backend when you want one form that works on any site. The table below compares the native builder, HTML embed support and whether a separate backend is needed on WordPress, Wix, Squarespace, Shopify, Webflow, Notion, Ghost and Google Sites.
Each platform name links to the setup page its details came from. “Native builder” is the form tool the platform ships with, “HTML embed” is whether you can paste your own form markup, and “separate backend” is whether you need a hosted service to receive, store and email submissions.
| Platform | Native builder | HTML embed support | Separate backend needed |
|---|---|---|---|
| WordPress | No native form; use a plugin such as Contact Form 7 or WPForms, or the splitforms plugin. | Yes — a Custom HTML block accepts a plain HTML form. | Yes for reliable delivery; a form plugin or splitforms handles it. |
| Wix | Wix Forms, with entries stored in a submissions table you can export. | Yes — Add Elements > Embed Code > Embed HTML. | No for Wix Forms; yes for a custom HTML form. |
| Squarespace | Form Block, which emails submissions and can connect storage options. | Yes — a Code Block accepts HTML on every plan, including Basic. | No for the Form Block; yes for a custom HTML form. |
| Shopify | Theme contact form built with Liquid. | Yes — a Custom HTML block or a Liquid section. | Optional; add one for dashboard storage, spam filtering and webhooks. |
| Webflow | Form Block, capped at 50 submissions per month on Free and 500 total on Basic. | Yes — an Embed element accepts raw HTML on every plan. | Yes for reliable email at volume; Form Block forwarding is unreliable on Basic. |
| Notion | No native contact form for published Notion sites. | Yes — a code or HTML embed through Super.so, Potion.so or Feather. | Yes — a hosted form backend or third-party embed is required. |
| Ghost | No native contact form; the members portal only handles sign-ups. | Yes — an HTML card accepts a plain HTML form. | Yes — point the form at a hosted form backend. |
| Google Sites | No native form; the usual option is a Google Forms embed. | Yes — an Embed block accepts HTML code. | Yes — a hosted form backend or Google Forms is required. |
There is no single best builder. Pick the one that matches how much control you want over the form and where the submissions should live.
If a basic form is all you need, use the builder your platform already ships: Wix Forms, the Squarespace Form Block, or a WordPress form plugin. You get a form in minutes, but storage and spam tools stay inside that platform.
Use a plain HTML form that posts to a hosted backend. The same form works on WordPress, Wix, Squarespace, Shopify, Webflow, Notion, Ghost and Google Sites, and every submission lands in one dashboard with the same spam rules.
The native Form Block caps at 50 submissions per month on Free and 500 total on Basic, and its email forwarding is unreliable on Basic. Replace it with an HTML form inside an Embed element so submissions go straight to your inbox.
None of these has a native contact form. Paste an HTML form into a code or embed block and point it at a hosted backend; no theme edit or plugin is needed.
Copy the fields into the new builder's HTML or embed block, point the form action at your backend endpoint, and add your access key. Submit a test entry and confirm it reaches your inbox and dashboard before you remove the old form. The form backend migration checklist covers the same steps, and the contact form backend guide shows the endpoint and spam fields to add.
Use your platform's native builder if you only need a simple form and want it inside that platform. Use a plain HTML form with a hosted backend if you want one form that works on any site, a searchable dashboard, spam filtering and webhooks. On Webflow, the native Form Block is capped at 50 submissions per month on the Free plan and 500 total on Basic, and its email forwarding is unreliable on Basic, so an HTML embed is the safer choice.
Not always. Wix Forms, the Squarespace Form Block and a WordPress form plugin can store and email submissions on their own. You need a separate backend when you use a custom HTML form, when you want one inbox and dashboard across several sites, or when you need spam filtering and webhooks the platform does not provide.
Yes. WordPress has a Custom HTML block, Wix has Embed Code > Embed HTML, Squarespace has a Code Block, Shopify has a Custom HTML block or Liquid section, Webflow has an Embed element, Notion sites use Super.so, Potion.so or Feather, Ghost has an HTML card, and Google Sites has an Embed block.
The Webflow Form Block is capped at 50 submissions per month on the Free plan and 500 total on Basic. Email forwarding is unreliable on Basic, and the Form Block does not work well at meaningful volume. The CMS plan raises the cap and fixes forwarding, or you can use an HTML form in an Embed element on any plan.
Copy the form fields into the new builder's HTML or embed block, point the form action at your backend endpoint, and add your access key. Then submit a test entry and confirm it reaches your inbox and dashboard before you remove the old form. The form backend migration checklist walks through the same steps.
splitforms has a free plan with 500 submissions total, unlimited forms, spam filtering, dashboard storage and email notifications, with no credit card. Paid plans start at $5 per month for 5,000 submissions a month and add webhooks, integrations and exports.
Paste the same HTML form into any platform on this page. The free plan covers 500 submissions total with unlimited forms, spam filtering, dashboard storage and email notifications, with no credit card.
