Add a working form to a static site without a backend. Submissions are forwarded to your email (and, if you set one, to a webhook), spam-filtered with Altcha. We relay submissions and never store the form data, unless you make the form a survey.
Set up a form (free)
- In your dashboard, go to Forms and click Create form.
- Give it a name and the notification email that should receive submissions.
- (Optional) Set a webhook URL to send each submission to your other tools (CRM, Slack, Zapier and so on), a thank-you redirect URL, which must be https and on one of your site’s own addresses, and turn on Altcha spam protection.
- Point your HTML form at the endpoint shown:
<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>
That’s it. On submit, you get an email; the visitor sees your thank-you page or a default confirmation.
Your form works only on your site’s primary domain, the one marked primary under Domains. A submission from any other address is refused. Your other domains redirect to the primary one, so visitors end up there anyway.

The free tier includes one form and up to 100 submissions per month. Going over is a soft limit: we never drop a submission, you’ll just see a usage nudge.
Spam filtering
Every form, free or Plus, is filtered before anything reaches you. Turning on Altcha in the form’s settings adds a captcha with no puzzle and no tracking. On top of that, we refuse disposable email addresses, limit how often one visitor can submit, and drop submissions stuffed with links or written by a bot rather than a person.
You can also add a hidden field that people never see and bots fill in. Name it _gotcha and leave it empty:
<input type="text" name="_gotcha" style="display:none" tabindex="-1" autocomplete="off">
A submission with that field filled in is dropped. To use a different name, change Honeypot field name in the form’s settings. The widget and the HTML shown under Endpoint already include it.
A dropped submission shows as Spam under Recent Activity on your form. In most cases the sender sees your normal thank-you page, so a bot can’t tell it was caught.
Surveys
A form can keep its answers, so you can see the results, compare them and export them. This is the one case where we store anything from a submission, and we store only the answers to the questions you define. Nothing that identifies a person is kept.
To make a form a survey:
- Open the form and go to Survey.
- Tick Keep answers.
- Under Questions, click Add question for each question. Pick Single choice, Multiple choice or Scale 1 to 5. A choice question can Allow “Other”. Each question’s name must match the
nameof its input on your page. - Save.
The simplest way to get a matching form onto your page is the widget or the HTML shown under Endpoint, which draw your questions for you.
What we keep:
- The answer to each question you defined, with the date it arrived. We keep no time of day, so an answer can’t be matched to the email that came in with it.
- “Other” is kept as “Other”. Anything typed next to it goes to your email only.
- Names, email addresses, comments and consent ticks go to your email and webhook, as on any form, and are never stored.
View results on the form shows each question as a bar chart and lists every response. You can delete one response or all of them, and export them as CSV, JSON or a PDF of the results.
Give several forms the same Group, for example one form per event, to see their answers pooled and how each event compares.
Tick Publish a summary to let your site fetch the totals and averages and show them. A summary shows nothing until there are 5 responses, so no one person’s answers can be read from it. Like the form, it answers only on your primary domain.
Survey answers count towards your monthly submissions. One address can send a survey up to 30 times an hour, so a shared tablet at an event keeps working. If your survey is public, turn on Altcha so a script can’t fill it in over and over.
Embedding and styling
The Endpoint card on a form gives you two ways to put it on a page. Both draw your questions for you, send the spam token, show the thank-you and, on a survey with a published summary, the average score.
- Widget: one script tag. It picks up changed questions within five minutes.
- HTML: the same form as a block of markup you paste and own. Paste it again after changing the questions.
<script src="https://api.statichost.uk/f/your-form-id/widget.js"></script>
The default look
The form takes your page’s font and text colour, and draws borders, hints and empty stars from that colour. It never paints its own background, so it sits on a light page or a dark one without a setting. The accent colour on the button, ticks and focus rings is set under Settings on the form, or on the tag:
<script src="https://api.statichost.uk/f/your-form-id/widget.js" data-color="#0f766e"></script>
Dark mode
The form follows your page’s colour scheme. A page that declares color-scheme: light dark in its CSS switches with the visitor’s setting, and the form switches with it. The accent tones lighten and the filled stars turn amber. The browser also draws the form’s own controls, such as checkboxes, in their dark form. A page that declares nothing stays light, whatever the visitor’s setting, because the form cannot know your page’s background.
If your site switches to dark with a class on the page instead, pin the form yourself:
<script src="https://api.statichost.uk/f/your-form-id/widget.js" data-theme="dark"></script>
data-theme takes light or dark. On the pasted HTML it is the data-theme attribute on the <form> tag, and the dashboard’s Scheme picker writes it for you.
Override one thing
Every element carries a class beginning shf-. Our stylesheet sits in a CSS layer, so any rule in your own stylesheet wins over it with no !important:
.shf-btn { background: #b91c1c; border-radius: 999px; }
.shf-opt { border-radius: 4px; }
The classes:
| Class | What it is |
|---|---|
shf | the form itself; also the thank-you box that replaces it |
shf-q | one question (a fieldset with a legend) |
shf-hint | the “Choose up to 3” line under a question |
shf-opts, shf-opt | a choice list and one choice in it (a label around its input) |
shf-other | the text box that appears next to “Other” |
shf-stars | the 1 to 5 scale: five hidden radio buttons, each with a star label |
shf-consent-row, shf-consent, shf-contact | the “You can contact me” row, its tick, and the name and email it reveals |
shf-field | a label above a text box |
shf-btn | the send button |
shf-status | the “Sending…” and error line under the button |
shf-thanks, shf-note, shf-score, shf-score-stars | the thank-you box, the preview note, the score line and its stars |
Plain HTML, your styles
Tick Plain HTML, no styles on the Endpoint card, or add data-style="none" to the tag, and the form arrives with no stylesheet beyond what hides the spam trap and reveals the contact fields. The classes stay as hooks. The scale becomes five labelled radio buttons, lowest first, so your own form styles cover everything:
<script src="https://api.statichost.uk/f/your-form-id/widget.js" data-style="none"></script>
form.shf { max-width: 480px; }
.shf-opt { display: block; margin: 4px 0; }
.shf-btn { background: #b58900; color: #fff; border: 0; padding: 8px 16px; }
With the pasted HTML, the plain copy is what the card shows while the box is ticked. After a submit, the average score is shown as text, with no star graphic to style.
Tag attributes
| Attribute | Values | What it does |
|---|---|---|
data-color | #rrggbb | the accent, overriding the form’s setting |
data-button | text | the button’s label |
data-theme | light, dark | pins the colour scheme; unset follows the page |
data-style | none | no stylesheet, classes kept |
Forms Plus
Upgrade a site to Forms Plus for:
- Up to 10 forms on one site (contact, signups, enquiries and more).
- Up to 2,000 submissions per month across all your forms.
See Forms on the features page for the overview.