WAITLIST · REACT

Waitlist for React

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 React

Form.tsxtsx52 lines

01'use client';
02 
03import { useState, type FormEvent } from 'react';
04 
05export default function WaitlistForm() {
06  const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07 
08  async function onSubmit(e: FormEvent<HTMLFormElement>) {
09    e.preventDefault();
10    setStatus('sending');
11 
12    const data = new FormData(e.currentTarget);
13    data.set('access_key', 'YOUR_ACCESS_KEY');
14    data.set('subject', 'New waitlist signup');
15 
16    const res = await fetch('https://splitforms.com/api/submit', {
17      method: 'POST',
18      body: data,
19      headers: { Accept: 'application/json' },
20    });
21 
22    const json = await res.json();
23    setStatus(json.success ? 'sent' : 'error');
24    if (json.success) e.currentTarget.reset();
25  }
26 
27  if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28 
29  return (
30    <form onSubmit={onSubmit}>
31      <label htmlFor="email">Email *</label>
32      <input id="email" type="email" name="email" placeholder="you@example.com" required />
33      <label htmlFor="name">Name</label>
34      <input id="name" type="text" name="name" placeholder="Optional" />
35      <label htmlFor="referral">How did you hear about us?</label>
36      <select id="referral" name="referral">
37        <option value="">Choose…</option>
38        <option>Twitter</option>
39        <option>Friend</option>
40        <option>Search</option>
41        <option>Newsletter</option>
42        <option>Other</option>
43      </select>
44 
45      <button type="submit" disabled={status === 'sending'}>
46        {status === 'sending' ? 'Sending…' : 'Send'}
47      </button>
48 
49      {status === 'error' && <p>Something went wrong. Try again.</p>}
50    </form>
51  );
52}

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00React + Waitlistplatform-specific integration guide

Why React developers choose splitforms for waitlist

React ships nothing for form delivery — it's a view layer. The historical options are an Express server you stand up just for POST /api/contact, a Vercel serverless function with SMTP wiring, or a third-party library like Formik that still leaves the backend problem unsolved. The waitlist on this page uses <code>useState</code> for submit state and a plain <code>fetch</code> POST to splitforms — no form library, no context provider, no wrapper component. It works in Create React App, Vite, Remix, and every React bundler because it's just standard <code>FormData</code> and the Fetch API.

§ 00Quick answerReact / Next.js · marketing

Yes — this is the shortest safe path for React.

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

best implementation

Paste the React / Next.js version, then replace YOUR_ACCESS_KEY.

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

native react reality

React itself ships nothing for form submission — it's a view layer.

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 × Reactwhy this combination, in 80 words

Built for React developers who hate operating a backend.

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

Splitforms is the form backend for React 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 codeReact / Next.js · 52 lines

Drop into any React project.

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

Form.tsxtsx52 lines

01'use client';
02 
03import { useState, type FormEvent } from 'react';
04 
05export default function WaitlistForm() {
06  const [status, setStatus] = useState<'idle' | 'sending' | 'sent' | 'error'>('idle');
07 
08  async function onSubmit(e: FormEvent<HTMLFormElement>) {
09    e.preventDefault();
10    setStatus('sending');
11 
12    const data = new FormData(e.currentTarget);
13    data.set('access_key', 'YOUR_ACCESS_KEY');
14    data.set('subject', 'New waitlist signup');
15 
16    const res = await fetch('https://splitforms.com/api/submit', {
17      method: 'POST',
18      body: data,
19      headers: { Accept: 'application/json' },
20    });
21 
22    const json = await res.json();
23    setStatus(json.success ? 'sent' : 'error');
24    if (json.success) e.currentTarget.reset();
25  }
26 
27  if (status === 'sent') return <p>Thanks — we&rsquo;ll be in touch.</p>;
28 
29  return (
30    <form onSubmit={onSubmit}>
31      <label htmlFor="email">Email *</label>
32      <input id="email" type="email" name="email" placeholder="you@example.com" required />
33      <label htmlFor="name">Name</label>
34      <input id="name" type="text" name="name" placeholder="Optional" />
35      <label htmlFor="referral">How did you hear about us?</label>
36      <select id="referral" name="referral">
37        <option value="">Choose…</option>
38        <option>Twitter</option>
39        <option>Friend</option>
40        <option>Search</option>
41        <option>Newsletter</option>
42        <option>Other</option>
43      </select>
44 
45      <button type="submit" disabled={status === 'sending'}>
46        {status === 'sending' ? 'Sending…' : 'Send'}
47      </button>
48 
49      {status === 'error' && <p>Something went wrong. Try again.</p>}
50    </form>
51  );
52}

ALTPrefer plain HTML? View the universal waitlist HTML snippet23 lines

form.htmlHTML

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <input type="hidden" name="subject" value="New waitlist signup">

  <label for="email">Email *</label>
  <input id="email" type="email" name="email" placeholder="you@example.com" required>
  <label for="name">Name</label>
  <input id="name" type="text" name="name" placeholder="Optional">
  <label for="referral">How did you hear about us?</label>
  <select id="referral" name="referral">
    <option value="">Choose…</option>
    <option>Twitter</option>
    <option>Friend</option>
    <option>Search</option>
    <option>Newsletter</option>
    <option>Other</option>
  </select>

  <!-- honeypot — bots fill every field -->
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">

  <button type="submit">Send</button>
