FEEDBACK FORM · NEXT.JS

Feedback Form for Next.js

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 Next.js

Form.tsxtsx52 lines

01'use client';
02 
03import { useState, type FormEvent } from 'react';
04 
05export default function FeedbackForm() {
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 feedback submission');
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="rating">How would you rate your experience? *</label>
32      <select id="rating" name="rating" required>
33        <option value="">Choose…</option>
34        <option>★★★★★</option>
35        <option>★★★★☆</option>
36        <option>★★★☆☆</option>
37        <option>★★☆☆☆</option>
38        <option>★☆☆☆☆</option>
39      </select>
40      <label htmlFor="feedback">What can we do better? *</label>
41      <textarea id="feedback" name="feedback" placeholder="Be honest — we won't take it personally." required />
42      <label htmlFor="email">Email (optional, for follow-up)</label>
43      <input id="email" type="email" name="email" placeholder="you@example.com" />
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

§ 00Next.js + Feedback Formplatform-specific integration guide

Why Next.js developers choose splitforms for feedback form

Next.js Server Actions handle the submit side but still leave you wiring SMTP, spam filtering, file uploads, and a dashboard. splitforms replaces all of that with one <code>fetch('/api/submit')</code> call. The feedback form works identically in App Router and Pages Router — it's just a <code>FormData</code> POST, no router-specific magic. Because Next.js pre-renders pages, the form HTML is in the DOM before any JavaScript executes, meaning instant Time-to-Interactive. The honeypot field is invisible to users but catches bots that scrape rendered HTML — especially important for Next.js sites where the form HTML is statically generated and predictable.

§ 00Quick answerReact / Next.js · feedback

Yes — this is the shortest safe path for Next.js.

Use the React / Next.js snippet on this page, keep the feedback form fields visible in your Next.js 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 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 next.js 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 × Next.jswhy this combination, in 80 words

Built for Next.js developers who hate operating a backend.

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

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

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Next.js 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 FeedbackForm() {
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 feedback submission');
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="rating">How would you rate your experience? *</label>
32      <select id="rating" name="rating" required>
33        <option value="">Choose…</option>
34        <option>★★★★★</option>
35        <option>★★★★☆</option>
36        <option>★★★☆☆</option>
37        <option>★★☆☆☆</option>
38        <option>★☆☆☆☆</option>
39      </select>
40      <label htmlFor="feedback">What can we do better? *</label>
41      <textarea id="feedback" name="feedback" placeholder="Be honest — we won't take it personally." required />
42      <label htmlFor="email">Email (optional, for follow-up)</label>
43      <input id="email" type="email" name="email" placeholder="you@example.com" />
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 feedback form 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 feedback submission">

  <label for="rating">How would you rate your experience? *</label>
  <select id="rating" name="rating" required>
    <option value="">Choose…</option>
    <option>★★★★★</option>
    <option>★★★★☆</option>
    <option>★★★☆☆</option>
    <option>★★☆☆☆</option>
    <option>★☆☆☆☆</option>
  </select>
  <label for="feedback">What can we do better? *</label>
  <textarea id="feedback" name="feedback" placeholder="Be honest — we won't take it personally." required></textarea>
  <label for="email">Email (optional, for follow-up)</label>
  <input id="email" type="email" name="email" placeholder="you@example.com">

  <!-- 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 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 Next.js project

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

§ 03cNext.js production notesnative path · deploy · gotchas

What changes when this feedback form lives in Next.js.

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

without splitforms

Without splitforms, you'd write a route handler at app/api/contact/route.ts, parse the FormData, configure SMTP via nodemailer or Resend (~10 minutes of secrets wrangling), add a Postgres or SQLite store for submissions, and then bolt on rate limiting, a honeypot check, an email-classifier or reCAPTCHA, and webhook fan-out. Server actions made the wiring slightly tidier in Next 14+, but the operational cost stays the same: a function with a runtime, a database, an outbound email provider, an inbox to monitor, and your name on the spam-filter incident report. Splitforms collapses all of that into a POST to a single URL.

deploy notes

On Vercel, the form works on every plan tier — server actions and client components both run inside the same edge/serverless function. Don't put the splitforms fetch inside a Vercel cron or background function (it's user-facing, latency matters). On Netlify with the Next runtime, server actions need the latest @netlify/plugin-nextjs (≥5.6). For self-hosted / Docker: configure output: 'standalone' in next.config.ts and pass SPLITFORMS_KEY as a runtime env var — never bake it into the image. For static export (output: 'export'), use the client-component path only — server actions aren't supported in static mode.

Next.js gotcha

Don't expose your access key client-side without domain locking

Inlining access_key in a "use client" component makes the key visible to anyone who views source. That's fine if you've enabled allowed-domains in your Splitforms dashboard (Settings → Security) — anyone copying the key from your bundle can't use it from a different origin. If you haven't, use a server action so the key stays on the server.

Next.js gotcha

Server actions need `'use server'` and a real form, not fetch

If you submit to a server action via <form action={myAction}>, Next handles the FormData serialization for you. If you call the action manually with fetch, you have to set the right Content-Type and stringify yourself. Pick one path and stick with it — mixing causes 'Server Action invalid' errors.

Next.js gotcha

App Router + Suspense + useSearchParams = static-prerender bailout

If your form reads ?next=/something to support post-submit redirects, useSearchParams forces the page out of static generation. Either wrap the inner component in a <Suspense fallback={<Skeleton/>}> so the wrapper still prerenders, or accept dynamic rendering for the form route only.

Next.js gotcha

Vercel Edge runtime can't read FormData from `multipart/form-data`

If your route handler uses export const runtime = 'edge' and the form posts as multipart (file inputs), it'll silently miss fields. Use application/x-www-form-urlencoded or remove the edge runtime declaration.

PATTERN A

Pattern A — server action (no client JS, key stays server-side)

Form posts to a server action; the action appends the access key from process.env.SPLITFORMS_KEY and proxies to splitforms. Works without JavaScript, key never reaches the bundle. Use the same wiring for the feedback form fields on this page.

pattern-a.tsxtsx10 lines

01// app/actions/contact.ts
02"use server";
03import { redirect } from "next/navigation";
04 
05export async function submitContact(formData: FormData) {
06  formData.append("access_key", process.env.SPLITFORMS_KEY!);
07  const res = await fetch("https://splitforms.com/api/submit", { method: "POST", body: formData });
08  if (!(await res.json()).success) throw new Error("Submission failed");
09  redirect("/thanks");
10}

PATTERN B

Pattern B — client component with fetch and inline status

'use client' component using useState for a 4-state status machine. Lets you show a spinner, inline errors, optimistic resets — at the cost of a hydration boundary. Use NEXT_PUBLIC_SPLITFORMS_KEY and rely on splitforms' domain-locking for safety. Use the same wiring for the feedback form fields on this page.

pattern-b.tsxtsx17 lines

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

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

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

01Does this feedback form work on Next.js?

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

02How much does the feedback form cost on Next.js?

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 Next.js 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 Next.js 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 Next.js5 adjacent patterns

Ship a feedback form on Next.js in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Feedback Form for Next.js

Why Next.js developers choose splitforms for feedback form

Yes — this is the shortest safe path for Next.js.

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

Built for Next.js developers who hate operating a backend.

Drop into any Next.js project.

Generate, embed, receive.

Generate a free splitforms key

Paste the feedback form into your Next.js 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 Next.js.

Don't expose your access key client-side without domain locking

Server actions need `'use server'` and a real form, not fetch

App Router + Suspense + useSearchParams = static-prerender bailout

Vercel Edge runtime can't read FormData from `multipart/form-data`

Pattern A — server action (no client JS, key stays server-side)

Pattern B — client component with fetch and inline status

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 Next.js — FAQ.

splitforms vs everything else.

Other ready-to-ship Next.js forms.

Ship a feedback form on Next.js in 60 seconds.