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.
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.
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.
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.
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.
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.
- ✓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)
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.
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.
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.
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.
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.
The reason this lead magnet download exists.
Multi-step (Typeform-style) · webhooks into ConvertKit / HubSpot / Mailchimp.
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.
Step 1: capture email
Single email field — frictionless step 1. Once the email is in, momentum carries through later qualifying questions.
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.
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.
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, 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.
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.
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.
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.
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.
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 — 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 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.
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.
First name
Greeting + dashboard label so submissions don't all read 'anonymous'.
Work email
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
Company
Lets you sort enterprise vs SMB inquiries before you reply.
What's your role?
Buyer-persona signal — IC vs decision-maker changes the follow-up cadence.
One backend. Every framework.
The same lead magnet download template works on every framework splitforms supports. Pick yours.
Lead Magnet Download on Next.js — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, real webhooks on the free tier, MCP support no other backend has.
Other ready-to-ship Next.js forms.
Same backend, different qualifying fields. Click through to copy the snippet.
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.