Registration Form in HTML — Working Code for 2026

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
  <input type="hidden" name="_subject"   value="New registration" />
  <input type="hidden" name="redirect"   value="https://yoursite.com/welcome" />

  <label>
    Full name
    <input name="name" type="text" required minlength="2" autocomplete="name" />
  </label>

  <label>
    Email
    <input name="email" type="email" required autocomplete="email" />
  </label>

  <label>
    Password
    <input name="password" type="password" required minlength="8"
           autocomplete="new-password" />
  </label>

  <label>
    Confirm password
    <input name="password_confirm" type="password" required minlength="8"
           autocomplete="new-password" />
  </label>

  <label>
    <input type="checkbox" name="agree_terms" required />
    I agree to the <a href="/terms">terms of service</a>
  </label>

  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" />
  <button type="submit">Create account</button>
</form>

A registration form is a contact form with stricter validation rules. Same `<form>` wrapper, same submit mechanics, but every field has more requirements: passwords must be a minimum length, emails must be unique, terms must be accepted. Most of the validation work happens server-side (on your backend) — the HTML's job is to fail loudly on obvious mistakes before the user even submits.

The form above uses every native validation primitive: `required` for mandatory fields, `type="email"` for email format checking, `minlength="8"` for password length, the terms checkbox uses `required` so the user can't submit without agreeing. Modern browsers show inline error messages automatically — no JavaScript needed for the baseline.

Password confirmation is the one case where native HTML falls short. There's no `equalTo` attribute, so you need ~5 lines of JavaScript to compare the two password fields and show an error if they don't match. The snippet for that is in the alternative-code section below.

The form POSTs to splitforms's `/api/submit` endpoint. splitforms emails you the registration, stores it permanently, and fires webhooks. If you're building a real registration system (where users actually log in), you'll want a database-backed signup flow — use splitforms for the lead-capture form, then write users to your auth provider via a webhook handler.

const form = document.querySelector("form");
const password = form.querySelector("[name=password]");
const confirm = form.querySelector("[name=password_confirm]");

confirm.addEventListener("input", () => {
  confirm.setCustomValidity(
    confirm.value === password.value ? "" : "Passwords don't match"
  );
});

Native validation, password-match in 5 lines of JS, splitforms backend.