NEWSLETTER SIGNUP · GATSBY

Newsletter Signup for Gatsby

Email-only newsletter capture — perfect for footers and landing pages. 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 Gatsby

Form.tsxtsx41 lines

01'use client';
02 
03import { useState, type FormEvent } from 'react';
04 
05export default function NewsletterForm() {
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 newsletter subscriber');
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="email">Your email *</label>
32      <input id="email" type="email" name="email" placeholder="you@example.com" required />
33 
34      <button type="submit" disabled={status === 'sending'}>
35        {status === 'sending' ? 'Sending…' : 'Send'}
36      </button>
37 
38      {status === 'error' && <p>Something went wrong. Try again.</p>}
39    </form>
40  );
41}

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Gatsby + Newsletter Signupplatform-specific integration guide

Why Gatsby developers choose splitforms for newsletter signup

Gatsby's static output is excellent for SEO and performance, but static HTML forms have no way to deliver submissions without a backend. Gatsby Cloud offers serverless functions, but wiring SMTP and a dashboard is a substantial project for what should be a simple contact form. The newsletter signup on this page posts from the browser to splitforms — no Gatsby Function, no API route, no build-time configuration. The form works identically whether you deploy to Gatsby Cloud, Netlify, Cloudflare Pages, or any static host.

§ 00Quick answerReact / Next.js · marketing

Yes — this is the shortest safe path for Gatsby.

Use the React / Next.js snippet on this page, keep the newsletter signup fields visible in your Gatsby 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 your email. Required fields are your email.

native gatsby reality

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 × Gatsbywhy this combination, in 80 words

Built for Gatsby developers who hate operating a backend.

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

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

Drop into any Gatsby project.

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

Form.tsxtsx41 lines

01'use client';
02 
03import { useState, type FormEvent } from 'react';
04 
05export default function NewsletterForm() {
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 newsletter subscriber');
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="email">Your email *</label>
32      <input id="email" type="email" name="email" placeholder="you@example.com" required />
33 
34      <button type="submit" disabled={status === 'sending'}>
35        {status === 'sending' ? 'Sending…' : 'Send'}
36      </button>
37 
38      {status === 'error' && <p>Something went wrong. Try again.</p>}
39    </form>
40  );
41}

ALTPrefer plain HTML? View the universal newsletter signup HTML snippet12 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 newsletter subscriber">

  <label for="email">Your email *</label>
  <input id="email" type="email" name="email" placeholder="you@example.com" required>

  <!-- 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 newsletter signup 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 newsletter signup into your Gatsby project

Drop the form snippet into a Gatsby 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 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

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).

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.

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.

§ 03cGatsby production notesnative path · deploy · gotchas

What changes when this newsletter signup lives in Gatsby.

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

without splitforms

Gatsby builds a static React app, so 'native' means choosing between (a) Netlify Forms (Gatsby-on-Netlify only, 100 free submissions/month, gatsby-plugin-netlify required), (b) Gatsby Functions (deprecated in Gatsby 5 — they were removed when Gatsby Cloud shut down), or (c) a third-party form backend. Gatsby v4 had Functions running as Lambda-equivalent serverless routes; v5 removed them entirely. Result: every Gatsby contact form today uses an external service. Splitforms is a drop-in replacement — same shape as Netlify Forms (POST to a URL), same shape as Formspree, but with 5× the free monthly submissions and built-in spam filtering.

deploy notes

Gatsby builds static HTML + JS that deploys to any host: Netlify, Vercel, Cloudflare Pages, AWS Amplify, S3 + CloudFront, Gatsby Cloud (sunset 2024 — migrate). The form posts cross-origin to splitforms regardless of host. Env vars exposed to the browser bundle must be prefixed GATSBY_ — anything else is undefined client-side. The key gets bundled into the JS at build time; lock it to your domain in the splitforms dashboard. For headless Gatsby + WordPress / Contentful setups, the form lives in the React tree, not the CMS — no special CMS wiring required.

Gatsby gotcha

GATSBY_ prefix required for env vars exposed at build time

Gatsby's webpack config only exposes process.env.* variables prefixed with GATSBY_. If you write process.env.SPLITFORMS_KEY, you'll get undefined in the browser bundle. Rename to GATSBY_SPLITFORMS_KEY — and accept that it's bundled into the static JS (lock the key to your domain in the splitforms dashboard).

Gatsby gotcha

Gatsby's <Link> can't wrap a form's submit handler

Gatsby's <Link> component prevents default navigation. If you wrap your form in <Link to="/thanks"> thinking the redirect will fire, it won't — the form's submit event runs, but the navigation is suppressed. Use a hidden redirect input on the form and let splitforms handle the 302.

Gatsby gotcha

SSR + client hydration mismatch on form initial state

If you use useState('idle') in your form and render any state-dependent UI on first paint, Gatsby's static HTML and React's client render can diverge — you'll see a hydration warning. Render the form unconditionally; only render status messages inside the handler-triggered branches.

Gatsby gotcha

Gatsby v5 partial hydration changed how forms hydrate

Gatsby 5 introduced partial hydration via React Server Components. If your form is in a Server Component, the onSubmit handler won't bind. Add 'use client' at the top of the file (or use a separate ContactForm.client.jsx).

PATTERN A

Pattern A — React component (Gatsby v4/v5)

Standard React function component, useState for status. Drop into src/components/ContactForm.jsx and import on any page. Set GATSBY_SPLITFORMS_KEY in .env.production and .env.development. Use the same wiring for the newsletter signup fields on this page.

pattern-a.jsxjsx16 lines

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

PATTERN B

Pattern B — partial hydration (Gatsby v5)

Gatsby 5's partial hydration mounts only the components marked client-bound. Add 'use client' at the top of the form file so the onSubmit handler binds at hydration time; the rest of the page stays static. Use the same wiring for the newsletter signup fields on this page.

pattern-b.jsxjsx7 lines

01// src/components/ContactForm.jsx
02"use client";
03import React, { useState } from "react";
04export default function ContactForm() {
05  const [status, setStatus] = useState("idle");
06  // ...same body as Pattern A
07}

§ 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

Your email

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

placeholder · you@example.com

§ 05Newsletter Signup on other frameworks21 frameworks · same backend

One backend. Every framework.

The same newsletter signup template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Newsletter Signup on Gatsby — FAQ.

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

01Does this newsletter signup work on Gatsby?

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

02How much does the newsletter signup cost on Gatsby?

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 Gatsby 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 Gatsby 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.

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 Gatsby5 adjacent patterns

Ship a newsletter signup on Gatsby in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Newsletter Signup for Gatsby

Why Gatsby developers choose splitforms for newsletter signup

Yes — this is the shortest safe path for Gatsby.

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

Built for Gatsby developers who hate operating a backend.

Drop into any Gatsby project.

Generate, embed, receive.

Generate a free splitforms key

Paste the newsletter signup into your Gatsby project

Receive submissions

The reason this newsletter signup exists.

Pick the form placement

Push to your ESP

Add GDPR / CASL consent

What changes when this newsletter signup lives in Gatsby.

GATSBY_ prefix required for env vars exposed at build time

Gatsby's <Link> can't wrap a form's submit handler

SSR + client hydration mismatch on form initial state

Gatsby v5 partial hydration changed how forms hydrate

Pattern A — React component (Gatsby v4/v5)

Pattern B — partial hydration (Gatsby v5)

What every field actually does.

Your email

One backend. Every framework.

Newsletter Signup on Gatsby — FAQ.

splitforms vs everything else.

Other ready-to-ship Gatsby forms.

Ship a newsletter signup on Gatsby in 60 seconds.