Launch
Static Forms
Visit
Example Image

Static Forms

Form backend for static sites, without server-side code

Visit

Static Forms is a form backend for static websites and frontend apps. Connect an HTML form to receive submissions by email without maintaining a backend, or use the visual form builder. Spam protection, webhooks, integrations, file uploads and form rules are available depending on the plan. A free plan is available; optional AI Reply requires a paid plan and separate usage credits.

Example Image
Example Image
Example Image
Example Image

Features

HTML form submission API and visual form builder

Email delivery and spam protection

Webhooks and integrations

File uploads and conditional form rules on eligible plans

Optional AI Reply with separate usage credits

Use Cases

Contact forms on static websites

Lead capture for landing pages

Agency client website forms

Routing inquiries to email and connected tools

Comments

Hi Fazier! Static Forms helps developers and agencies collect website inquiries without building a form backend. Keep your own HTML form design, manage submissions in an inbox, and connect your workflow with email, webhooks and integrations. A free plan is available to get started; advanced features depend on the plan. I would love to hear which form workflows you find hardest to manage and which integrations would make your day easier.

custom-img
I'm a web developer and entrepreneur loo...

For agency client sites, handover is the awkward bit: we build the form, then the client wants submissions going to their own inbox and the agency out of the loop. Can a form be moved to the client's own Static Forms account later, keeping its endpoint and submission history, so we don't have to touch the site's HTML at handover?

Does the spam protection work without a CAPTCHA on plain HTML forms? I'm curious how it handles bot submissions on a static site where I can't add server-side checks like a honeypot validation.

custom-img
Building Songprint, an AI music detector...

Solid pick for static sites — the setup friction of a full backend just for a contact form is real. How do you handle spam on the free tier, is there a honeypot or Akismet-style filtering? Also curious about webhook support so submissions can pipe into a CRM or an n8n flow without polling an inbox.

This solves a genuinely annoying problem — spinning up an entire backend just to receive a contact form on a static site is overkill, and the usual workarounds (Google Forms embeds) look terrible on a polished landing page. Two questions: how does the spam protection work on plain HTML forms without a CAPTCHA — honeypot plus rate limiting, or something smarter? And do webhooks fire on the free plan? That's usually the first thing that gets paywalled, so it'd be good to know. Conditional form rules are a nice differentiator, by the way.

The split between a plain HTML-form endpoint and the visual form builder is handy, since you can keep your own markup and still route submissions to email, webhooks and integrations. I like that spam protection is built in rather than left to the developer. Do you plan to offer a per-form submission log export or retention setting on the free plan, for agencies handling many client sites?

Nice that Static Forms offers both a plain HTML form endpoint and a visual form builder, so static-site owners can pick whichever fits. The email delivery with built-in spam protection is a handy way to skip running a backend.

Super handy for static sites. Setting up a backend just to receive contact form emails always felt like overkill. Do webhooks and spam protection come with the free plan, or only on paid tiers?

The dual approach is smart — connecting an existing HTML form for people who already have a site, and a visual builder for those starting from zero covers both audiences. A few questions: how does the spam protection work under the hood (honeypot, CAPTCHA, or filtering on your side), and what does the free plan include for file uploads in terms of size and retention? Also, for webhooks — can a submission trigger multiple endpoints at once, e.g. email plus Slack plus a CRM? The AI Reply feature is intriguing too: does it draft replies for approval, or send them automatically?

The webhooks plus visual form builder combo is handy for static sites. When a webhook delivery fails, does Static Forms retry with backoff and show the failed payload in the inbox, or would I need to catch that on my own endpoint? That decides whether I could rely on it for lead capture.

The agency use case is the strongest fit here — client sites on static hosting rarely justify a maintained backend just for a contact form, and being able to route each site's inquiries to the client's own email rather than the agency's inbox is the detail that matters in practice. Two quick questions: are routing rules set per form, so different client forms can each send to different emails and webhooks? And on plans with file uploads, do uploaded files arrive as email attachments or as download links?

custom-img
Founder of Curalo, a free tool directory...

The conditional form rules and per-plan file uploads stand out for agency work. When a client site's form has file uploads enabled, do the files arrive as email attachments or only as download links in the inbox? It would also help to state on the page which plan unlocks webhooks, since that decides whether a small studio can start on the free tier.

Keeping your own HTML form markup and just pointing the action at your endpoint is the right call for agency client sites. How do the conditional form rules treat a field that a rule hides: is its value dropped from the submission entirely, or sent through empty?

I run a Hugo site on Cloudflare, so a no-backend form is exactly the gap I have. Can I set a custom redirect or thank-you page after submission on the free plan, and where are submissions stored? Is there an EU data region?

