WAITLIST · FRAMER

Waitlist for Framer

Pre-launch capture form with optional referral source. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code

500/mo free·no card·drop-in for Framer

form.htmlhtml23 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Framer + Waitlistplatform-specific integration guide

Why Framer developers choose splitforms for waitlist

Framer's code component feature lets you drop custom HTML directly into your design, which is where this waitlist fits. Framer's built-in form actions are limited — they forward to a Framer webhook that lacks email delivery, spam filtering, and a dashboard. The waitlist on this page bypasses Framer's form system entirely: paste it into a code component, and submissions go straight to splitforms for email, webhooks, spam filtering, and dashboard storage. Framer handles the design; splitforms handles the delivery.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for Framer.

Use the HTML snippet on this page, keep the waitlist fields visible in your Framer UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the HTML version, then replace YOUR_ACCESS_KEY.

The posted payload contains email, name, how did you hear about us?. Required fields are email.

native framer reality

use case fit

Pre-launch waitlists let you capture demand before the product ships. The multi-step form qualifies the use case so launch-day conversions skew toward the highest-intent signups.

§ 01Waitlist × Framerwhy this combination, in 80 words

Built for Framer developers who hate operating a backend.

Splitforms is the form backend for Framer sites. One POST endpoint, no SDK, no plugin — drop the waitlist into a page and ship.

Splitforms is the form backend for Framer sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan

✓500 form submissions per month
✓2 forms on Free; unlimited forms on Pro
✓Spam protection (honeypot + classifier)
✓Webhooks: Slack, Discord, WhatsApp, custom
✓CSV export of all submissions
✓Email notifications (CC and BCC on Pro)

§ 02Copy-paste codeHTML · 23 lines

Drop into any Framer project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Framer page, and ship. No build-time integration required.

form.htmlhtml23 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first waitlist submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the waitlist into your Framer project

Drop the form snippet into a Framer page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippethtml

<form action="https://splitforms.com/api/submit" method="POST">
  …
</form>

STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now

FROM contact@yoursite.com

New waitlist signup

Maya Iyer maya@studio71.co

Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?

§ 03bWaitlist Signup Form (Pre-Launch Lead Capture)template-specific playbook

The reason this waitlist exists.

Multi-step (Typeform-style) · webhooks into Loops / ConvertKit / Beehiiv.

why it matters

Waitlists are the cheapest growth tool a pre-launch product has — Superhuman, Notion, and Linear all built sizable waitlists before paid launch. The form captures email plus a question or two on use case ('what would you use this for?', 'what tools do you use today?') so the launch sequence segments by intent. Multi-step flow boosts completion vs a single form — the prospect commits in step 1 and answers the qualifying questions in step 2-3 with momentum. Push waitlist signups to a dedicated ESP audience (Loops, ConvertKit, Beehiiv) so launch-day emails segment by use case and target the highest-intent signups first.

route the submission

Step 1: capture email

Single email field — keep step 1 frictionless. Loss-rate from email-only is near-zero; once the email is in, momentum carries through later qualifying questions.

Step 2-3: qualify use case

One or two questions on use case ('what problem brings you here?', 'what tools do you use today?'). Optional but most users complete because they're invested by step 2.

Push to ESP segment

Webhook to Loops / ConvertKit / Beehiiv / Mailchimp into a 'waitlist' audience. Launch-day emails segment by use case so the highest-intent signups get the first invite waves.

§ 03cFramer production notesnative path · deploy · gotchas

What changes when this waitlist lives in Framer.

These notes come from the Framer platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Framer's built-in form widget delivers submissions to a single email address (configured per form) with no dashboard for managing submissions, no webhooks below the Pro plan, and no spam filtering beyond Framer's basic bot detection. CMS-driven Framer forms inherit the same constraints. The native flow works for a portfolio's contact form; it falls apart for any setup that needs Slack/Discord notifications, multiple recipients, CSV export, or tagged form-name routing. Replacing it means writing a Code Component — Framer's mechanism for embedding custom React. That's the pattern splitforms uses: a Code Component with the access key as a property control, dropped onto the canvas like a native widget.

deploy notes

Framer publishes sites to its own CDN — there's no Vercel/Netlify config to manage. The form posts cross-origin to splitforms regardless. Framer's published sites have a default Content Security Policy that may block connect-src to splitforms.com on some plans; if submissions silently fail, add <meta http-equiv="Content-Security-Policy" content="connect-src https://splitforms.com"> via Site Settings → Custom Code → Head HTML. Lock the access key to BOTH your *.framer.app preview URL AND your custom domain — Framer serves both with different Origin headers. Framer's preview environment runs Code Components live, so you can test the form before publishing.

Framer gotcha

addPropertyControls must be the LAST statement in the file

Framer reads property controls only if addPropertyControls(Component, {...}) is called after the component is exported. If you put it before the export or wrap it in a conditional, the access-key control disappears from the right panel and you can't set the key visually.

Framer gotcha

Framer's canvas re-renders the component on every prop change

Editing the access key in the right panel re-mounts the form mid-edit. If a user is testing the form when you change the key, their status === 'loading' state resets to 'idle' visually but the in-flight fetch still completes. Not a bug in production — only an editor quirk.

Framer gotcha

Framer's published page CSP blocks splitforms.com unless you set it

