Newsletter Signup for Framer (free, no backend)

§ 00Framer + Newsletter Signupplatform-specific integration guide

Why Framer developers choose splitforms for newsletter signup

Framer's code component feature lets you drop custom HTML directly into your design, which is where this newsletter signup fits. Framer's built-in form actions are limited — they forward to a Framer webhook that lacks email delivery, spam filtering, and a dashboard. The newsletter signup on this page bypasses Framer's form system entirely: paste it into a code component, and submissions go straight to splitforms for email, webhooks, spam filtering, and dashboard storage. Framer handles the design; splitforms handles the delivery.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for Framer.

Use the HTML snippet on this page, keep the newsletter signup fields visible in your Framer 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 framer reality

Framer's built-in form widget delivers submissions to a single email address (configured per form) with no dashboard for managing submissions, no webhooks below the Pro plan, and no spam filtering beyond Framer's basic bot detection.

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

Built for Framer developers who hate operating a backend.

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

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

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Framer 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 Framer project

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

§ 03cFramer production notesnative path · deploy · gotchas

What changes when this newsletter signup lives in Framer.

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

without splitforms

Framer's built-in form widget delivers submissions to a single email address (configured per form) with no dashboard for managing submissions, no webhooks below the Pro plan, and no spam filtering beyond Framer's basic bot detection. CMS-driven Framer forms inherit the same constraints. The native flow works for a portfolio's contact form; it falls apart for any setup that needs Slack/Discord notifications, multiple recipients, CSV export, or tagged form-name routing. Replacing it means writing a Code Component — Framer's mechanism for embedding custom React. That's the pattern splitforms uses: a Code Component with the access key as a property control, dropped onto the canvas like a native widget.

deploy notes

Framer publishes sites to its own CDN — there's no Vercel/Netlify config to manage. The form posts cross-origin to splitforms regardless. Framer's published sites have a default Content Security Policy that may block connect-src to splitforms.com on some plans; if submissions silently fail, add <meta http-equiv="Content-Security-Policy" content="connect-src https://splitforms.com"> via Site Settings → Custom Code → Head HTML. Lock the access key to BOTH your *.framer.app preview URL AND your custom domain — Framer serves both with different Origin headers. Framer's preview environment runs Code Components live, so you can test the form before publishing.

Framer gotcha

addPropertyControls must be the LAST statement in the file

Framer reads property controls only if addPropertyControls(Component, {...}) is called after the component is exported. If you put it before the export or wrap it in a conditional, the access-key control disappears from the right panel and you can't set the key visually.

Framer gotcha

Framer's canvas re-renders the component on every prop change

Editing the access key in the right panel re-mounts the form mid-edit. If a user is testing the form when you change the key, their status === 'loading' state resets to 'idle' visually but the in-flight fetch still completes. Not a bug in production — only an editor quirk.

Framer gotcha

Framer's published page CSP blocks splitforms.com unless you set it

Framer's published sites have a default Content Security Policy that allows known integrations. Splitforms isn't on the default allowlist — you may need to add connect-src https://splitforms.com via Framer's Site Settings → Custom Code → Head HTML, inside a <meta http-equiv="Content-Security-Policy" content="…"> tag.

Framer gotcha

Code Components don't get Framer's font system by default

If you use style={{ fontFamily: '...' }} in a Code Component, you have to import the font manually — Framer's site fonts only auto-apply to canvas-built elements. Use font-family: inherit to inherit from the parent frame.

PATTERN A

Pattern A — Code Component with property control

Paste into Framer's Code Components panel. The access key becomes a property in the right-side inspector — designers swap keys per page or per environment without touching code. Use the same wiring for the newsletter signup fields on this page.

pattern-a.tsxtsx19 lines

01// ContactForm.tsx (Framer Code Component)
02import { useState } from "react";
03import { addPropertyControls, ControlType } from "framer";
04export default function ContactForm({ accessKey = "YOUR_ACCESS_KEY" }) {
05  const [status, setStatus] = useState<"idle" | "loading" | "ok" | "err">("idle");
06  return (
07    <form onSubmit={async (e) => {
08      e.preventDefault(); setStatus("loading");
09      const fd = new FormData(e.currentTarget);
10      fd.append("access_key", accessKey);
11      const r = await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
12      setStatus((await r.json()).success ? "ok" : "err");
13    }} style={{ display: "grid", gap: 12 }}>
14      <input name="email" type="email" required />
15      <button disabled={status === "loading"}>Send</button>
16    </form>
17  );
18}
19addPropertyControls(ContactForm, { accessKey: { type: ControlType.String } });

PATTERN B

Pattern B — Framer override (apply to existing canvas form)

If you already designed a form on the canvas with Framer's native form widget, an override can intercept its submit and re-route to splitforms. Useful when you want to keep the canvas-built design but swap the backend. Use the same wiring for the newsletter signup fields on this page.

pattern-b.tsxtsx12 lines

01// SplitformsOverride.tsx
02import type { ComponentType } from "react";
03export function withSplitforms(Component): ComponentType {
04  return (props) => (
05    <Component {...props} onSubmit={async (e) => {
06      e.preventDefault();
07      const fd = new FormData(e.currentTarget);
08      fd.append("access_key", "YOUR_ACCESS_KEY");
09      await fetch("https://splitforms.com/api/submit", { method: "POST", body: fd });
10    }} />
11  );
12}

§ 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

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

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

01Does this newsletter signup work on Framer?

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

02How much does the newsletter signup cost on Framer?

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 Framer 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 Framer 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 Framer5 adjacent patterns

Ship a newsletter signup on Framer in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Newsletter Signup for Framer

Why Framer developers choose splitforms for newsletter signup

Yes — this is the shortest safe path for Framer.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Framer developers who hate operating a backend.

Drop into any Framer project.

Generate, embed, receive.

Generate a free splitforms key

Paste the newsletter signup into your Framer 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 Framer.

addPropertyControls must be the LAST statement in the file

Framer's canvas re-renders the component on every prop change

Framer's published page CSP blocks splitforms.com unless you set it

Code Components don't get Framer's font system by default

Pattern A — Code Component with property control

Pattern B — Framer override (apply to existing canvas form)

What every field actually does.

Your email

One backend. Every framework.

Newsletter Signup on Framer — FAQ.

splitforms vs everything else.

Other ready-to-ship Framer forms.

Ship a newsletter signup on Framer in 60 seconds.