You have a static site, no server, and a contact page that needs to work by tonight. The fastest-looking answer is a mailto form: one line of HTML and no account to create. The cost shows up later, when a prospect tells you they filled in your form three weeks ago and you never heard from them.
A mailto form is an HTML form whose action attribute is a mailto: address, so the browser hands the field values to the visitor's own email application instead of sending them to a server. That one sentence explains every limitation in this article. SimpleForm, a hosted form backend for static sites, takes the other route: the browser POSTs to an endpoint URL and the service stores the submission and emails you.
What does a mailto form actually do when someone clicks send?
It does not send anything. The browser reads the mailto: URI, which the IETF defines in RFC 6068, and asks the operating system to open whichever program is registered as the default mail handler. That program opens a draft, and the visitor still has to press send from their own account.
Here is the typical markup:
<form action="mailto:you@example.com" method="post" enctype="text/plain">
<input name="name">
<textarea name="message"></textarea>
<button type="submit">Send</button>
</form>Your page never learns whether the draft was sent, edited, or abandoned. There is no success state you can show, because the browser has no response to read.
Where do mailto form messages get lost?
They get lost at every hand-off between the click and your inbox. Each step below depends on the visitor's device, not on your site, so you cannot fix any of them from your side.
- The visitor has no desktop mail client configured, which is common for people who only use webmail, so the click opens nothing or opens an unrelated app.
- The mail app opens a draft and the visitor closes it, because a blank compose window looks like the form failed.
- The visitor is on a locked-down work machine where the mailto handler is disabled.
- The draft arrives with the field values mangled, because plain-text encoding does not cope well with line breaks and non-ASCII characters in every client.
- The message is sent from the visitor's personal address, so it can land in your spam folder or be blocked by a corporate filter.
The pattern is the worst kind of failure: silent. You see no error in logs, because no request reached a server, and the visitor assumes you ignored them.
How does a form backend differ from a mailto form?
A form backend receives the submission over HTTP, so the data reaches a system you control before any email client is involved. With SimpleForm you set the form's action to your endpoint URL, and each submission is stored in the dashboard and emailed to you. The visitor never needs a mail app, and your page gets a real response code back.
| Question | Mailto form | Form backend |
|---|---|---|
| Who sends the email? | The visitor, from their mail app | The service, on submit |
| Works without a mail client? | No | Yes |
| Do you get a stored copy? | Only if the visitor sends it | Yes, in the dashboard |
| Can the page show a success message? | No response to read | Yes, via status code or redirect |
| Spam filtering | None | Honeypot and rate limiting |
| Setup effort | One attribute | One attribute plus an endpoint URL |
The setup effort is the only row where mailto wins, and the gap is one URL. Everything else favours the backend.
Is a mailto form ever the right choice?
Yes, in a narrow set of cases: a throwaway prototype, an internal page where every visitor uses the same mail client, or a plain mailto link that someone clicks on purpose to email you. In those cases the visitor expects an email draft and understands what is happening.
It stops being the right choice once a stranger needs to reach you and you cannot afford to lose the message. A pricing enquiry, a support request, or a job application should not depend on whether the sender has Outlook installed.
There is also an exposure issue. Writing your address into the HTML hands it to every scraper that crawls the page. With a backend, recipients are configured in your dashboard rather than printed in your markup. The free plan includes one email recipient, and Pro includes five, as listed on the pricing page.
What does the switch look like in practice?
The change is small, and you keep your existing fields. Replace the mailto action with your endpoint URL, change the method to POST, and remove the text/plain encoding so the browser sends normal form data. SimpleForm accepts URL-encoded posts, multipart forms and JSON.
<form action="https://simpleform.dev/f/YOUR_TOKEN" method="POST">
<input name="name" required>
<input name="email" type="email" required>
<textarea name="message" required></textarea>
<button type="submit">Send</button>
</form>This is the point where doing it by hand gets tedious: if you replace mailto with your own server code you take on mail delivery, spam handling, storage and uptime. A hosted endpoint covers those, and the SimpleForm documentation lists the response codes and the options for redirects and JSON responses.
What spam and abuse protection do you get?
With mailto you get none, because there is no server in the path to apply it. Anyone can read your address from the page source and email it directly, and a bot can do the same at volume.
On SimpleForm every plan includes a hidden honeypot field and IP-based rate limiting, at a maximum of 10 submissions per IP per hour per endpoint. Pro and Agency plans add optional Google reCAPTCHA v3 with your own site key. Blocked automated posts do not use up your inbox, and the honeypot responds with a 200 so bots get no signal that they were caught.
Will a form backend cost more than a mailto form?
A mailto form is free, and a backend does not have to cost anything for a small site. The Free plan includes 100 submissions per month, 3 forms and 7 days of submission history, with no credit card required. If you go over the monthly limit, extra submissions return a 402 response and are not stored, so check the volume you expect before you launch.
The honest counter-argument is dependence on a third party: your form now relies on someone else's endpoint. That is a fair trade-off. You can export submissions as CSV or JSON on paid plans, and because the form is plain HTML pointing at a URL, moving to another backend later means changing one attribute.
What should you do next?
Replace the mailto action on your most important form today. Create a free endpoint, paste its URL into the form's action, and send yourself a test message. It takes a few minutes, and you will see the submission in your dashboard and inbox straight away. Create your free SimpleForm endpoint and put the first test message through.
Frequently asked questions
No. A mailto form relies on the visitor's device having a default mail application registered. If the visitor uses only webmail or the handler is disabled, the click opens nothing useful and no message is created. Your site never receives an error, so the lost message stays invisible to you.
No. The browser only opens a draft in the visitor's mail app, and the visitor must press send themselves. Browsers deliberately block silent sending for privacy reasons. If you need submissions delivered without that extra step, the form has to POST to a server or a hosted form backend.
It is visible to anyone who views the page source, including scrapers that harvest addresses for spam lists. A form backend avoids this because recipients are set in a dashboard rather than printed in your HTML. If you must use mailto, expect more unsolicited email over time.
Change the form's action from the mailto address to your endpoint URL, set the method to POST, and remove the text/plain enctype. Keep your existing field names. With SimpleForm you create an endpoint after signing up, paste its URL into the action attribute, and submit a test entry to confirm delivery.
Yes, for low volume. SimpleForm's Free plan includes 100 submissions per month, 3 forms and 7 days of submission history, and it does not require a credit card. Submissions above the monthly limit return a 402 response and are not stored, so higher-traffic sites should look at a paid plan.