</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 React project

Drop the form snippet into a React 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.

snippettsx

'use client';
  …
</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.

§ 03cReact production notesnative path · deploy · gotchas

What changes when this waitlist lives in React.

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

without splitforms

React itself ships nothing for form submission — it's a view layer. The historical baseline is one of: an Express/Hono/Fastify server you stand up just for POST /api/contact, a Function-as-a-Service (Vercel/Netlify/Cloudflare) that ends up needing the same SMTP wiring, or a third-party form library (React Hook Form, Formik) that handles validation but still leaves you to operate the backend. Vite, CRA, and Remix all default to assuming you have somewhere to POST — they just don't tell you where. Splitforms is the where: a single fetch call, no library install, no useEffect gymnastics, no Express boilerplate.

deploy notes

Vite-built React apps are static — they deploy to any static host (Vercel, Netlify, Cloudflare Pages, S3, GitHub Pages). The splitforms fetch is cross-origin, so configure your CSP to allow connect-src 'self' https://splitforms.com if you have one. Vite reads env vars from .env at build time and only exposes those prefixed VITE_ to the browser bundle. CRA uses REACT_APP_ instead. On Cloudflare Pages, the build output is served from the edge with sub-50ms cold starts; splitforms adds another ~30ms RTT — not noticeable in practice. Lock the access key to your live origin in the splitforms dashboard.

React gotcha

useState + setStatus inside async causes race conditions

If a user double-clicks submit before the first request settles, you'll fire two POSTs. Always disable the button while status === 'loading'. Better still, also use an AbortController to cancel the in-flight request if a re-submit happens.

React gotcha

FormData and controlled inputs can desync

If you control inputs via useState (value={name} onChange={...}), the FormData object you build with new FormData(e.target) won't see your state — it reads the actual DOM. Either use uncontrolled inputs (no value prop) or build the body manually from state.

React gotcha

CSP errors when posting to a third-party endpoint

If your site has a strict Content Security Policy with connect-src 'self', fetch to splitforms.com will be blocked. Add splitforms.com to your connect-src directive: connect-src 'self' https://splitforms.com.

React gotcha

Strict mode + double-mount triggers two submissions in dev

React 18+ strict mode mounts components twice in development to surface side effects. If you put your fetch call in useEffect (don't), you'll see double-submits. Always trigger network calls in event handlers, not effects.

PATTERN A

Pattern A — uncontrolled inputs + native FormData

Skip useState per field. Inputs stay uncontrolled, new FormData(e.currentTarget) reads them at submit time, status state covers idle/loading/ok/err. ~25 lines, no form library. Use the same wiring for the waitlist fields on this page.

pattern-a.jsxjsx17 lines

01import { useState } from "react";
02export default function ContactForm() {
03  const [status, setStatus] = useState("idle");
04  return (
05    <form onSubmit={async (e) => {
06      e.preventDefault(); setStatus("loading");
07      const fd = new FormData(e.currentTarget);
08      fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
09      const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10      setStatus((await r.json()).success ? "ok" : "err");
11    }}>
12      <input name="email" type="email" required />
13      <textarea name="message" required />
14      <button disabled={status === "loading"}>Send</button>
15    </form>
16  );
17}

PATTERN B

Pattern B — React Hook Form for validation, splitforms for delivery

RHF handles client-side validation (zod schema, error messages); on valid submit, hand off to splitforms. RHF's handleSubmit callback receives parsed values — repackage as FormData and POST. Use the same wiring for the waitlist fields on this page.

pattern-b.jsxjsx8 lines

01import { useForm } from "react-hook-form";
02const { register, handleSubmit, formState } = useForm();
03const onSubmit = async (data) => {
04  const fd = new FormData();
05  Object.entries(data).forEach(([k, v]) => fd.append(k, v));
06  fd.append("access_key", import.meta.env.VITE_SPLITFORMS_KEY);
07  await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
08};

§ 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 React — FAQ.

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

01Does this waitlist work on React?

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

02How much does the waitlist cost on React?

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 React 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 React 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 React5 adjacent patterns

Ship a waitlist on React in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Waitlist for React

Why React developers choose splitforms for waitlist

Yes — this is the shortest safe path for React.

Paste the React / Next.js version, then replace YOUR_ACCESS_KEY.

Built for React developers who hate operating a backend.

Drop into any React project.

Generate, embed, receive.

Generate a free splitforms key

Paste the waitlist into your React 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 React.

useState + setStatus inside async causes race conditions

FormData and controlled inputs can desync

CSP errors when posting to a third-party endpoint

Strict mode + double-mount triggers two submissions in dev

Pattern A — uncontrolled inputs + native FormData

Pattern B — React Hook Form for validation, splitforms for delivery

What every field actually does.

Email

Name

How did you hear about us?

One backend. Every framework.

Waitlist on React — FAQ.

splitforms vs everything else.

Other ready-to-ship React forms.

Ship a waitlist on React in 60 seconds.