EVENT RSVP · SVELTEKIT

Event RSVP for SvelteKit

Attendance confirmation with headcount and dietary needs. 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 SvelteKit

form.htmlhtml25 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 event RSVP">
04 
05  <label for="name">Your name *</label>
06  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07  <label for="email">Email *</label>
08  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
09  <label for="attending">Will you attend? *</label>
10  <select id="attending" name="attending" required>
11    <option value="">Choose…</option>
12    <option>Yes — count me in</option>
13    <option>Maybe</option>
14    <option>No, I can't make it</option>
15  </select>
16  <label for="guests">How many guests are you bringing?</label>
17  <input id="guests" type="number" name="guests" placeholder="0">
18  <label for="dietary">Dietary preferences</label>
19  <input id="dietary" type="text" name="dietary" placeholder="Vegan, gluten-free, allergies…">
20 
21  <!-- honeypot — bots fill every field -->
22  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
23 
24  <button type="submit">Send</button>
25</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00SvelteKit + Event RSVPplatform-specific integration guide

Why SvelteKit developers choose splitforms for event rsvp

Svelte's lightweight runtime is one of its biggest selling points — adding a heavy form library defeats the purpose. The event rsvp on this page keeps that promise: it uses Svelte's native <code>on:submit</code> directive and a <code>fetch</code> POST, with no external dependencies. The form state lives in a simple <code>let</code> variable, not a store or a state machine. In SvelteKit, you could alternatively use a <code>+page.server.ts</code> action, but that couples your form to SvelteKit's server-side runtime — splitforms decouples it so the same form works on static hosts and other frameworks.

§ 00Quick answerHTML · events

Yes — this is the shortest safe path for SvelteKit.

Use the HTML snippet on this page, keep the event rsvp fields visible in your SvelteKit 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 your name, email, will you attend?, how many guests are you bringing?, dietary preferences. Required fields are your name, email and will you attend?.

native sveltekit reality

use case fit

Eventbrite charges 3.7% + $1.79 per ticket. For a free event, fundraiser, or private gathering, the RSVP form does the same job for $0 — and lives on your own domain.

§ 01Event RSVP × SvelteKitwhy this combination, in 80 words

Built for SvelteKit developers who hate operating a backend.

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

Splitforms is the form backend for SvelteKit 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 · 25 lines

Drop into any SvelteKit project.

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

form.htmlhtml25 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 event RSVP">
04 
05  <label for="name">Your name *</label>
06  <input id="name" type="text" name="name" placeholder="Jane Builder" required>
07  <label for="email">Email *</label>
08  <input id="email" type="email" name="email" placeholder="jane@example.com" required>
09  <label for="attending">Will you attend? *</label>
10  <select id="attending" name="attending" required>
11    <option value="">Choose…</option>
12    <option>Yes — count me in</option>
13    <option>Maybe</option>
14    <option>No, I can't make it</option>
15  </select>
16  <label for="guests">How many guests are you bringing?</label>
17  <input id="guests" type="number" name="guests" placeholder="0">
18  <label for="dietary">Dietary preferences</label>
19  <input id="dietary" type="text" name="dietary" placeholder="Vegan, gluten-free, allergies…">
20 
21  <!-- honeypot — bots fill every field -->
22  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
23 
24  <button type="submit">Send</button>
25</form>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first event rsvp 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 event rsvp into your SvelteKit project

Drop the form snippet into a SvelteKit 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 event RSVP

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?

§ 03bEvent RSVP Form (Public / Private Events)template-specific playbook

The reason this event rsvp exists.

Webhooks into Notion / Airtable / Google Sheets · auto .ics calendar invite.

why it matters

Eventbrite, Splash, and Hopin take 3-7% of every paid ticket and charge subscription fees for the white-label option. For free events (fundraisers, private parties, conferences with sponsor-only revenue, weddings), the platform fees are pure waste. The RSVP form captures attending yes/no, guest count, plus-one names, dietary restrictions, and any custom fields (workshop preference for conferences, song requests for weddings). Webhook to a Notion / Airtable / Google Sheet for the running headcount, plus an automatic confirmation email. Final headcount goes to catering 5-7 days out, same as any platform would deliver.

