Form Backend vs Email Service: Which One Do You Need?

What each one actually does

Form backend (splitforms, Formspree, Getform)

A form backend is a complete submission management platform. It sits between your website form and your inbox. When a visitor submits a form, the form backend:

1. Receives the HTTP POST request
2. Validates the submission (required fields, email format, honeypot)
3. Filters spam using AI classification (on splitforms) or rules-based filters
4. Stores the submission in a database with full metadata (IP, timestamp, user agent)
5. Sends a notification email to you with the submission content
6. Optionally fires webhooks to Slack, Discord, Zapier, or your API
7. Optionally sends autoresponders — a confirmation email back to the submitter
8. Provides a dashboard where you can search, read, export, and manage all submissions

Email service (SendGrid, Mailgun, Postmark, AWS SES)

An email service is a transport layer. It sends emails from your code. You write server-side logic that says "send an email to this address with this content." The email service handles delivery, bounce handling, SPF/DKIM/DMARC, and IP reputation. It does not:

• Receive form submissions (you write that code)
• Validate form data (you write that code)
• Store submissions (you build that database)
• Filter spam (you build that logic)
• Provide a submissions dashboard (you build that UI)

The analogy

Think of it this way: an email service is the postal service — it delivers letters. A form backend is the entire mailroom: it receives incoming letters, sorts them, filters out junk mail, files copies in the cabinet, notifies you when something arrives, and can forward copies to other people.

You wouldn't hire the postal service to run your mailroom. And you wouldn't build a mailroom just to send a few packages. They're different tools for different needs.

When you need a form backend

• You have a contact form, lead form, or signup form on a website
• You want submissions stored and searchable, not just emailed
• You need spam filtering without CAPTCHA friction
• You want webhooks to forward submissions to Slack, Notion, or a CRM
• You want autoresponders (confirmation emails to the submitter)
• Your site is static (no backend server) and you don't want to write one
• You want a dashboard where non-technical team members can review submissions

Choose: splitforms — free 500/month, $1/month Starter, $5/month Pro. Endpoint: https://splitforms.com/api/submit.

When you need an email service

• You're sending transactional emails from an app (password resets, order confirmations, receipts)
• You're sending marketing campaigns or newsletters to a list
• You have a backend server and want programmatic control over email sending
• You're sending thousands of emails per day and need dedicated IP / deliverability consulting
• You need advanced features: A/B testing, drip campaigns, unsubscribe management, bounce webhooks

Choose: SendGrid, Mailgun, Postmark, or AWS SES. Expect $15-90/month depending on volume.

When you need both

Some businesses use both: a form backend for website forms and a separate email service for app emails. Example: a SaaS company uses splitforms for their marketing site's contact and demo-request forms, and uses Postmark for their app's password-reset and notification emails.

Note: splitforms also supports custom SMTP configuration on paid plans. So if you already have a SendGrid or Mailgun account, you can configure splitforms to send notification emails through your existing email service. You get form backend features and use your preferred email provider for delivery.

Feature comparison

The full picture: where each fits in your stack

┌─────────────────────────────────────────────┐
│  Visitor's Browser                          │
│  ┌───────────────────────────────────────┐  │
│  │  HTML Form                            │  │
│  │  action="splitforms.com/api/submit"   │  │
│  └──────────────┬────────────────────────┘  │
└─────────────────┼───────────────────────────┘
                  │ HTTP POST
                  ▼
┌─────────────────────────────────────────────┐
│  Form Backend (splitforms)                  │
│  • Validates fields                         │
│  • Filters spam (AI)                        │
│  • Stores in database                       │
│  • Fires webhooks                           │
│  • Sends notification email ──────────┐     │
└────────────────────────────────────────┼─────┘
                                         │
                    ┌────────────────────▼────────────────────┐
                    │  Email Service (built-in or custom SMTP)│
                    │  • Delivers to your inbox               │
                    │  • Handles bounces, SPF/DKIM            │
                    └─────────────────────────────────────────┘

The form backend usesan email service under the hood. When you use splitforms, email delivery is handled for you. When you use an email service directly, you're responsible for everything above the email layer.

Quick decision guide

• "I have a form on my website and I want submissions in my inbox." → Form backend (splitforms). Done.
• "I need to send order confirmation emails from my app." → Email service (SendGrid / Postmark).
• "I have a form AND I send app emails." → Both. splitforms for forms, email service for app email.
• "I have a form and I want it to use my existing SendGrid account." → splitforms with custom SMTP configured to SendGrid.
• "I want to build everything myself for learning." → Email service + your own backend code. Enjoy!

Still not sure? Email hello@splitforms.comwith your use case and we'll tell you straight whether splitforms is the right fit or you need something else.

FAQ