Framer's published sites have a default Content Security Policy that allows known integrations. Splitforms isn't on the default allowlist — you may need to add connect-src https://splitforms.com via Framer's Site Settings → Custom Code → Head HTML, inside a <meta http-equiv="Content-Security-Policy" content="…"> tag.

Framer gotcha

Code Components don't get Framer's font system by default

If you use style={{ fontFamily: '...' }} in a Code Component, you have to import the font manually — Framer's site fonts only auto-apply to canvas-built elements. Use font-family: inherit to inherit from the parent frame.

PATTERN A

Pattern A — Code Component with property control

Paste into Framer's Code Components panel. The access key becomes a property in the right-side inspector — designers swap keys per page or per environment without touching code. Use the same wiring for the waitlist fields on this page.

pattern-a.tsxtsx19 lines

01// ContactForm.tsx (Framer Code Component)
02import { useState } from "react";
03import { addPropertyControls, ControlType } from "framer";
04export default function ContactForm({ accessKey = "YOUR_ACCESS_KEY" }) {
05  const [status, setStatus] = useState<"idle" | "loading" | "ok" | "err">("idle");
06  return (
07    <form onSubmit={async (e) => {
08      e.preventDefault(); setStatus("loading");
09      const fd = new FormData(e.currentTarget);
10      fd.append("access_key", accessKey);
11      const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
12      setStatus((await r.json()).success ? "ok" : "err");
13    }} style={{ display: "grid", gap: 12 }}>
14      <input name="email" type="email" required />
15      <button disabled={status === "loading"}>Send</button>
16    </form>
17  );
18}
19addPropertyControls(ContactForm, { accessKey: { type: ControlType.String } });

PATTERN B

Pattern B — Framer override (apply to existing canvas form)

If you already designed a form on the canvas with Framer's native form widget, an override can intercept its submit and re-route to splitforms. Useful when you want to keep the canvas-built design but swap the backend. Use the same wiring for the waitlist fields on this page.

pattern-b.tsxtsx12 lines

01// SplitformsOverride.tsx
02import type { ComponentType } from "react";
03export function withSplitforms(Component): ComponentType {
04  return (props) => (
05    <Component {...props} onSubmit={async (e) => {
06      e.preventDefault();
07      const fd = new FormData(e.currentTarget);
08      fd.append("access_key", "YOUR_ACCESS_KEY");
09      await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10    }} />
11  );
12}

§ 04Field-by-field rundown3 fields · names you POST

What every field actually does.

Each field below ships in the waitlist template — rename, remove, or add your own. Splitforms accepts any name you POST.

emailREQUIRED

Email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · you@example.com

name

TEXT

Name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Optional

referral

SELECT

How did you hear about us?

Dropdown — keeps responses normalised so you can filter the dashboard.

TwitterFriendSearchNewsletterOther

§ 05Waitlist on other frameworks21 frameworks · same backend

One backend. Every framework.

The same waitlist template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Waitlist on Framer — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this waitlist work on Framer?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Framer site without server-side code, plugins, or SDKs. Drop the snippet into a Framer page or component and submissions land in your splitforms dashboard.

02How much does the waitlist cost on Framer?

Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.

03Can I customize the fields?

Yes. The template ships with sensible defaults (email, name, how did you hear about us?…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the waitlist?

A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Framer as on any other framework.

05Can I send the waitlist submissions to Slack or Discord?

Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.

06Will it work on a static Framer site?

Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.

07Should I show waitlist position / numbers?

Showing 'you're #347 in line' on the confirmation creates social proof but invites comparison. Showing total waitlist size ('join 2,500 people on the waitlist') without per-person position is the safer middle. Refer-a-friend mechanics that move people up the list (Robinhood-style) drive viral growth but require more eng work.

08How do I trigger launch invites in waves?

Tag waitlist signups by use case in the ESP audience (Loops, ConvertKit). Launch-day, segment by tag and send invite waves over 48-72 hours. Highest-intent / closest-fit goes first; broadest casts go last. Spreads server load and lets you triage onboarding support.

09Can I integrate with Loops / ConvertKit / Beehiiv?

Yes — webhook the JSON. Loops has direct webhook support and is purpose-built for product transactional + waitlist email. ConvertKit and Beehiiv accept via API or Zapier. All three handle the launch-sequence segmentation cleanly.

§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for Framer5 adjacent patterns

Ship a waitlist on Framer in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Framer project.

Get free access key →Read the docs

founders pricing locked in · early access open

Waitlist for Framer

Why Framer developers choose splitforms for waitlist

Yes — this is the shortest safe path for Framer.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Framer developers who hate operating a backend.

Drop into any Framer project.

Generate, embed, receive.

Generate a free splitforms key

Paste the waitlist into your Framer project

Receive submissions

The reason this waitlist exists.

Step 1: capture email

Step 2-3: qualify use case

Push to ESP segment

What changes when this waitlist lives in Framer.

addPropertyControls must be the LAST statement in the file

Framer's canvas re-renders the component on every prop change

Framer's published page CSP blocks splitforms.com unless you set it

Code Components don't get Framer's font system by default

Pattern A — Code Component with property control

Pattern B — Framer override (apply to existing canvas form)

What every field actually does.

Email

Name

How did you hear about us?

One backend. Every framework.

Waitlist on Framer — FAQ.

splitforms vs everything else.

Other ready-to-ship Framer forms.

Ship a waitlist on Framer in 60 seconds.