Blog
Email signup forms on a static site (without an email marketing platform)
· 4 min read
A newsletter signup, a waitlist, a "notify me when it's live" box - these start life as form problems, not marketing problems. One field, usually just an email address. Traffic that's quiet for weeks and then spikes the moment a link goes out. And a very common reflex the instant you sit down to build one: open a Mailchimp or ConvertKit account, drop their embed snippet on the page, and never look back - even though what you actually wanted was a form that goes somewhere, not a marketing platform.
A form problem wearing a marketing platform's clothes
Think about what an early-stage signup box actually needs to do: show a field, validate an email, store it somewhere you can see, and tell you when someone new shows up. That's it. No automation, no segmentation, no A/B-tested subject lines - because there's no newsletter to send yet. It might be a waitlist before you've even picked a product to build, or a personal site's "get new posts" box that will never justify a monthly subscription. The job is capture, not campaigns.
The reason people reach for a full email marketing platform this early usually isn't that they need one - it's that there's no obvious lighter option that comes to mind first. An ESP's embed form is free to add and it "just works," so it becomes the default even for a single input field. The cost shows up later: a third-party JavaScript SDK loaded on every page view, its own cookies and tracking, and an account with settings, audiences, and tags to manage before you've written a single campaign.
When a lightweight form backend is the right tool
A hosted form backend handles exactly the part you need right now, and nothing more:
<form action="https://formhook.app/f/fh_your-key" method="POST">
<input type="email" name="email" required autocomplete="email" />
<button type="submit">Subscribe</button>
</form>Point that action at a form endpoint and the field is live - no SDK, no cookies, no account to configure beyond the form itself. Submissions land in a dashboard, spam is filtered before it reaches you (a honeypot field, rate limiting, and Cloudflare Turnstile switched on by default), and you get notified the moment someone signs up. On Formhook that's free for up to 250 submissions a month, no card required - which comfortably covers a waitlist or an early site's mailing list.
When you actually want a dedicated ESP
The lightweight approach stops being the right one once there's an actual newsletter to run: automated welcome sequences, drip campaigns, subscriber segmentation, A/B-tested sends, or - the part that's genuinely hard to DIY - the inbox deliverability reputation built up over thousands of sends. That's a real product with a real team behind it, worth paying for once you're actually using it. The point isn't to avoid an ESP forever; it's to not pay for one, configure one, and load its script on every page before you have a reason to.
Be honest about what this is
Worth saying plainly: a form backend is not an email marketing platform. Formhook collects the signup and notifies you that it happened - it does not send your newsletter, and it never will. What it does give you is ownership: every submission is stored as data you control, and a full-account export (a ZIP with all forms, submissions, and files) means the list is never locked in. When the day comes that you outgrow a simple signup box, you export the emails and import them straight into whichever ESP you've chosen - no scraping a dashboard, no starting from zero.
For a waitlist, an early product, or a site that just wants "notify me" without a marketing SDK bolted on, that's the whole job. See the free tier and have the form live in a couple of minutes.
Ship a working form in one line
EU-hosted, submissions kept forever, push notifications on every tier.
Start freeNo credit card · read the docs
Keep reading
- File uploads on a static site: your real optionsStatic hosting can't receive files - but your forms still can. How multipart uploads work through a form backend, plus limits, security, and GDPR storage.
- What is a form backend? (And when you need one)A form backend receives, stores, and forwards your website's form submissions so you don't run a server. Here's how they work and when you need one.
- How to add a contact form to GitHub PagesGitHub Pages can't run server code, but you can still have a working contact form. Three approaches compared, with a copy-paste solution that takes a minute.