The visual form builder alongside a plain HTML submission API is a nice combination for agencies handling many client sites. Could you share how the spam protection works for plain HTML forms, and whether webhooks include retry logic if the receiving endpoint is down?

Having webhooks next to plain email delivery is handy for static sites. For file uploads, is there a per-submission size limit, and are attachments sent in the email or stored in the dashboard?

Premium Products

Comments

Hi Fazier! Static Forms helps developers and agencies collect website inquiries without building a form backend. Keep your own HTML form design, manage submissions in an inbox, and connect your workflow with email, webhooks and integrations. A free plan is available to get started; advanced features depend on the plan. I would love to hear which form workflows you find hardest to manage and which integrations would make your day easier.

custom-img
I'm a web developer and entrepreneur loo...

For agency client sites, handover is the awkward bit: we build the form, then the client wants submissions going to their own inbox and the agency out of the loop. Can a form be moved to the client's own Static Forms account later, keeping its endpoint and submission history, so we don't have to touch the site's HTML at handover?

Does the spam protection work without a CAPTCHA on plain HTML forms? I'm curious how it handles bot submissions on a static site where I can't add server-side checks like a honeypot validation.

custom-img
Building Songprint, an AI music detector...

Solid pick for static sites — the setup friction of a full backend just for a contact form is real. How do you handle spam on the free tier, is there a honeypot or Akismet-style filtering? Also curious about webhook support so submissions can pipe into a CRM or an n8n flow without polling an inbox.

This solves a genuinely annoying problem — spinning up an entire backend just to receive a contact form on a static site is overkill, and the usual workarounds (Google Forms embeds) look terrible on a polished landing page. Two questions: how does the spam protection work on plain HTML forms without a CAPTCHA — honeypot plus rate limiting, or something smarter? And do webhooks fire on the free plan? That's usually the first thing that gets paywalled, so it'd be good to know. Conditional form rules are a nice differentiator, by the way.

The split between a plain HTML-form endpoint and the visual form builder is handy, since you can keep your own markup and still route submissions to email, webhooks and integrations. I like that spam protection is built in rather than left to the developer. Do you plan to offer a per-form submission log export or retention setting on the free plan, for agencies handling many client sites?

Nice that Static Forms offers both a plain HTML form endpoint and a visual form builder, so static-site owners can pick whichever fits. The email delivery with built-in spam protection is a handy way to skip running a backend.

Super handy for static sites. Setting up a backend just to receive contact form emails always felt like overkill. Do webhooks and spam protection come with the free plan, or only on paid tiers?

The dual approach is smart — connecting an existing HTML form for people who already have a site, and a visual builder for those starting from zero covers both audiences. A few questions: how does the spam protection work under the hood (honeypot, CAPTCHA, or filtering on your side), and what does the free plan include for file uploads in terms of size and retention? Also, for webhooks — can a submission trigger multiple endpoints at once, e.g. email plus Slack plus a CRM? The AI Reply feature is intriguing too: does it draft replies for approval, or send them automatically?

The webhooks plus visual form builder combo is handy for static sites. When a webhook delivery fails, does Static Forms retry with backoff and show the failed payload in the inbox, or would I need to catch that on my own endpoint? That decides whether I could rely on it for lead capture.

The agency use case is the strongest fit here — client sites on static hosting rarely justify a maintained backend just for a contact form, and being able to route each site's inquiries to the client's own email rather than the agency's inbox is the detail that matters in practice. Two quick questions: are routing rules set per form, so different client forms can each send to different emails and webhooks? And on plans with file uploads, do uploaded files arrive as email attachments or as download links?

custom-img
Founder of Curalo, a free tool directory...

The conditional form rules and per-plan file uploads stand out for agency work. When a client site's form has file uploads enabled, do the files arrive as email attachments or only as download links in the inbox? It would also help to state on the page which plan unlocks webhooks, since that decides whether a small studio can start on the free tier.

Keeping your own HTML form markup and just pointing the action at your endpoint is the right call for agency client sites. How do the conditional form rules treat a field that a rule hides: is its value dropped from the submission entirely, or sent through empty?

I run a Hugo site on Cloudflare, so a no-backend form is exactly the gap I have. Can I set a custom redirect or thank-you page after submission on the free plan, and where are submissions stored? Is there an EU data region?

The visual form builder alongside a plain HTML submission API is a nice combination for agencies handling many client sites. Could you share how the spam protection works for plain HTML forms, and whether webhooks include retry logic if the receiving endpoint is down?

Having webhooks next to plain email delivery is handy for static sites. For file uploads, is there a per-submission size limit, and are attachments sent in the email or stored in the dashboard?

Premium Products