Contact Forms on a Static Site: Where the Message Goes
A form on a static site posts to an address we run. We check it, email it to you, pass it to your webhook if you have one, and keep nothing.
A static site can’t receive a form by itself. There is no program on the server to read what a visitor typed, because there is no program on the server at all. The form still works: it sends what the visitor wrote to an address we run, and we take it from there.
One message, step by step
The visitor presses Send. Their browser posts the form to
https://api.statichost.uk/f/followed by your form’s ID. It can be a plain HTML form with no script at all. If you’d rather not write the HTML, the form’s Endpoint card in your dashboard gives you a one-line widget or a block of markup to paste.We check where it came from. A form answers only on your site’s primary domain. A copy of your form on someone else’s page gets nowhere.
We check whether a person sent it. With Altcha switched on, the visitor’s browser does a small calculation before the form goes. We also refuse disposable email addresses, limit how often one visitor can send, and drop submissions stuffed with links or written by a bot. Since 27 October, posts from Tor, VPNs and hosting networks are refused too, with a message telling a real visitor what to change (the detail). A dropped submission shows as Spam under Recent Activity on your form.
We email it to you, at the notification address you set for that form.
We send it to your webhook, if you gave one. That is how an enquiry ends up in a CRM, a team chat or an automation without anyone copying it across.
The visitor sees your thank-you page, which must be an https address on your own site, or our default confirmation if you haven’t set one.
Then we forget it. Nothing from the submission is stored on our side. The one exception is a form you have made into a survey, which keeps the answers to your questions and nothing that identifies the person (forms documentation).
Setting one up
In your dashboard, go to Forms and choose Create form. Give it a name and the email address that should receive submissions, and switch on Altcha. Then point your form at the endpoint:
<form action="https://api.statichost.uk/f/your-form-id" method="POST">
<input type="email" name="email" required>
<textarea name="message"></textarea>
<button type="submit">Send</button>
</form>
The forms documentation covers the hidden spam-trap field, styling the widget and dark mode.
What it costs
Every site gets one form and 100 submissions a month, free. The 100 is a soft limit: we never drop a real submission because you went over it, you see a note in your dashboard instead. Forms Plus, at £5 a site a month, raises that to 10 forms and 2,000 submissions a month across them.
Why a static site can’t run this itself is in what a static site is, and when you need something else.
Ready to Deploy?
Join Jamstack developers across the UK hosting their static sites with privacy and performance built in. Hosting is free for good, no credit card needed, with Plus features when you want them.
