Use semantic HTML
Every input has a <label> with `for` matching the input's id. Inputs use native types: text, email, tel, url. Required fields have `required`. The button is `<button type="submit">`, not a div with onclick.
Form template · Basic contact form
A working HTML contact form with no CSS, no JavaScript, no framework — just semantic markup and an action URL. Use as a starting point or for accessibility audits.
Every template is free and fully editable in the drag-drop builder — swap fields, colors, and the button label before you publish.
No server, API route, or SDK — your Raw HTML Contact Form posts straight to one endpoint.
Every submission is emailed to you and saved to a searchable dashboard — spam filtered before it reaches you.
It's plain HTML you own — paste the Raw HTML Contact Form snippet, swap in your access key, and ship.
Copy and ship
HTML by default — the same field set also renders as React, Next.js, PHP, and cURL in your dashboard. Every variant posts to the same /api/submit endpoint. Replace YOUR_ACCESS_KEY with the key from your dashboard; that's the only edit.
<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 contact form submission">
<label for="name">Full name *</label>
<input id="name" type="text" name="name" placeholder="Jane Builder" required>
<label for="email">Email *</label>
<input id="email" type="email" name="email" placeholder="jane@example.com" required>
<label for="phone">Phone *</label>
<input id="phone" type="tel" name="phone" placeholder="+1 415 555 0142" required>
<label for="message">Message *</label>
<textarea id="message" name="message" placeholder="How can we help?" required></textarea>
<!-- honeypot — bots fill every field -->
<input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
<button type="submit">Send</button>
</form><p class="splitforms-attribution" style="margin-top:12px;font-size:11px;color:#888;text-align:right">
Powered by <a href="https://splitforms.com" style="color:#888;text-decoration:none" target="_blank" rel="sponsored noopener">splitforms</a>
</p>How to add it
To add a Raw HTML Contact Form to your site you need three things: a free splitforms access key, the HTML snippet above, and your key pasted into it. No backend, database, or CAPTCHA library — the form posts to one URL and every submission lands in your inbox and dashboard.
Every input has a <label> with `for` matching the input's id. Inputs use native types: text, email, tel, url. Required fields have `required`. The button is `<button type="submit">`, not a div with onclick.
Set `action="https://splitforms.com/api/submit"` and `method="POST"`. The form works as plain HTML — no JavaScript, no fetch, no AJAX.
Once the bare HTML is correct, add CSS. Tailwind, plain CSS, CSS-in-JS — all of them work because the markup is semantic.
What's included
Most contact-form tutorials front-load CSS and JavaScript before the underlying HTML is correct. The bare-HTML version is the right starting point — semantic <label> + <input> pairs, native validation attributes, a real <button type="submit">. Style it later. The raw version is also useful for accessibility audits — if it works with no CSS, your form is structurally sound. Semantic HTML, zero CSS, zero JavaScript — the right starting point.

Where submissions go
Reply-to is wired to the visitor's email, so one tap on Reply answers them directly — while the built-in honeypot and spam classifier filter out bots before they reach you. Every submission is emailed to your inbox and can forward to a webhook or Slack the moment a visitor hits send.

How SplitForms works
Connect your form, collect every submission, and send data where it needs to go — without building backend infrastructure.

Point your form to your unique SplitForms endpoint. That's it.

We instantly capture and organize every submission in your inbox.

Send data to email, spreadsheets, CRMs, webhooks, and 7,000+ apps.

No credit card required. Set up in under 60 seconds.
Connect & automate
SplitForms works with the destinations you route to and the platforms you build on — from Slack and Sheets to WordPress, Shopify, and Next.js.

Trusted by indie teams and agencies shipping forms worldwide
Testimonials
40 quotes on record — from indie hacks to agency migrations.
“I replaced a Lambda + DynamoDB + SES contact form with six lines of HTML. It took eleven minutes, and the dashboard is better than what I was going to build.”
“We migrated 14 client sites off Formspree in a single weekend. The price is a third of what we paid, the API is more honest, and the spam filter actually works.”
“The webhook payload is signed, idempotent, and well-shaped. It reads like code from a competent team, not a CRUD app held together with duct tape.”
“I stopped reaching for Typeform on small marketing sites. splitforms covers 90% of the use case at none of the bloat.”
“I onboarded our whole agency in an afternoon. The MCP integration meant Cursor literally dropped the form straight into our client repos for us.”
“The free plan gave me 500 submissions before I paid a cent, and Pro is five dollars a month. I've spent more on coffee deciding which backend to use.”
“Spam went from forty junk entries a day to zero, with no reCAPTCHA puzzle ruining the form. The honeypot and time-trap just quietly do their job.”
“Point the form action at one endpoint and you're done. No SDK, no client library, no build step. This is how a form backend should feel.”
“Leads land in Slack the second someone submits, and a copy goes to Google Sheets for the sales team. I wired both up in under ten minutes.”
“I run a static Hugo site on a five-dollar VPS. splitforms gave it a real contact form without me standing up a single server.”
Questions
Three reasons. (1) Forms must work without JavaScript — progressive enhancement starts from a working baseline. (2) Accessibility is structural — if the bare HTML isn't right, no amount of ARIA fixes it. (3) Debugging is easier — when you can see the form working without styling, you know any later issues are visual, not behavioral.
Yes. Plain <form action method=POST> has worked in every browser since Mosaic. Modern attributes (required, type=email) gracefully degrade in browsers that don't support them — the form still submits, just without native validation.
Use `type="email"` on the input. Modern browsers validate the format natively (must contain @, must have a TLD). For more strict validation, splitforms validates server-side anyway and rejects malformed addresses.
Yes — CSS doesn't change HTML semantics. Style the form however you want; the labels still associate with inputs, the button still submits, the validation still fires.
Simple pricing
Choose a plan that fits your workflow — from a free form endpoint to full automations, exports, and higher submission limits.
Free forever
For side projects and indie devs.
For agencies and growing products.
Pay $59. 3 years sorted.
No credit card required on Free • Cancel anytime