send.webforms.toRead the docs →

Comparison

The FormSubmit alternative for forms that go more than one place

FormSubmit needs nothing but your email address in the action URL, and has no dashboard, account or pricing page at all. WebForms is what you move to once you need to see, search or route what was submitted.

Start freeSee pricing

FormSubmit is about as minimal as a form backend gets: put your email address directly in the form action, submit once to confirm it, and every submission after that arrives by email. There is no signup, no dashboard and no pricing page, because there is no paid tier - the entire service is free.

That minimalism is also the ceiling. Your email address is visible in your page source unless you use their hashed-endpoint option, there is no stored, searchable record of submissions beyond your inbox, and there is no way to send one submission to more than an email address and a redirect.

WebForms keeps the no-backend setup but replaces the bare email-in-the-URL model with an endpoint, a stored and searchable submission history, fan-out to Slack, Discord, Telegram and webhooks alongside email, and a delivery log for every attempt.

When to stay with FormSubmit

Switching has a real cost. These are the cases where we would not bother.

WebForms vs FormSubmit

Capability by capability, then their published prices. Anything we quote for FormSubmit was read off their own pricing page on the date shown, but prices change - check their pricing directly before deciding.

CapabilityWebFormsFormSubmit
SetupPoint form action at your endpoint. No account required to try it, one to keep data.Put your email directly in the action attribute. No account of any kind.
Submission storageEvery submission stored, searchable and exportable as CSV or JSON.None. The email delivered is the only record.
Destinations per formEmail, Slack, Discord, Telegram and webhooks from one submission.Email only.
Delivery visibilityPer-destination log with status, response and retry history.No dashboard and no delivery log of any kind.
Address privacyYour endpoint contains no personal information.Your email is in the page source unless you generate a hashed endpoint first.
Routing rulesRoute on field values to different destinations per rule.Not offered; there is nowhere to route to but one inbox.
Spam filteringHoneypot, Turnstile, rate limits and an AI classifier that learns from your marks.A honeypot field and captcha option via a special field name.
PricingFree plan, then paid plans as usage grows.Entirely free. No paid tier exists.

Moving from FormSubmit

  1. Create a form and copy the endpoint

    Sign up, add a form, and copy its endpoint URL. Nothing is charged and no card is needed for the free plan.

  2. Swap the action attribute

    Replace your email address in the action URL with your WebForms endpoint. Field names carry over, and any _replyto or _subject style fields you used map to equivalent settings in the dashboard.

  3. Add your destinations

    Add an email destination to match what you had, then add Slack, Discord, Telegram or a webhook if you want them.

  4. Submit once and confirm

    Send a real submission. It appears in the dashboard immediately, so you can confirm the switch before you deploy it everywhere.

Want the field-by-field version? Read the complete FormSubmit migration guide

Try it without deciding anything

The free plan includes 300 submissions a month, unlimited forms, email delivery, stored submissions and spam filtering, with no card required and no expiry. Point one form at it and keep FormSubmit running on the others until you are convinced.

Questions

Close to it. Both are plain HTML form POSTs with no backend, so the change is the action URL. The difference is what happens after: submissions are stored, searchable and fanned out rather than relayed straight to one inbox with no record.

Other comparisons