Newsletter Signup for Astro
Email-only newsletter capture — perfect for footers and landing pages. Free for 500 submissions per month — no backend, no SDK, no plugin.
Why Astro developers choose splitforms for newsletter signup
Astro's static-first architecture means your form HTML ships pre-rendered with zero client JavaScript — perfect for fast page loads, but it also means you can't call a server-side endpoint on static hosts. splitforms is designed for exactly this: the browser POSTs directly to our edge endpoint, so the form works on Netlify, Cloudflare Pages, Vercel, or any static host without an Astro API route. The newsletter signup is pure HTML — no <code><script></code> tag, no client component, no island. Astro's view transitions and partial hydration don't interfere with the form submission because it uses a standard browser POST.
Yes — this is the shortest safe path for Astro.
Use the HTML snippet on this page, keep the newsletter signup fields visible in your Astro UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.
Paste the HTML version, then replace YOUR_ACCESS_KEY.
The posted payload contains your email. Required fields are your email.
Astro's whole pitch is shipping zero JavaScript by default.
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.
Built for Astro developers who hate operating a backend.
Splitforms is the form backend for Astro sites. One POST endpoint, no SDK, no plugin — drop the newsletter signup into a page and ship.
Splitforms is the form backend for Astro 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.
- ✓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)
Drop into any Astro project.
Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Astro page, and ship. No build-time integration required.
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.
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 newsletter signup into your Astro project
Drop the form snippet into a Astro 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
Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.
The reason this newsletter signup exists.
Webhooks into ConvertKit / Mailchimp / Substack / Beehiiv / Buttondown.
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.
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.
What changes when this newsletter signup lives in Astro.
These notes come from the Astro platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.
Astro's whole pitch is shipping zero JavaScript by default. A native contact form on Astro means either (a) building a form with no submission target — useless — or (b) standing up an API endpoint via output: 'server' or 'hybrid', which means writing a Node/Bun/Deno handler, picking an email provider, writing your own honeypot logic. Astro 5 added typed Actions, but they're a wrapper around the same underlying fetch — you still deliver the email yourself. The result: every Astro contact-form tutorial ends with 'now configure SendGrid'. Splitforms is the SendGrid-replacement that doesn't require an account, an API key for the email provider, or DNS records for SPF/DKIM.
Astro deploys cleanly to Vercel, Netlify, Cloudflare Pages, GitHub Pages, and any static host with output: 'static'. For Astro Actions (Pattern B), you need output: 'server' or 'hybrid' and a matching adapter (@astrojs/vercel, @astrojs/netlify, @astrojs/cloudflare). On Cloudflare Pages with the Cloudflare adapter, the Action runs in a Worker — keep the splitforms fetch tight (no extra proxying) to stay under the 10ms CPU budget on the free plan. The PUBLIC_ prefix is mandatory for env vars exposed to client-rendered .astro files; vars without it are silently undefined. Lock the key to your *.pages.dev and custom domain.
PUBLIC_ prefix is required for client-exposed env vars
Astro mirrors Vite's env-var convention: only variables prefixed with PUBLIC_ are exposed to client-side code (and to .astro files when output: 'static'). If you write import.meta.env.SPLITFORMS_KEY, you'll get undefined at build time. Rename to PUBLIC_SPLITFORMS_KEY.
client:load on the form island defeats the point of Astro
If you wrap the form in <MyForm client:load />, you ship a full React/Preact runtime just for one form. Use client:visible (load when scrolled into view) or client:idle (load after main thread is free) instead. For zero-JS forms, skip the island entirely and use a plain HTML form action.
Astro Actions need a try/catch or they crash the page
If your action throws, Astro 5's behavior is to render an error page rather than return the error to your form. Wrap the splitforms fetch in try/catch and return { success: false, message } from the action — your form component can then render the message.
View Transitions can break form re-submit state
If you've enabled <ViewTransitions /> in your layout, navigating to /contact and back may re-mount the form mid-submission. Add data-astro-reload to the form's submit anchor or guard with if (status === 'loading') return at the top of your handler.
Pattern A — pure HTML form (zero JS shipped)
The Astro-native approach: a .astro file with frontmatter pulling the key from import.meta.env, then a static <form action> that posts directly. Zero hydration, zero island, zero KB JavaScript. Use the same wiring for the newsletter signup fields on this page.
Pattern B — Astro Action for typed server-side proxying
Astro 5 Actions give you Zod-validated, type-safe form handlers. Use one to keep the access key off the client entirely — the form posts to the action, the action proxies to splitforms. Use the same wiring for the newsletter signup fields on this page.
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.
Your email
Reply-to address — splitforms wires this so hitting reply goes back to the sender.
One backend. Every framework.
The same newsletter signup template works on every framework splitforms supports. Pick yours.
Newsletter Signup on Astro — FAQ.
Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.
splitforms vs everything else.
Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.
Other ready-to-ship Astro forms.
Same backend, different qualifying fields. Click through to copy the snippet.
Ship a newsletter signup on Astro in 60 seconds.
500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Astro project.