splitforms.com
LEAD MAGNET DOWNLOAD · NEXT.JS

Lead Magnet Download for Next.js

Email-gated download form for ebooks, PDFs, checklists, and templates. Free for 1,000 submissions per month — no backend, no SDK, no plugin.

1,000/mo free·no card·drop-in for Next.js
Form.tsxtsx55 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function LeadMagnetForm() {
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 lead magnet download');
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="name">First name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane" required />
33 <label htmlFor="email">Work email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@company.com" required />
35 <label htmlFor="company">Company</label>
36 <input id="company" type="text" name="company" placeholder="Acme Inc" />
37 <label htmlFor="role">What's your role?</label>
38 <select id="role" name="role">
39 <option value="">Choose…</option>
40 <option>Founder / CEO</option>
41 <option>Engineer</option>
42 <option>Designer</option>
43 <option>Marketer</option>
44 <option>Product manager</option>
45 <option>Other</option>
46 </select>
47
48 <button type="submit" disabled={status === 'sending'}>
49 {status === 'sending' ? 'Sending…' : 'Send'}
50 </button>
51
52 {status === 'error' && <p>Something went wrong. Try again.</p>}
53 </form>
54 );
55}
1,000
submissions / mo, free
4
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Quick answerReact / Next.js · marketing

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

Use the React / Next.js snippet on this page, keep the lead magnet download 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 first name, work email, company, what's your role?. Required fields are first name and work email.

native next.js reality

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.

use case fit

Ungated content gets read; gated content builds your list. The lead-magnet form trades the PDF for an email plus 1-2 qualifying questions, so the nurture sequence segments by intent.

§ 01Lead Magnet Download × Next.jswhy this combination, in 80 words

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

Splitforms is the form-to-email API for Next.js sites. One POST endpoint, no SDK, no plugin — drop the lead magnet download into a page and ship.

Splitforms is the form-to-email API for Next.js sites. One POST endpoint, spam filtering, signed webhooks, file uploads, a real dashboard — drop-in, no server, no PHP. Free for 1,000 submissions per month, $5/mo Pro for 5,000, $59 for 4 years if you hate recurring SaaS bills.

✦ what you get on the free plan
  • 1,000 form submissions per month
  • Unlimited forms — one key, many pages
  • 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 · 55 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.tsxtsx55 lines
01'use client';
02
03import { useState, type FormEvent } from 'react';
04
05export default function LeadMagnetForm() {
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 lead magnet download');
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="name">First name *</label>
32 <input id="name" type="text" name="name" placeholder="Jane" required />
33 <label htmlFor="email">Work email *</label>
34 <input id="email" type="email" name="email" placeholder="jane@company.com" required />
35 <label htmlFor="company">Company</label>
36 <input id="company" type="text" name="company" placeholder="Acme Inc" />
37 <label htmlFor="role">What's your role?</label>
38 <select id="role" name="role">
39 <option value="">Choose…</option>
40 <option>Founder / CEO</option>
41 <option>Engineer</option>
42 <option>Designer</option>
43 <option>Marketer</option>
44 <option>Product manager</option>
45 <option>Other</option>
46 </select>
47
48 <button type="submit" disabled={status === 'sending'}>
49 {status === 'sending' ? 'Sending…' : 'Send'}
50 </button>
51
52 {status === 'error' && <p>Something went wrong. Try again.</p>}
53 </form>
54 );
55}
ALTPrefer plain HTML? View the universal lead magnet download HTML snippet26 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 lead magnet download">

  <label for="name">First name *</label>
  <input id="name" type="text" name="name" placeholder="Jane" required>
  <label for="email">Work email *</label>
  <input id="email" type="email" name="email" placeholder="jane@company.com" required>
  <label for="company">Company</label>
  <input id="company" type="text" name="company" placeholder="Acme Inc">
  <label for="role">What's your role?</label>
  <select id="role" name="role">
    <option value="">Choose…</option>
    <option>Founder / CEO</option>
    <option>Engineer</option>
    <option>Designer</option>
    <option>Marketer</option>
    <option>Product manager</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 lead magnet download submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Sign in at splitforms.com — your access key is created instantly. No credit card, no setup wizard, no SDK to install.

