Contact form for Carrd websites

In Carrd Designer, add a Form widget. Open its settings, change Type to Custom, set Method to POST, set Action to https://splitforms.com/api/submit. Add a hidden field named access_key with your splitforms key. That's it — no Mailchimp account needed.

No — but neither does any custom form solution. Carrd's Form widget requires Pro Standard ($19/year). Once you have Pro Standard, splitforms is free on top.

Carrd's Form widget shows a built-in error message on non-2xx responses. Splitforms returns 4xx with a JSON message for spam/invalid keys — Carrd will display the default error text. Customize it in the form widget's settings.

Yes. Add the access_key hidden field to each form. Use a different form-name hidden field per form (e.g. contact, newsletter) so the splitforms dashboard groups them.

Two options. (1) Use Carrd's built-in success message. (2) Set the absolute thank-you URL in Dashboard → Form settings → Redirect so splitforms sends the browser there after a native submit. Submitted redirect fields are ignored.

Yes. Carrd's exported HTML keeps the form action intact. The form will POST to splitforms from any host — just update the splitforms access-key allowed domains list to match.

Carrd's free plan and Pro Lite don't expose the Form widget at all. Pro Standard ($19/yr) unlocks the Form widget with Type → Custom. Splitforms doesn't change Carrd's plan requirements — it just fills in the backend that Carrd doesn't ship.

If you paste raw HTML via an Embed element, your form will look like browser-default — no Carrd typography, no site colors. Use the native Form widget for styling, then add a hidden access_key field via Custom fields.

Carrd's Form widget has a built-in success message that shows on a 2xx response. If you also configure a redirect in the splitforms dashboard, the success state may flash before navigation. Pick one: the splitforms dashboard redirect or Carrd's success text.

Carrd uses friendly labels like 'Your name', but the actual input name attribute is name-1 or similar unless you set Custom in the field settings. Set the Custom name to name, email, message — splitforms uses the input names as keys in your inbox.

Carrd's Designer preview never actually POSTs the form. To test, publish the site (Carrd publishes free to a *.carrd.co subdomain) and submit from the live URL. Lock the splitforms access key to that subdomain in the dashboard.

If your one-pager sits behind Carrd's Pro Plus password gate, the page itself loads only after a session cookie is set — but Carrd's password layer also adds a Referer-Policy: no-referrer header to outbound form posts. Splitforms's domain-locked access keys verify the Origin header, which becomes null under that policy, so legitimate submissions get rejected as off-domain. Either disable password protection on the contact page specifically, or set the access key to allow null origins (NOT recommended for production — anyone can replay the key from any page).

Carrd's Form widget requires Pro Standard ($19/year) just to exist on the page, and even then it doesn't deliver email itself — the form 'works' by posting to an external integration: Mailchimp, SendGrid, Basin, Formspree, etc. So the question isn't 'native vs splitforms' but 'which third-party backend do you wire up?'. Mailchimp is overkill (and surprisingly expensive once your list grows); Basin and Formspree limit free submissions; SendGrid requires DNS verification. Splitforms is the same shape of integration (Type: Custom, Method: POST, Action: a URL) at a better free tier and with built-in spam filtering. Carrd's Form widget settings don't change.

Carrd publishes to a *.carrd.co subdomain on every plan; Pro Standard adds a custom domain. The form posts to splitforms from the browser, so neither subdomain nor custom domain matters for delivery. Lock the splitforms access key to BOTH the *.carrd.co URL and your custom domain — Carrd serves the same content under both, with different Origin headers. Carrd's Designer preview never actually POSTs; you have to publish (free) and submit from the live URL to test. Embed elements bypass Carrd's CSS, so the form will look browser-default unless you inline styles.