WAITLIST · TAILWIND CSS

Waitlist for Tailwind CSS

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 Tailwind CSS

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

§ 00Tailwind CSS + Waitlistplatform-specific integration guide

Why Tailwind CSS developers choose splitforms for waitlist

Tailwind CSS handles the styling side — utility classes for layout, spacing, colors, and responsive breakpoints. But styling a form is only half the job; you still need email delivery, spam filtering, webhook routing, and storage. The waitlist on this page combines Tailwind's utility-first CSS with splitforms' backend API: Tailwind makes it look right, splitforms makes it work. No form library needed — just standard HTML inputs with Tailwind classes, posting <code>FormData</code> to one endpoint. Works in Next.js, React, Vue, Astro, or any framework that supports Tailwind.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for Tailwind CSS.

Use the HTML snippet on this page, keep the waitlist fields visible in your Tailwind CSS 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 tailwind css reality

Tailwind is a styling layer — it has no opinion on form submission, networking, or backend.

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

Built for Tailwind CSS developers who hate operating a backend.

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

Splitforms is the form backend for Tailwind CSS 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 Tailwind CSS project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Tailwind CSS 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 Tailwind CSS project

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

§ 03cTailwind CSS production notesnative path · deploy · gotchas

What changes when this waitlist lives in Tailwind CSS.

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

without splitforms

Tailwind is a styling layer — it has no opinion on form submission, networking, or backend. The 'native' approach means writing utility classes for visual treatment and bringing your own delivery mechanism: a Next.js route handler, a Vite + React + fetch combo, an HTMX endpoint, etc. Tailwind UI ($299 one-time) sells styled form templates but doesn't include a backend either. Tailwind v4's @theme directive changes how tokens are defined, not what forms do. The shape of the problem stays: utility classes for look-and-feel, splitforms for delivery. Drop the snippet on this page into any framework with Tailwind configured and you have a styled, working form in 60 seconds.

deploy notes

Tailwind is purely a build-time concern — utilities are compiled into your CSS bundle, then deployed as static assets. JIT mode (default in v3+) and the v4 engine both purge unused classes; if you build form HTML inside a JS template literal at runtime, Tailwind can't see those classes and purges them — add to safelist or move markup into source files. Works on every host. For dark mode toggled via class, set darkMode: 'class' in v3 config or use @variant dark (.dark &) in v4 CSS. The @tailwindcss/forms plugin resets input styles aggressively — pick one (plugin OR explicit utilities), not both.

Tailwind CSS gotcha

JIT mode purges classes inside template strings

If you build the form HTML inside a JS template literal, Tailwind's JIT can't see your classes and purges them. Either move the markup into a .html / .tsx / .vue file, or add the classes to your safelist in tailwind.config.js.

Tailwind CSS gotcha

Tailwind 4's @theme replaces tailwind.config.js — focus colors break

Tailwind 4 (released 2026) moved theme tokens into CSS via @theme { … }. If you copy a Tailwind 3 snippet using focus:ring-orange-500, the orange-500 token has to be defined in your @theme block or it falls back to no ring color. Use a CSS variable: focus:ring-[var(--accent)] for portability.

Tailwind CSS gotcha

Form gets no styling at all — Preflight not loaded

If you're embedding the form inside a Shadow DOM, iframe, or a CMS that strips global CSS, Tailwind's Preflight (the global reset) doesn't apply. Inputs render with browser-default white backgrounds, ignoring bg-white if you set it in @apply but not as a utility on the element. Always use utilities directly on the input.

Tailwind CSS gotcha

Dark mode classes need `class` strategy explicitly set

Tailwind defaults to media-query dark mode (prefers-color-scheme). If your form has dark:bg-gray-900 and you toggle dark mode via a class on <html>, you need darkMode: 'class' in tailwind.config.js (Tailwind 3) or @variant dark (.dark &) in your CSS (Tailwind 4).

PATTERN A

Pattern A — utility-first inline styles

Every input gets utilities directly on the element — explicit, JIT-safe, no @apply indirection. Works in HTML, JSX, TSX, Vue, Svelte, Astro identically. Use the same wiring for the waitlist fields on this page.

pattern-a.htmlhtml12 lines

01<form action="https://splitforms.com/api/submit" method="POST"
02  class="max-w-md mx-auto space-y-4 p-6 bg-white rounded-2xl border border-gray-200">
03  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04  <input name="email" type="email" required
05    class="w-full rounded-lg border px-3 py-2 focus:ring-2 focus:ring-orange-500" />
06  <textarea name="message" rows="4" required
07    class="w-full rounded-lg border px-3 py-2 focus:ring-2 focus:ring-orange-500" />
08  <button type="submit"
09    class="w-full bg-orange-600 hover:bg-orange-700 text-white font-semibold py-2 rounded-lg">
10    Send
11  </button>
12</form>

PATTERN B

Pattern B — dark-mode + accessible focus states (Tailwind v4)

Pairs dark: variants with focus-visible: for keyboard-only focus rings. Uses CSS variables for accent color so the same component works in light/dark without rewriting utilities. Use the same wiring for the waitlist fields on this page.

pattern-b.htmlhtml9 lines

01<form action="https://splitforms.com/api/submit" method="POST"
02  class="max-w-md mx-auto p-6 rounded-2xl border bg-white dark:bg-zinc-900 dark:border-zinc-800">
03  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04  <input name="email" type="email" required
05    class="w-full rounded-lg border bg-white dark:bg-zinc-950 px-3 py-2
06           text-gray-900 dark:text-zinc-100
07           focus-visible:ring-2 focus-visible:ring-[var(--accent)]" />
08  <button class="w-full bg-[var(--accent)] text-white py-2 rounded-lg">Send</button>
09</form>

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

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

01Does this waitlist work on Tailwind CSS?

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

02How much does the waitlist cost on Tailwind CSS?

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 Tailwind CSS 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 Tailwind CSS 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 Tailwind CSS5 adjacent patterns

Ship a waitlist on Tailwind CSS in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Waitlist for Tailwind CSS

Why Tailwind CSS developers choose splitforms for waitlist

Yes — this is the shortest safe path for Tailwind CSS.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Tailwind CSS developers who hate operating a backend.

Drop into any Tailwind CSS project.

Generate, embed, receive.

Generate a free splitforms key

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

JIT mode purges classes inside template strings

Tailwind 4's @theme replaces tailwind.config.js — focus colors break

Form gets no styling at all — Preflight not loaded

Dark mode classes need `class` strategy explicitly set

Pattern A — utility-first inline styles

Pattern B — dark-mode + accessible focus states (Tailwind v4)

What every field actually does.

Email

Name

How did you hear about us?

One backend. Every framework.

Waitlist on Tailwind CSS — FAQ.

splitforms vs everything else.

Other ready-to-ship Tailwind CSS forms.

Ship a waitlist on Tailwind CSS in 60 seconds.