NEWSLETTER SIGNUP · HUGO

Newsletter Signup for Hugo

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 Hugo

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

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Hugo + Newsletter Signupplatform-specific integration guide

Why Hugo developers choose splitforms for newsletter signup

Hugo's build speed is legendary, but Hugo sites are static HTML — there's no built-in mechanism to process form submissions. The traditional workaround is Netlify Forms (100 subs/month free) or a third-party API. The newsletter signup on this page posts directly from the browser to splitforms with zero Hugo configuration. It works in Hugo themes, shortcodes, and partial templates — just paste the HTML. Because Hugo's output is plain HTML, the form works on any host without a server-side component.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for Hugo.

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

Hugo is a static site generator — there's no runtime, no /server/api, no way to handle a form POST without an external service.

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

Built for Hugo developers who hate operating a backend.

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

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

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

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the newsletter signup into your Hugo project

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

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.

§ 03cHugo production notesnative path · deploy · gotchas

What changes when this newsletter signup lives in Hugo.

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

without splitforms

Hugo is a static site generator — there's no runtime, no /server/api, no way to handle a form POST without an external service. The native paths are: (a) a Cloudflare Worker / Lambda / Cloud Run service handling POST /contact and emailing you (~4 hours of setup, ongoing operation), (b) Netlify Forms (Hugo-on-Netlify only, 100/mo free), or (c) a third-party form backend like Formspree, Basin, or Web3Forms. Hugo's templating shines for the form's HTML — {{ partial }}, {{ .Site.Params }} for the access key, {{< shortcode >}} for Markdown reuse — but the delivery layer is always external. Splitforms is the simplest external option that doesn't require a Cloud Run service.

deploy notes

Hugo deploys to any static host: Vercel, Netlify, Cloudflare Pages, GitHub Pages, S3, Surge, plain Apache/nginx. The form posts cross-origin so the host is irrelevant. Set splitformsKey in hugo.toml under [params] for private repos; for public repos, build with hugo --param splitformsKey=$SPLITFORMS_KEY and read it from CI env. Hugo's local dev server runs on localhost:1313 — add that to splitforms allowed-domains for testing or use a separate dev key. hugo --minify compresses HTML but doesn't touch attribute values — the form works under minification.

Hugo gotcha

Site.Params lookup is case-sensitive in some Hugo versions

If you set splitformsKey in hugo.toml under [params] but reference it as {{ .Site.Params.SplitformsKey }} in the template, recent Hugo versions still resolve it — but Hugo 0.110 and earlier don't. Use the exact case from your config file.

Hugo gotcha

Markdown content stripping eats inline form HTML

If you put a <form> directly in a Markdown content file, Goldmark's HTML sanitizer strips it. Either set markup.goldmark.renderer.unsafe = true in your config, or wrap the form in a shortcode (recommended): {{< contact-form >}}.

Hugo gotcha

absURL filter on the redirect URL adds a trailing slash you don't want

{{ "thanks/" | absURL }} produces https://yoursite.com/thanks/. Hugo's URL filter normalizes trailing slashes per your uglyURLs config — if your /thanks page lives at /thanks.html (uglyURLs=true), the redirect 404s. Hardcode the URL or set relURL consistently.

Hugo gotcha

Hugo modules / theme overrides require partial in your project, not the theme

If you copy contact-form.html into a vendored theme's layouts/partials/, your changes get overwritten on the next theme update. Always put custom partials in your project's own layouts/partials/ — Hugo's lookup chain prefers project over theme automatically.

PATTERN A

Pattern A — partial in `layouts/partials/contact-form.html`

Reusable partial called from any template with {{ partial "contact-form.html" . }}. Pulls the access key from Site.Params.splitformsKey. Project-level partials override theme partials automatically. Use the same wiring for the newsletter signup fields on this page.

pattern-a.htmlhtml8 lines

01{{/* layouts/partials/contact-form.html */}}
02<form action="https://splitforms.com/api/submit" method="POST">
03  <input type="hidden" name="access_key" value="{{ .Site.Params.splitformsKey }}" />
04  <input type="hidden" name="redirect"   value="{{ "thanks/" | absURL }}" />
05  <input name="email" type="email" required />
06  <textarea name="message" required></textarea>
07  <button type="submit">Send</button>
08</form>

PATTERN B

Pattern B — shortcode usable from Markdown content

Save as layouts/shortcodes/contact-form.html. Now writers can drop {{< contact-form >}} (with optional redirect="…" arg) directly into any .md file. Eliminates the need to switch to template editing for one-off forms. Use the same wiring for the newsletter signup fields on this page.

pattern-b.htmlhtml9 lines

01{{/* layouts/shortcodes/contact-form.html */}}
02{{- $redirect := .Get "redirect" | default "/thanks/" -}}
03<form action="https://splitforms.com/api/submit" method="POST">
04  <input type="hidden" name="access_key" value="{{ .Site.Params.splitformsKey }}" />
05  <input type="hidden" name="redirect"   value="{{ $redirect | absURL }}" />
06  <input name="email" type="email" required />
07  <textarea name="message" required></textarea>
08  <button type="submit">Send</button>
09</form>

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

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

01Does this newsletter signup work on Hugo?

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

02How much does the newsletter signup cost on Hugo?

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 Hugo 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 Hugo 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 Hugo5 adjacent patterns

Ship a newsletter signup on Hugo in 60 seconds.

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

Get free access key →Read the docs

founders pricing locked in · early access open

Newsletter Signup for Hugo

Why Hugo developers choose splitforms for newsletter signup

Yes — this is the shortest safe path for Hugo.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Hugo developers who hate operating a backend.

Drop into any Hugo project.

Generate, embed, receive.

Generate a free splitforms key

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

Site.Params lookup is case-sensitive in some Hugo versions

Markdown content stripping eats inline form HTML

absURL filter on the redirect URL adds a trailing slash you don't want

Hugo modules / theme overrides require partial in your project, not the theme

Pattern A — partial in `layouts/partials/contact-form.html`

Pattern B — shortcode usable from Markdown content

What every field actually does.

Your email

One backend. Every framework.

Newsletter Signup on Hugo — FAQ.

splitforms vs everything else.

Other ready-to-ship Hugo forms.

Ship a newsletter signup on Hugo in 60 seconds.