A form backend is a server-side service that receives HTML form submissions, processes the data, and delivers it to you via email, webhooks, or a dashboard — without requiring you to write any server code.
By Vaibhav Jain · Last updated March 27, 2026
Static websites and JAMstack applications don't have a built-in server to handle form submissions. When a user clicks "Submit" on a contact form, that data needs to go somewhere — a form backend is the service that catches it.
Form backends work by providing you with a unique endpoint URL. You set this URL as your HTML form's action attribute. When a visitor submits the form, the browser sends a POST request to that endpoint, and the form backend takes over: it validates the data, filters spam, stores the submission, and notifies you via email or integrations like Slack.
The primary advantage is speed of implementation. Instead of setting up a Node.js server, configuring a database, writing input validation, building email sending logic, and deploying it all to production, you get a working form endpoint in under a minute. This is especially valuable for marketing sites, portfolios, landing pages, and any project where the form is a small feature rather than the core product.
FormsList, Formspree, Getform, and Basin are examples of form backend services. They differ in pricing, features, integration options, and spam filtering capabilities, but all solve the same fundamental problem: giving static sites a way to handle form submissions.
What is a form backend? A form backend is a hosted server-side service that accepts HTML form submissions over HTTP, processes the incoming data (validation, spam filtering, sanitization), stores it securely, and routes it to the appropriate destination — whether that is an email inbox, a webhook URL, a Slack channel, or a third-party integration like a CRM or spreadsheet. Form backends exist so that frontend developers, designers, and marketers can add fully functional forms to static websites, JAMstack applications, and single-page apps without writing, deploying, or maintaining any server-side code.
The way a form backend works is straightforward. You create a form in the service's dashboard and receive a unique endpoint URL, such as https://formslist.com/f/abc123. You then set this URL as the action attribute on your HTML form element. When a visitor fills out the form and clicks submit, the browser sends a standard HTTP POST request containing the form field data to that endpoint. The form backend receives the request, runs it through spam detection (honeypot checks, CAPTCHA verification, AI-based scoring), validates the fields, stores the submission in a database, and triggers any configured notifications or integrations. The entire flow — from submission to notification — typically completes in under two seconds. Services like FormsList provide a web dashboard where you can view, search, filter, and export all submissions, configure auto-responder emails, set up webhooks, and monitor analytics like submission volume and spam rates.
Form backends are particularly valuable for several categories of projects. Static site generators like Hugo, Jekyll, Gatsby, Eleventy, and Astro produce HTML files with no server runtime, meaning there is no built-in mechanism to process form data. JAMstack sites deployed on platforms like Netlify, Vercel, or Cloudflare Pages face the same limitation. Marketing landing pages built in Webflow, Carrd, or Framer often need a contact or lead capture form but have no backend infrastructure. Even full-stack applications sometimes use form backends for ancillary forms (feedback widgets, support forms) to avoid adding endpoints to the main application. FormsList is designed for all of these scenarios — you can set up a working form endpoint in under 60 seconds, with built-in spam protection, email notifications, webhook forwarding, and a submission management dashboard included on every plan.
A real-world example: a SaaS startup launches a marketing website on Vercel with a "Request a Demo" form. Rather than building an API route, configuring a database, writing email-sending logic, and implementing spam filtering, the team points the form's action URL to their FormsList endpoint. Submissions instantly appear in the FormsList dashboard, trigger email notifications to the sales team, and forward to HubSpot via webhook for lead tracking. The entire integration takes five minutes, with zero server code and zero ongoing maintenance.
A freelance designer adds a contact form to their static portfolio site hosted on Netlify. The form's action URL points to a FormsList endpoint, and submissions arrive via email.
A startup builds a Webflow landing page with an email capture form. The form backend collects email addresses and forwards them to a Google Sheet via integration.
An open-source project adds a feedback form to their docs site. The form backend sends submissions to a Discord channel where maintainers can see user feedback in real time.
Set up your form backend in under a minute. No server required, no complex configuration — just a simple endpoint for your forms.