Create your form
key=sk_live_••••••••
STEP 02EMBED

Paste the lead magnet download 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

Email arrives within seconds. Webhook fires in parallel. Dashboard updates live. CSV export, Slack/Discord forwarding, BCC to your team — all included free.

inbox · 1 newjust now
FROM contact@yoursite.com
New lead magnet download
Maya Iyer maya@studio71.co
Loved the demo — quick question about pricing on the 4-year plan. Are usage limits per project or account-wide?
§ 03bLead Magnet Download Form (Ebook / PDF / Checklist Gate)template-specific playbook

The reason this lead magnet download exists.

Multi-step (Typeform-style) · webhooks into ConvertKit / HubSpot / Mailchimp.

why it matters

Lead magnets — ebooks, checklists, templates, swipe files, mini-courses — are the workhorse of B2B content marketing. Gated downloads convert at 25-50% of landing-page visitors (vs 1-2% for newsletter signups), but only when the magnet is truly valuable. The form captures email plus 1-2 qualifying questions ('what's your role?', 'what's your team size?') so the nurture sequence segments by intent. Multi-step boosts completion vs a single form. After submit, the user is redirected to the PDF or it's emailed via webhook + auto-responder. Push the email to your ESP segmented by lead-magnet topic — that's how content marketers build audience taxonomies that actually convert downstream.

route the submission
01

Step 1: capture email

Single email field — frictionless step 1. Once the email is in, momentum carries through later qualifying questions.

02

Step 2-3: qualify role / team

One or two questions on role and team size. Optional but most users complete because they're invested. Each answer becomes a tag in the ESP for downstream segmentation.

03

Deliver the magnet

Auto-respond with the PDF link (or redirect to a thank-you page that auto-downloads). Webhook to ConvertKit / HubSpot / Mailchimp into a 'lead-magnet:[topic]' audience for the nurture sequence.

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

What changes when this lead magnet download 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 lead magnet download 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 lead magnet download 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 rundown4 fields · names you POST

What every field actually does.

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

nameREQUIRED
TEXT

First name

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

placeholder · Jane
emailREQUIRED
EMAIL

Work email

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

placeholder · jane@company.com
company
TEXT

Company

Lets you sort enterprise vs SMB inquiries before you reply.

placeholder · Acme Inc
role
SELECT

What's your role?

Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.

Founder / CEOEngineerDesignerMarketerProduct managerOther
§ 05Lead Magnet Download on other frameworks4 frameworks · same backend

One backend. Every framework.

The same lead magnet download template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Lead Magnet Download on Next.jsFAQ.

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

01Does this lead magnet download 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 inbox via splitforms.com.
02How much does the lead magnet download cost on Next.js?
Free for 1,000 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 4-year plan (15,000 submissions/mo for 48 months). The same pricing applies regardless of which framework hosts the form.
03Can I customize the fields?
Yes. The template ships with sensible defaults (first name, work email, company, what's your role?…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the lead magnet download?
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 lead magnet download submissions to Slack or Discord?
Yes. Webhooks are free on every plan, 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 redirect to the PDF or email it?
Email it. Redirects to a Drive / S3 link mean the user gets the PDF without confirming the email — and the email might be a typo or a temporary address. Email delivery confirms the address by requiring an open. Add a 'didn't get it?' resend button on the thank-you page for the rare typo case.
08Can I integrate with ConvertKit / HubSpot / Mailchimp?
Yes — webhook the JSON into the ESP. ConvertKit's 'tags' map naturally to lead-magnet topics; HubSpot's 'lists' do the same. The nurture sequence triggers on tag-add and the topic-specific drip starts immediately. Most B2B teams use this exact pattern.
09Is gating content GDPR-safe?
If you have EU visitors, the consent for marketing email needs to be explicit and unbundled — meaning a separate checkbox 'I want to receive emails about [topic]' that's not pre-checked and not bundled with 'I accept the download'. Bundled consent has been challenged in EU rulings; unbundled is the safe play.
§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, real webhooks on the free tier, MCP support no other backend has.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions250501,000
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (4-year flat)$59 once
✻ ✻ ✻

Ship a lead magnet download on Next.js in 60 seconds.

1,000 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
v0.1 · founders pricing locked in · early access open