HTML to email
Send an HTML form to email without backend code
If the goal is simple email alerts from an HTML form, you still need a reliable form backend between the browser and the mailbox. Formserve receives the submission, blocks obvious spam, stores the entry, and emails the right people.
§ 01 · Overview What you get
Inbox plus email
Email is useful, but it should not be the only place the lead exists. Formserve stores the submission and then sends the notification.
Reduce spam before it hits your team
Use allowed domains, honeypot fields, rate limits, and blocklists before the email is sent.
Route later if needed
Start with email-only and add Slack, webhooks, Sheets, or CRM delivery later without changing the form.
§ 02 · Context Why HTML-to-email still needs a backend
Browsers cannot safely send email directly on their own. You need a server-side destination to receive the form and decide what to do next.
Formserve acts as that destination. The form POSTs to an endpoint URL, the submission is stored, and then email notifications are sent according to the endpoint settings.
This is a safer and more maintainable replacement for fragile mailto patterns or one-off scripts.
§ 03 · Context Better than relying on email alone
Every submission stays searchable in the Formserve inbox.
Delivery failures remain visible instead of disappearing into email logs.
You can later add auto-responders, exports, or integrations without reworking the form implementation.
§ 04 · Context Why mailto and one-off scripts break
The classic shortcut is a `mailto:` link or a form with a `mailto:` action. It opens the visitor's own email client, depends on them having one configured, drops all the form data if they do not, and never stores anything on your side. Most visitors simply abandon it.
The next shortcut is a hand-written PHP or serverless script that calls an SMTP server. It works until the mail provider flags it, the credentials rotate, the host changes, or a bad input crashes it — and because nothing is stored, you cannot tell how many leads were lost. Every one of those failure modes is silent.
A form backend removes both problems. The submission is stored the instant it arrives, the notification email is a delivery on top of that stored record, and if the email bounces the lead is still safe in the inbox with the failure visible. You get the simplicity of "send it to my email" without betting the lead on email actually arriving.
§ 05 · Setup How to connect it
§ 06 · Example Keep the form simple
<form action="https://formserve.io/f/YOUR_ENDPOINT_KEY" method="POST">
<input type="text" name="_honeypot" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px" />
<input type="email" name="email" required />
<textarea name="message" required></textarea>
<button type="submit">Send</button>
</form>