Contact forms for static sites

Any host that serves your site as files. The form is ordinary HTML in your pages, and the browser posts it straight to formboost.app, so the host is never involved in the submission. Some of these hosts can also run functions; a contact form does not need one.

A generator builds the same kind of folder of files, so the form is the same everywhere — what changes is where you put it. Each guide shows the idiomatic place in that generator:

• •Jekyll — in a page or an _includes partial; the endpoint can live in _config.yml.
• •Astro — in an .astro component, as plain HTML or with a small script.
• •Eleventy — in a template or include.
• •Gatsby — a React component posting with fetch().
• •Next.js static export — plain HTML or fetch(); Server Actions need a server, so a static export cannot use them.
• •Hugo — put the form in a partial under layouts/partials/ and include it where you need it; the HTML is exactly the example above.

A plain HTML form is answered with a redirect. By default that is Formboost's thank-you page; add a hidden _redirect field and it is yours. The address must be https:// and on the same site as the page the form is on (the host must match exactly, so www. counts) — that rule is what stops anyone using the endpoint to send people to a site of their choosing.

Two consequences on static hosts. Testing from localhost lands on Formboost's page, because localhost is not your site. And preview deployments — a pull-request preview on Netlify, Vercel or Cloudflare Pages — have their own address, so a _redirect that names your production domain falls back there too. On the live domain it works. If you want previews to redirect as well, set the field from the page itself:

<input type="hidden" name="_redirect" id="redirect">
<script>
  document.getElementById("redirect").value = location.origin + "/thanks.html";
</script>

Plain HTML needs no JavaScript and works on every host and every builder. If you would rather keep the visitor on the page, submit with fetch(): send the fields as JSON with Accept: application/json and you get a 202 back instead of a redirect. Do not pass new FormData(form) straight to fetch() — that sends a multipart body, which the endpoint refuses with 415. The HTML form generator writes either version for you.

A form on a static site has the same visible endpoint as any other form, so spam protection happens on Formboost's side, with no CAPTCHA for your visitors:

• •A hidden _honey field catches bots that fill in every input. The submission is kept, marked as spam, and never forwarded.
• •Every submission is screened: heuristics on the Free plan, with AI deciding the borderline cases on Starter and reading every submission on Pro and above — how it works.
• •Each IP address is rate-limited, so a script cannot flood your inbox.

10 forms and 500 submissions a month, email notifications, and one Slack, Discord or Telegram destination per form — no card and no expiry. Submissions are stored in your dashboard and export to CSV. Webhooks, Google Sheets, Zapier, n8n and Auto Reply start on Starter. The form accepts text, choices, dates and links; it does not take file uploads.