splitforms.com
NEWSLETTER SIGNUP · NUXT

Newsletter Signup for Nuxt

Email-only newsletter capture — perfect for footers and landing pages. Free for 500 submissions per month — no backend, no SDK, no plugin.

500/mo free·no card·drop-in for Nuxt
form.htmlhtml12 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 newsletter subscriber">
04
05 <label for="email">Your email *</label>
06 <input id="email" type="email" name="email" placeholder="you@example.com" required>
07
08 <!-- honeypot — bots fill every field -->
09 <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
10
11 <button type="submit">Send</button>
12</form>
500
submissions / mo, free
1
fields, ready to ship
5
code outputs
60s
from copy to inbox
§ 00Nuxt + Newsletter Signupplatform-specific integration guide

Why Nuxt developers choose splitforms for newsletter signup

Nuxt 3's auto-imports and server routes make it easy to add form handling, but setting up a server-side submission pipeline (SMTP, spam checks, database, dashboard) is still a significant project. The newsletter signup on this page uses <code>useState</code> for submit state and a <code>fetch</code> POST to splitforms — no server route, no Nitro engine dependency, no SMTP configuration. Because the form posts directly from the browser, it works identically on static hosting (Netlify, Cloudflare Pages) and on Nuxt's server-rendered pages.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for Nuxt.

Use the HTML snippet on this page, keep the newsletter signup fields visible in your Nuxt 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 email. Required fields are your email.

native nuxt reality

Nuxt 3's Nitro server gives you /server/api/contact.post.ts for free — write a handler, parse FormData, send email, store the submission, fan out a webhook.

use case fit

Email lists still convert 5-10x social. The newsletter signup form is the single most leveraged piece of your site — pop it up smartly, not annoyingly, and it pays compound interest.

§ 01Newsletter Signup × Nuxtwhy this combination, in 80 words

Built for Nuxt developers who hate operating a backend.

Splitforms is the form backend for Nuxt sites. One POST endpoint, no SDK, no plugin — drop the newsletter signup into a page and ship.

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

Drop into any Nuxt project.

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

form.htmlhtml12 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 newsletter subscriber">
04
05 <label for="email">Your email *</label>
06 <input id="email" type="email" name="email" placeholder="you@example.com" required>
07
08 <!-- honeypot — bots fill every field -->
09 <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
10
11 <button type="submit">Send</button>
12</form>
§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first newsletter signup 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 newsletter signup into your Nuxt project

Drop the form snippet into a Nuxt 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 newsletter subscriber
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?
§ 03bNewsletter Signup Form (Email Capture)template-specific playbook

The reason this newsletter signup exists.

Webhooks into ConvertKit / Mailchimp / Substack / Beehiiv / Buttondown.

why it matters

Newsletter conversion benchmarks haven't moved much: ConvertKit / Substack landing pages convert at 1-2% of visitors, popup forms at 2-4%, content-upgrade lead magnets at 8-15%. The form itself is trivially simple (email field, optional name) but where it lives matters — exit-intent popup, scroll-triggered slide-in, footer inline, content-end inline all behave differently. Push the submission to your ESP (Mailchimp / ConvertKit / Substack / Beehiiv / Buttondown) via webhook so the welcome email fires automatically. GDPR / CASL require explicit consent — a checkbox or unbundled-consent text under the form covers it for EU and Canadian visitors.

route the submission
01

Pick the form placement

Popup (highest volume, also highest annoyance — set scroll or exit-intent triggers), inline footer (low volume, low friction), content-end inline (best conversion-quality combo).

02

Push to your ESP

Webhook the email to ConvertKit / Mailchimp / Substack / Beehiiv / Buttondown. Each has either a native webhook receiver or a Zapier connector. Welcome email fires automatically on add.

03

Add GDPR / CASL consent

EU visitors need explicit consent — add a 'I want to receive emails from [your brand]' checkbox or unbundled-consent text under the email field. Required text varies by jurisdiction; consult your privacy lawyer if in doubt.

§ 03cNuxt production notesnative path · deploy · gotchas

What changes when this newsletter signup lives in Nuxt.

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

without splitforms

Nuxt 3's Nitro server gives you /server/api/contact.post.ts for free — write a handler, parse FormData, send email, store the submission, fan out a webhook. The DX is good; the operational cost is the same as any framework: an SMTP integration (Nodemailer + a transactional provider), a Postgres or KV store for submissions, anti-spam logic (honeypot + classifier or hCaptcha), and webhook signing if you want secure delivery to Slack/Discord/Make.com. Each feature is another deploy artifact, another env var, another thing to monitor. Splitforms is the inverse: skip the /server/api route entirely (post directly from the page), or proxy through a one-line Nitro route to keep the key server-side.

deploy notes

Nuxt's Nitro server abstracts away deployment — pick a preset (vercel, netlify, cloudflare-pages, cloudflare-workers, node-server, static, aws-lambda, digital-ocean) and ship. The form's POST is cross-origin to splitforms, so the preset doesn't affect delivery. On Cloudflare Workers (10ms CPU on free tier), strongly prefer Pattern A — Pattern B's $fetch round-trip can blow the budget under load. Use runtimeConfig.public.splitformsKey (client-exposed) for Pattern A and runtimeConfig.splitformsKey (server-only) for Pattern B. Both populate from NUXT_PUBLIC_SPLITFORMS_KEY / NUXT_SPLITFORMS_KEY env vars.

