FEEDBACK FORM · SVELTEKIT

Feedback Form for SvelteKit

Rating + free-text feedback with optional follow-up email. 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.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 feedback submission">
04 
05  <label for="rating">How would you rate your experience? *</label>
06  <select id="rating" name="rating" required>
07    <option value="">Choose…</option>
08    <option>★★★★★</option>
09    <option>★★★★☆</option>
10    <option>★★★☆☆</option>
11    <option>★★☆☆☆</option>
12    <option>★☆☆☆☆</option>
13  </select>
14  <label for="feedback">What can we do better? *</label>
15  <textarea id="feedback" name="feedback" placeholder="Be honest — we won't take it personally." required></textarea>
16  <label for="email">Email (optional, for follow-up)</label>
17  <input id="email" type="email" name="email" placeholder="you@example.com">
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

§ 00SvelteKit + Feedback Formplatform-specific integration guide

Why SvelteKit developers choose splitforms for feedback form

Svelte's lightweight runtime is one of its biggest selling points — adding a heavy form library defeats the purpose. The feedback form 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 · feedback

Yes — this is the shortest safe path for SvelteKit.

Use the HTML snippet on this page, keep the feedback form 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 how would you rate your experience?, what can we do better?, email (optional, for follow-up). Required fields are how would you rate your experience? and what can we do better?.

native sveltekit reality

use case fit

Customer feedback is the cheapest product research you have. The form captures NPS / CSAT plus an open comment — and routes negative responses to a Slack channel for same-day triage.

§ 01Feedback Form × 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 feedback form 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 · 23 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.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 feedback submission">
04 
05  <label for="rating">How would you rate your experience? *</label>
06  <select id="rating" name="rating" required>
07    <option value="">Choose…</option>
08    <option>★★★★★</option>
09    <option>★★★★☆</option>
10    <option>★★★☆☆</option>
11    <option>★★☆☆☆</option>
12    <option>★☆☆☆☆</option>
13  </select>
14  <label for="feedback">What can we do better? *</label>
15  <textarea id="feedback" name="feedback" placeholder="Be honest — we won't take it personally." required></textarea>
16  <label for="email">Email (optional, for follow-up)</label>
17  <input id="email" type="email" name="email" placeholder="you@example.com">
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 feedback form 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 feedback form 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 feedback submission

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?

§ 03bCustomer Feedback Form (NPS / CSAT / Open-Ended)template-specific playbook

The reason this feedback form exists.

Webhooks into Slack / Linear / Productboard · NPS detractor triage in minutes.

why it matters

Feedback forms cost almost nothing to ship and pay back disproportionately — every NPS detractor (score 0-6) is a conversation that prevents churn, every promoter (9-10) is a referral or testimonial source. The form is simple: 0-10 rating, an optional comment, and an email. The leverage is in the routing: detractors auto-DM your support lead in Slack within minutes, promoters get a 'mind leaving us a G2 / Trustpilot review?' follow-up, passives go into a digest. Survey tools (SurveyMonkey, Typeform, Hotjar) charge $30-100/mo for the same pattern. The form pattern is 30 lines of HTML.

route the submission

Capture rating + comment

Required: 0-10 NPS rating (or 1-5 CSAT for transactional surveys). Optional: comment textarea, email for follow-up. Keep it minimal — long surveys tank completion.

Route by score

Webhook branches on score: 0-6 (detractors) DM Slack support channel; 7-8 (passives) go to weekly digest; 9-10 (promoters) trigger a G2 / Trustpilot review-request email.

Push to your tools

Detractor comments to Linear / Productboard for product triage. Promoter quotes to a 'testimonials' Notion database for marketing. Raw data to a CSV / BigQuery / dbt warehouse for trend analysis.

§ 03cSvelteKit production notesnative path · deploy · gotchas

What changes when this feedback form 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 feedback form 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 feedback form 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 rundown3 fields · names you POST

What every field actually does.

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

ratingREQUIRED

SELECT

How would you rate your experience?

NPS / CSAT signal — quantitative complement to the comment field.

★★★★★★★★★☆★★★☆☆★★☆☆☆★☆☆☆☆

feedbackREQUIRED

TEXTAREA

What can we do better?

Free-text input — no character limit, expands as the visitor types.

placeholder · Be honest — we won't take it personally.

Email (optional, for follow-up)

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

placeholder · you@example.com

§ 05Feedback Form on other frameworks21 frameworks · same backend

One backend. Every framework.

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

§ 06Questions9 answered

Feedback Form on SvelteKit — FAQ.

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

01Does this feedback form 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 feedback form 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 (how would you rate your experience?, what can we do better?, email (optional, for follow-up)…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the feedback form?

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 feedback form 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.

07Should I use NPS or CSAT?

NPS (0-10) for relationship surveys ('how likely are you to recommend us?') sent quarterly or after major moments. CSAT (1-5) for transactional surveys ('how was this support ticket?') sent right after the interaction. Different questions, different cadences, both common patterns.

08Will I get response bias from a public form?

Yes — open-link feedback skews toward people with strong feelings (positive or negative). For statistically representative measurement, send the survey via email to a random sample of users. The public form catches the heat-of-moment feedback you'd otherwise miss.

09Can I push to Slack / Linear / Productboard?

Yes — webhook the JSON. Slack has incoming webhooks (free); Linear and Productboard accept inbound issue creation via Zapier or native APIs. Detractor comments showing up as a Linear issue with the rating prefilled in the title is a powerful workflow.

§ 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 feedback form 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

Feedback Form for SvelteKit

Why SvelteKit developers choose splitforms for feedback form

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 feedback form into your SvelteKit project

Receive submissions

The reason this feedback form exists.

Capture rating + comment

Route by score

Push to your tools

What changes when this feedback form 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.

How would you rate your experience?

What can we do better?

Email (optional, for follow-up)

One backend. Every framework.

Feedback Form on SvelteKit — FAQ.

splitforms vs everything else.

Other ready-to-ship SvelteKit forms.

Ship a feedback form on SvelteKit in 60 seconds.