route the submission

Capture attendance and party

Required: attending yes/no, guest count, plus-one names if applicable. Optional: dietary restrictions, song requests, workshop preference, accessibility needs.

Update the running list

Webhook to a Notion / Airtable / Google Sheet that the host references. Each RSVP appends a row; conditional formatting highlights special diets. Real-time headcount without spreadsheet work.

Confirm via email

Auto-respond with confirmation, event details, and a calendar invite (.ics file). Most guests forget the date once they've RSVP'd — calendar adds reduce no-shows by 30-40%.

§ 03cSvelteKit production notesnative path · deploy · gotchas

What changes when this event rsvp lives in SvelteKit.

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

without splitforms

SvelteKit's headline form story is form actions — write a default-exported actions object in +page.server.ts, and SvelteKit handles FormData parsing, progressive enhancement (use:enhance), and result passing via the form prop. It's elegant DX — but it doesn't deliver email. You still write the SMTP integration, the spam-filter logic, the database for storing submissions, the webhook fan-out. The result is a form action that's ~80% boilerplate and ~20% your business logic. Splitforms collapses the boilerplate: the form posts directly from the browser to splitforms.com, the form action becomes a thin proxy (or you skip it entirely), and the operational layer disappears.

deploy notes

SvelteKit's adapter system is the deployment story: @sveltejs/adapter-vercel, -netlify, -cloudflare, -cloudflare-workers, -node, -static. The form's POST is cross-origin to splitforms regardless of adapter. On Cloudflare Pages/Workers (free tier: 10ms CPU per request), avoid Pattern B — the form action's fetch round-trip eats your budget; use Pattern A. On Vercel/Netlify, both patterns work with no measurable difference. $env/static/public inlines at build time (use for client-exposed keys); $env/static/private is server-only (use for Pattern B's server-action key). Domain-lock the access key.

SvelteKit gotcha

Form actions need POST and the named action prefix

If you use +page.server.ts form actions, the form's action attribute must be ?/contact (or whatever you named it) — not /api/contact. Forgetting the ?/ prefix routes to a 404 because SvelteKit doesn't recognize it as an action.

SvelteKit gotcha

use:enhance disables your client-side handler if you don't return a callback

use:enhance without arguments uses default progressive-enhancement behavior — which calls the form action and re-renders. If you need custom logic (toast on error, etc.), return a function: use:enhance={({ formData, cancel }) => async ({ result }) => …}.

SvelteKit gotcha

Cloudflare adapter has a 50ms cold start budget — fetch to splitforms eats it

If you use a SvelteKit form action that proxies to splitforms.com via fetch, the round-trip eats your CF Worker time budget on cold start. Skip the proxy: have the form POST directly to splitforms.com from the client (the snippet above does this).

SvelteKit gotcha

$env/static/public vs $env/dynamic/public — pick the right one

$env/static/public is inlined at build time (faster, but key is in the bundle). $env/dynamic/public is read at runtime (slower, but rotatable without rebuild). For the splitforms key, static is fine if you've locked the key to your domain.

PATTERN A

Pattern A — client-side fetch (skip form actions)

Pure +page.svelte with a fetch handler — no +page.server.ts needed. Simpler, works on every adapter without server CPU time, no proxying. Best for Cloudflare Workers / Pages where CPU budget matters. Use the same wiring for the event rsvp fields on this page.

pattern-a.txtsvelte14 lines

01<script>
02  let status = "idle";
03  async function onSubmit(e) {
04    status = "loading";
05    const fd = new FormData(e.currentTarget);
06    fd.append("access_key", import.meta.env.VITE_PUBLIC_SPLITFORMS_KEY);
07    const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
08    status = (await r.json()).success ? "ok" : "err";
09  }
10</script>
11<form on:submit|preventDefault={onSubmit}>
12  <input name="email" type="email" required />
13  <button disabled={status === "loading"}>Send</button>
14</form>

