Short answer: If the site is hosted on Netlify, use Netlify Forms: it needs one HTML attribute, filters spam with Akismet, and on Netlify's newer credit-based plans form submissions are free and unlimited. Anywhere else, Web3Forms has the biggest free tier (250 submissions a month) but doesn't store submissions, while Formspree and Basin give you a dashboard, archive and better spam tools with smaller free tiers (50 a month each).
A static site has no server to receive a POST, so a contact form needs a form backend: a hosted endpoint that accepts the submission, filters spam and emails it to the business. All four of these work with a plain <form action="...">, no JavaScript required. Limits and prices below are from each vendor's own pages, checked November 2026.
Which form backend has the best free tier?
On raw numbers, Web3Forms (250 submissions a month, unlimited forms) and Netlify Forms on a credit-based plan (no submission limit) are the most generous. Formspree and Basin both cap free accounts at 50 submissions a month, and Basin's free plan allows only one form.
| Formspree | Netlify Forms | Basin | Web3Forms | |
|---|---|---|---|---|
| Free submissions/month | 50 | Unlimited on credit-based plans; metered on legacy plans | 50 | 250 |
| Forms on free | Unlimited | Unlimited | 1 | Unlimited |
| Stores submissions | Yes, 30-day archive on free | Yes, in the Netlify UI | Yes, 30-day retention on free | No, email/webhook only |
| File uploads on free | No (0 GB) | Yes (metered on legacy plans) | 100 MB | No (Pro) |
| Spam, free tier | Basic filtering, reCAPTCHA, _gotcha honeypot |
Akismet on everything, honeypot, reCAPTCHA 2 | Basic spam protection | Spam checks, hCaptcha, botcheck honeypot |
| First paid tier | $15/mo or $120/yr (200 submissions) | Netlify plan pricing | $12.50/mo billed yearly (250) | $12/mo or $149/yr (20k) |
| Hosting | Any | Netlify only | Any | Any |
A note on Netlify's two pricing systems: accounts created from September 4, 2025 use credit-based plans, and Netlify's billing FAQ says that on those plans "form usage is free and unlimited," with no submission limits or tiers. Older accounts on legacy plans are metered by submissions and upload storage; the docs' example of the lowest level is 100 submissions and 10 MB of uploads a month.
How do you set up Formspree on a static site?
Create a form in the Formspree dashboard, copy its ID, and point your form's action at https://formspree.io/f/YOUR_FORM_ID. That's the whole integration for a basic contact form.
<form action="https://formspree.io/f/YOUR_FORM_ID" method="POST">
<label>Name <input name="name" autocomplete="name" required></label>
<label>Email <input type="email" name="email" autocomplete="email" required></label>
<label>Message <textarea name="message" rows="5" required></textarea></label>
<!-- Honeypot: humans never see it, bots fill it in -->
<input type="text" name="_gotcha" class="visually-hidden" tabindex="-1" autocomplete="off">
<button type="submit">Send message</button>
</form>
Formspree's docs say a filled _gotcha field is treated as a bot and the submission is "silently ignored," and the honeypot is available on all plans. They suggest hiding it with a CSS class rather than an inline style.
The free plan (50 submissions a month as of November 2026) is enough for a lot of small businesses, but it lacks a custom thank-you page, submission export and autoresponses. Paid plans are $15/month (Personal, 200 submissions), $30 (Professional, 2,000) and $90 (Business, 20,000) on monthly billing, cheaper on yearly. Advanced spam control starts at Professional; custom honeypot and spam rules at Business. Uploads, where included, are limited to 25 MB per file.
How do Netlify Forms work?
Netlify parses your HTML at deploy time and wires up any form marked with data-netlify="true". You have to switch on form detection once in the Netlify UI (Forms, then Enable form detection), and it applies from the next deploy.
<form name="contact" method="POST" data-netlify="true" netlify-honeypot="bot-field">
<p class="visually-hidden">
<label>Don't fill this out: <input name="bot-field"></label>
</p>
<label>Name <input name="name" required></label>
<label>Email <input type="email" name="email" required></label>
<label>Message <textarea name="message" required></textarea></label>
<button type="submit">Send</button>
</form>
During the build Netlify strips the attribute and injects a hidden form-name input. Every submission is checked with Akismet; the ones it flags land under Spam submissions, which you can review. Submissions caught by the honeypot or a failed reCAPTCHA 2 challenge are dropped completely and don't show up anywhere.
The thing that trips people up: JavaScript-rendered forms are invisible to the build. If your form only exists after React or Vue renders it, Netlify won't find it. The docs give two fixes: add a hidden static HTML copy of the form with the same field names, or include <input type="hidden" name="form-name" value="contact"> in the rendered form.
For AJAX submissions, Netlify wants URL-encoded data, not JSON:
form.addEventListener('submit', async (e) => {
e.preventDefault();
const body = new URLSearchParams(new FormData(form)).toString();
await fetch('/', {
method: 'POST',
headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
body,
});
});
One more legacy-plan caveat from Netlify's billing FAQ: when a free legacy account hits 100% of a metered limit, new builds are disabled and all sites on the account are paused until you upgrade. Know which plan your client's account is on.
Is Basin worth it for client sites?
Basin is the most "client-ready" of the four once you pay: a proper dashboard, a long list of spam tools, and integrations. Its free plan is a trial in practice, with one form, 50 submissions a month and 30-day retention.
Setup is the same pattern as Formspree, with an endpoint like https://usebasin.com/f/1a2b3c4d5e6f. If you submit with JavaScript and want JSON back, Basin's docs say you must send an Accept: application/json header.
Basin's spam documentation lists reCAPTCHA v2 and v3, hCaptcha, Cloudflare Turnstile, honeypot fields, email validation, geographic filtering, duplicate detection and AI-based content detection. The pricing page ties the advanced filters to the Pro plan, so check which ones your tier gets.
Paid plans as of November 2026 on yearly billing: Starter $12.50/month (250 submissions, 3 forms), Growth $24.17 (1,000, unlimited forms, webhooks and API), Pro $30.62 (5,000). Basin's pricing page says submissions over your cap are still delivered and billed as overage, which is friendlier than having a client's leads bounce.
What's the catch with Web3Forms?
Web3Forms doesn't store your submissions. Its FAQ says: "We do not store any form submissions of our users." Each one is forwarded to your email or a webhook and that's it. For some clients that's a privacy plus; for others it means a lost email is a lost lead.
<form action="https://api.web3forms.com/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
<input type="hidden" name="redirect" value="https://example.com/thanks">
<input type="checkbox" name="botcheck" class="visually-hidden" tabindex="-1">
<input name="name" required>
<input type="email" name="email" required>
<textarea name="message" required></textarea>
<button type="submit">Send</button>
</form>
The access key sits in your HTML, and the Web3Forms docs say that's fine to make public. Without JavaScript you need the redirect field, because the default response is JSON. Restricting submissions to your own domain is a Pro feature, as are reCAPTCHA, Turnstile and file uploads; hCaptcha works on free.
The free tier is 250 submissions a month with unlimited forms and domains, and you can use it without creating an account. Pro is $12/month or $149/year for 20,000 submissions.
How do you stop contact form spam on a static site?
Layer it: a honeypot field on every form, the service's server-side filter, and a CAPTCHA only if spam still gets through. Most local business forms get by with the first two, and skipping the CAPTCHA keeps the form easier to use on a phone.
A few habits that help regardless of backend:
-
Hide honeypots with a class, not
type="hidden". Many bots skiptype="hidden"inputs. Use a visually-hidden class andtabindex="-1"so keyboard users never land on it. -
Validate in HTML.
type="email"andrequiredcost nothing and stop junk. - Send to an address someone reads daily, and do a test submission at handover with the owner watching.
- Prefer a privacy-friendly CAPTCHA (Turnstile or hCaptcha) if you do need one.
Which one should you pick for a client?
Our defaults:
- Site on Netlify: Netlify Forms. Nothing else to sign up for, Akismet built in.
- Elsewhere, client wants a dashboard and an archive: Formspree free to start, a paid plan once they rely on it. Basin if they want more spam tools and integrations and will pay from day one.
- Elsewhere, high volume, no budget, email is fine: Web3Forms, with the honeypot and hCaptcha turned on.
Whichever you choose, set up the account under the client's email, not yours. When they stop paying for your care plan, their leads shouldn't stop arriving.
Fictional example handover note: "Your contact form sends to the hello@ address on your business email. Messages also stay in the Formspree dashboard for 30 days. If a customer says they filled it in and you didn't get it, check spam first, then the dashboard."
Finding sites with broken contact forms
A form that posts nowhere, a mailto link that opens nothing on mobile, or a contact page with no form at all: you'll see these constantly if you test local business sites from your phone. Submit a form with a clearly labelled test message and see whether the page even confirms it.
If you want a head start on the list, LeadReef finds local businesses whose websites are outdated, broken on mobile or missing, shows what's wrong with each one, and helps with a first mockup and outreach message. You pick who to contact and send it yourself, and the first 10 leads are free. It also runs inside Cursor, Claude or ChatGPT through MCP, if you'd rather ask for leads from your editor. Full disclosure: we build LeadReef. Everything above works without it.
Frequently asked questions
Can I add a contact form to a static site without a backend?
Not without some backend, but you don't have to run one. Formspree, Netlify Forms, Basin and Web3Forms each give you an endpoint to put in the form's action attribute, and they handle storage, spam filtering and email.
Are Netlify Forms free?
On Netlify's credit-based plans (all new accounts since September 4, 2025), the billing FAQ says form usage is free and unlimited. On older legacy plans, submissions and uploads are metered, and hitting a free-tier limit can pause the account's sites.
Is it safe to put a form access key in HTML?
For Web3Forms, its docs say the access key can be public. Formspree and Basin endpoints are public by design too. Protect them with honeypots, server-side spam filtering and, on paid plans, domain restrictions.
Why does my Netlify form not show up in the dashboard?
Usually because form detection isn't enabled, or the form is rendered by JavaScript and wasn't in the built HTML. Add a static copy of the form or a hidden form-name input, then redeploy.
Which free form service stores submissions?
Formspree (30-day archive on free), Basin (30-day retention on free) and Netlify Forms keep submissions you can view later. Web3Forms forwards them and doesn't store them.
Sources (checked November 2026): Formspree plans; Formspree Help, Honeypot spam filtering; Formspree, Eleventy guide; Netlify Docs, Forms setup, Spam filters, Forms usage and billing, Billing FAQ for credit-based plans and Billing FAQ for legacy plans; Basin pricing; Basin Docs, HTML form backend and Spam protection overview; Web3Forms pricing; Web3Forms Docs, Installation and FAQ.



Top comments (0)