Nuxt gotcha

runtimeConfig.public is required for client exposure — `runtimeConfig.x` is server-only

Nuxt's runtimeConfig has two scopes. Anything under runtimeConfig.public is exposed to the browser bundle; anything else is server-only. If you put splitformsKey directly in runtimeConfig (not .public), useRuntimeConfig().splitformsKey returns undefined client-side.

Nuxt gotcha

useRuntimeConfig() called outside setup() returns empty object

Calling useRuntimeConfig() inside a regular function (not inside <script setup> or a composable) returns {}. Always call it at the top of <script setup> and capture the value, then use config.public.splitformsKey inside event handlers.

Nuxt gotcha

Nitro Cloudflare preset has 10ms CPU time on the free plan

If you proxy the splitforms call through a Nuxt server route (/server/api/contact.post.ts), the fetch round-trip eats your Cloudflare Worker CPU budget. On Cloudflare Pages Free tier, this can fail under load. Skip the proxy: have the form POST directly to splitforms.com.

Nuxt gotcha

Nuxt Content's <ContentDoc> rendering can break form HTML

If you embed the form in a Markdown file rendered by Nuxt Content, MDC syntax may interpret your inputs as MDC components. Wrap the form in <NuxtContent> (or use :component="ContactForm") instead of inline form HTML.

PATTERN A

Pattern A — direct browser POST from `<script setup>`

No server route. Page reads the access key from useRuntimeConfig().public.splitformsKey. Works identically on every Nitro preset. Use the same wiring for the newsletter signup fields on this page.

pattern-a.txtvue18 lines
01<script setup>
02import { ref } from "vue";
03const status = ref("idle");
04const config = useRuntimeConfig();
05async function onSubmit(e) {
06 status.value = "loading";
07 const fd = new FormData(e.target);
08 fd.append("access_key", config.public.splitformsKey);
09 const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10 status.value = (await r.json()).success ? "ok" : "err";
11}
12</script>
13<template>
14 <form @submit.prevent="onSubmit">
15 <input name="email" type="email" required />
16 <button :disabled="status === 'loading'">Send</button>
17 </form>
18</template>
PATTERN B

Pattern B — Nitro server route (key stays server-side)

Page posts to /api/contact (a Nitro route) which appends the access key from runtimeConfig.splitformsKey (private) and proxies to splitforms. Adds a hop but the key never reaches the browser bundle. Use the same wiring for the newsletter signup fields on this page.

pattern-b.txtvue11 lines
01// server/api/contact.post.ts
02export default defineEventHandler(async (event) => {
03 const config = useRuntimeConfig();
04 const parts = await readMultipartFormData(event);
05 const fd = new FormData();
06 for (const p of parts ?? []) p.name && fd.append(p.name, p.data.toString("utf8"));
07 fd.append("access_key", config.splitformsKey);
08 const res = await $fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
09 if (!res.success) throw createError({ statusCode: 400, message: res.message });
10 return { ok: true };
11});
§ 04Field-by-field rundown1 fields · names you POST

What every field actually does.

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

emailREQUIRED
EMAIL

Your email

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

placeholder · you@example.com
§ 06Questions9 answered

Newsletter Signup on NuxtFAQ.

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

01Does this newsletter signup work on Nuxt?
Yes. The form is plain HTML with a single POST endpoint, so it runs on any Nuxt site without server-side code, plugins, or SDKs. Drop the snippet into a Nuxt page or component and submissions land in your splitforms dashboard.
02How much does the newsletter signup cost on Nuxt?
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 email…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.
04How does spam protection work on the newsletter signup?
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 Nuxt as on any other framework.
05Can I send the newsletter signup 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 Nuxt 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.
07Will my form trigger GDPR consent requirements?
If you have any EU or UK visitors, yes — GDPR requires explicit, freely-given consent for marketing emails. Add a separate consent checkbox (not pre-checked) below the email field. Same applies to CASL in Canada and PECR in the UK. US-only audiences fall under CAN-SPAM, which is less strict but still requires honest unsubscribe handling.
08How do I push to ConvertKit / Mailchimp / Substack / Beehiiv?
Webhook the submission as JSON. ConvertKit has a native webhook receiver per form; Mailchimp accepts via API or Zapier; Substack accepts via Beehiiv/Substack import API or Zapier; Beehiiv has direct webhook support. The newsletter platform fires the welcome sequence automatically on add.
09Does double opt-in hurt list growth?
Double opt-in drops list size by 20-30% but improves deliverability and engagement metrics — single-opt-in lists accumulate spam-trap addresses that tank inbox placement. Most serious senders run double opt-in for that reason. Substack and Beehiiv default to it.
§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

FeatureWeb3FormsFormspreesplitforms
Free monthly submissions25050500
Custom fields beyond contactYesPro tierFree
Webhooks (Slack / Discord)Pro tierPro tierFree, signed
AI / MCP submission inboxNoNoYes
Long-term plan (3-year flat)$59 every 3 years
✻ ✻ ✻

Ship a newsletter signup on Nuxt in 60 seconds.

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

Get free access key →Read the docs
founders pricing locked in · early access open