How to Send HTML Form Data to Email Without a Server

Can you send an HTML form to email without a server?

Yes, but only because someone else runs the server. HTML can't send email, and neither can JavaScript in the browser. What you can do is let the browser POST the form to a hosted form backend that does have mail infrastructure. It saves the submission and emails you a notification, while your own site stays completely static.

The setup is one HTML snippet. Replace YOUR_ACCESS_KEY with your real key from splitforms.com/login:

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
  <!-- Optional: send visitors to your own thank-you page -->
  <input type="hidden" name="redirect" value="https://yoursite.com/thanks" />

  <label>Name <input name="name" required /></label>
  <label>Email <input name="email" type="email" required /></label>
  <label>Message <textarea name="message" required></textarea></label>

  <!-- Honeypot: invisible to humans, filled by bots -->
  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off" />

  <button type="submit">Send</button>
</form>

Paste it into Webflow, WordPress, Next.js, Astro, Carrd, GitHub Pages, Cloudflare Pages, anywhere static HTML lives. When a visitor submits, the message appears in your dashboard and the notification email goes out to your inbox. The hidden redirect field works on every plan: point it at a page on your own site (or a path like /thanks) and visitors land there after submitting.

How do the ways to send a form to email compare?

Every way to get form data into an inbox, including the one that doesn't work. "Own server" means a machine or backend code you have to run and maintain.

How to choose:

• Static site, contact or quote form: a hosted form backend. It's the only option here that needs no server, no JavaScript, and still keeps a copy of every message.
• Already on Netlify and staying there: the host's built-in forms can be enough. See Netlify contact forms without functions for the trade-offs.
• The form is product logic (it writes to your database or needs a logged-in user): write your own function. Do you need a backend for a contact form? covers where that line is.
• Moving off a PHP contact script: see contact forms without PHP and alternatives to PHP mail().
• Weighing a client-side SDK: EmailJS vs a form backend compares the two approaches.

How do you set it up, step by step?

1. Sign up. Go to splitforms.com/login and continue with Google, or enter your email and paste the 6-digit code from your inbox.
2. Copy the access key. Your dashboard shows each form's access key, a long random string. It tells splitforms which form a submission belongs to.
3. Paste the snippet above on your site, replacing YOUR_ACCESS_KEY.
4. Send a test. Open the page, fill in the form and click Send. The submission shows up in your dashboard, and the notification email follows. If it isn't in your inbox, check spam once and mark it as not spam.

That's the whole flow. No webhooks to configure, no SMTP servers to point at, no environment variables to set.

Once it works, the form to email notification settings cover what you can change: the subject line, the sender name, which inbox receives each message, and, on paid plans, CC/BCC and routing by answer.

Why can't HTML or JavaScript send email on their own?

HTML describes a page for the browser to render. Its only networking ability is "request this URL", which is exactly what a form's action does. It has no way to hand a message to a mail server.

JavaScript in the browser can't either. Browsers only allow web traffic (HTTP requests, WebSockets, WebRTC); they don't let a page open the raw TCP connection that SMTP needs on ports 25, 465 or 587. That restriction is deliberate: if any web page could send mail, every site you visited could send spam from your computer.

Libraries that promise "SMTP from JavaScript" get around this by posting your message to their own server, which then sends it. That is still a server, just one you don't control, and if the library asks for your SMTP username and password, those credentials sit in your page source where any visitor can copy them.

So somewhere in the chain there has to be a server that speaks SMTP. The only real question is whether you run it (a PHP host or a serverless function plus an email API) or let a form backend run it for you. For a contact form, a form backend is the shortest path unless you need full control.

How do you send the form from React, Vue or another JavaScript app?

Same endpoint, slightly different syntax. You call fetch() instead of letting the browser submit, and splitforms answers with JSON:

async function onSubmit(e) {
  e.preventDefault();
  const formData = new FormData(e.target);
  formData.append("access_key", "YOUR_ACCESS_KEY");
  const res = await fetch("https://splitforms.com/api/submit", {
    method: "POST",
    body: formData,
  });
  const data = await res.json();
  if (data.success) showSuccessMessage();
}

Your email provider's credentials never appear in this code; only the public access key does. For the full walkthrough see sending form data to email with JavaScript fetch, or a framework guide:

• Next.js contact form
• React contact form
• Vue / Nuxt contact form
• Astro contact form
• Webflow contact form
• WordPress contact form (no plugin)

How do you stop spam without a captcha?

The honeypot field in the snippet above stops a lot of simple bots on its own. Bots tend to fill every input they find; humans never see a display:none input. splitforms silently drops any submission with a filled-in botcheck field, and every plan also applies rate limiting and automatic spam scoring, with suspicious messages held in a Spam folder instead of your inbox.

If a form still attracts spam, add Cloudflare Turnstile or Google reCAPTCHA; both can be turned on per form. See honeypot vs reCAPTCHA and how to stop contact form spam.

Why not just use a mailto: link?

A mailto: link, or a form with action="mailto:you@example.com", asks the browser to open the visitor's default email app with a pre-filled draft. Plenty of visitors don't have one set up, especially on shared or work computers where mail lives in a browser tab, so clicking often does nothing visible. Even when a draft opens, the visitor still has to press Send, and you never learn about the ones who don't.

There's also no saved copy and no spam filtering, and your address sits in the page source for scrapers. Keep mailto: as a secondary "or email us" link next to a real form, not as the form itself.

Can you accept file uploads without a server?

Yes. Add enctype="multipart/form-data" to the form and an <input type="file">. File uploads are a paid feature on splitforms (Pro at $5/month or Annual at $49/year): turn on Storage under your dashboard's integrations, and each submission can carry up to 5 files of 5 MB each. See how to add file uploads to a contact form.

Frequently asked questions

Next steps

• Sign up free: 500 submissions total, no credit card.
• Or read What Is a Form Backend? for the bigger picture.
• Or skip ahead to the 60-second setup guide.
• Emails not arriving? Read why contact form emails go to spam.
• Compare services: top form-to-email services.