PATTERN B

Pattern B — form action with use:enhance (no-JS support)

Server-side form action proxies to splitforms; key stays in $env/static/private. With use:enhance, the form posts traditionally without JS (full-page reload, splitforms 302 to /thanks) and AJAXes when JS loads. Maximum compatibility, slight CPU cost on the server. Use the same wiring for the event rsvp fields on this page.

pattern-b.txtsvelte12 lines

01// +page.server.ts
02import { fail, redirect } from "@sveltejs/kit";
03import { SPLITFORMS_KEY } from "$env/static/private";
04export const actions = {
05  default: async ({ request }) => {
06    const fd = await request.formData();
07    fd.append("access_key", SPLITFORMS_KEY);
08    const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
09    if (!(await r.json()).success) return fail(400, { message: "Failed" });
10    throw redirect(303, "/thanks");
11  },
12};

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

What every field actually does.

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

nameREQUIRED

TEXT

Your name

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

placeholder · Jane Builder

emailREQUIRED

Email

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

placeholder · jane@example.com

attendingREQUIRED

SELECT

Will you attend?

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

Yes — count me inMaybeNo, I can't make it

guests

NUMBER

How many guests are you bringing?

Standard input — splitforms accepts whatever you POST under this name.

placeholder · 0

dietary

TEXT

Dietary preferences

Logistics input you'd otherwise gather over email anyway.

placeholder · Vegan, gluten-free, allergies…

§ 05Event RSVP on other frameworks21 frameworks · same backend

One backend. Every framework.

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

§ 06Questions9 answered

Event RSVP on SvelteKit — FAQ.

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

01Does this event rsvp work on SvelteKit?

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

02How much does the event rsvp cost on SvelteKit?

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 (your name, email, will you attend?, how many guests are you bringing?…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the event rsvp?

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 SvelteKit as on any other framework.

05Can I send the event rsvp 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 SvelteKit 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.

07Why not just use Eventbrite or Splash?

For free events, both charge subscription fees ($30-100/mo for white-label) plus per-ticket fees. The form costs $0, lives on your own domain (which matters for weddings and brand events), and the data is yours — not licensed inside their platform.

08Can I send a calendar invite (.ics) automatically?

Yes — generate an .ics file and attach to the auto-responder. Webhook to a Zapier / Make automation that crafts the .ics with event title, date, location, and notes. Most email clients render the attachment as 'add to calendar' inline.

09How do I handle plus-ones?

Add 'plus-one yes/no' and a name field that appears conditionally. For weddings, the 'plus-one allowed' is invitation-specific — capture invitation code on the form, and the webhook validates whether that invite includes a plus-one before accepting the second name.

§ 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 SvelteKit5 adjacent patterns

Ship a event rsvp on SvelteKit in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Event RSVP for SvelteKit

Why SvelteKit developers choose splitforms for event rsvp

Yes — this is the shortest safe path for SvelteKit.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for SvelteKit developers who hate operating a backend.

Drop into any SvelteKit project.

Generate, embed, receive.

Generate a free splitforms key

Paste the event rsvp into your SvelteKit project

Receive submissions

The reason this event rsvp exists.

Capture attendance and party

Update the running list

Confirm via email

What changes when this event rsvp lives in SvelteKit.

Form actions need POST and the named action prefix

use:enhance disables your client-side handler if you don't return a callback

Cloudflare adapter has a 50ms cold start budget — fetch to splitforms eats it

$env/static/public vs $env/dynamic/public — pick the right one

Pattern A — client-side fetch (skip form actions)

Pattern B — form action with use:enhance (no-JS support)

What every field actually does.

Your name

Email

Will you attend?

How many guests are you bringing?

Dietary preferences

One backend. Every framework.

Event RSVP on SvelteKit — FAQ.

splitforms vs everything else.

Other ready-to-ship SvelteKit forms.

Ship a event rsvp on SvelteKit in 60 seconds.