Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Formspree, Forminit, Basin, Web3Forms, or roll your own? A practical framework for picking a form backend — and the questions that separate a toy from a tool.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Judge a form backend on five axes: email deliverability, spam filtering, conditional routing, file handling, and price at your real monthly volume. Tools that only 'forward the email' work until you need routing or attachments — which is the line between a form forwarder and a full backend.
"Form backend" covers everything from a one-line email forwarder to a full submission platform, and the category has gotten crowded. If you're choosing in 2026, don't start from the feature grid — start from what your forms actually have to do. Here's the framework we'd use, plus the five axes that separate a weekend toy from something you can hand to a client.
Three rough tiers cover most projects. A side project or portfolio needs a contact form that reaches your inbox and blocks spam — almost anything works, so optimise for simplicity and price. A growing product needs deliverability, an autoresponder, and somewhere submissions are stored and searchable. An agency or team needs routing, per-form sending domains, file uploads, and a clean way to hand accounts to clients. Match the tool to the tier you're actually in — not the one you imagine you'll reach.
A form is worthless if its notifications land in spam. Ask whether the tool sends from a shared domain or lets you connect your own SMTP / sending domain, and whether it handles SPF/DKIM alignment. Sending from your own domain is the single biggest deliverability win; we explain the mechanics in custom-domain email sending, explained.
Every public form gets bots. Look for server-side scoring and a honeypot by default, with an optional challenge for suspicious traffic — not a CAPTCHA bolted onto every submission. Our guide to stopping form spam covers what "good" looks like.
This is the clearest line between a forwarder and a backend. Can one form send sales enquiries to sales and bug reports to support, based on a field — without you wiring up Zapier? If routing matters to you, read conditional routing recipes and check it's built in, not bolted on.
Job applications, support tickets, and design briefs all need attachments. Many lightweight tools cap uploads at a few megabytes or don't support them at all. If you'll ever accept a resume or a screenshot, confirm the size limit and where files are stored — our practical guide to form file uploads is a good checklist.
Free tiers are generous until you launch. Model your actual monthly submissions and read the pricing at that number, including overage behaviour. A plan that's free at 50/month can get expensive at 5,000. Compare our numbers on the pricing page and decide with real figures, not the headline.
You can always write your own endpoint. The question is whether re-implementing spam scoring, deliverability, retries, storage, and a dashboard is a better use of your time than shipping the product. We made the honest case in build vs buy: a contact form API — for most teams, buy wins until you have a genuinely custom requirement.
Formspree and Forminit are well-known form forwarders that shine for simple contact forms. FormBridge sits a tier up: routing, per-form sending domains, 100 MB uploads, autoresponders, and a searchable inbox are built in rather than add-ons. For head-to-head detail, see FormBridge vs Formspree and FormBridge vs Forminit, or the broader field in Basin vs Getform vs Formspark. If you're still mapping the landscape, our alternatives page lays out where each tool fits.
If your form only ever needs to reach one inbox and block spam, pick the simplest tool you can and move on. The moment you need routing, attachments over a few megabytes, or email from your own domain, you've outgrown a forwarder and want a full backend. And whatever you choose, don't forget the conversion side — a great backend still needs a form people finish, which is exactly what our 7 reasons people abandon your contact form covers.
Want to try the full-backend end of the spectrum? Start on the free plan, skim the feature overview, and wire up a form in minutes with the docs.
A forwarder takes a submission and emails it to you — that's the whole job. A backend adds spam scoring, conditional routing, file storage, autoresponders, and a searchable record of every submission. You outgrow a forwarder the moment you need routing or attachments.
Only if you have a genuinely custom requirement. Re-implementing spam filtering, email deliverability, retries, storage, and a dashboard is a lot of ongoing maintenance. For most teams, buying is faster and cheaper until a specific need forces a custom build.
Model your real monthly submission volume and read each plan's price at that number — not the free-tier headline. Include overage behaviour and whether features you need (routing, file uploads, custom sending domain) are included or paid add-ons.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.