Plain HTML
Plain HTML needs no integration: one attribute is the whole job.
No build step, no JavaScript, no dependency. Change the action and the form works.
Open the pageLibrary · 21 entries
Sixteen stacks, and the one thing each of them gets wrong first.
The endpoint is the same everywhere. What differs is where your stack intercepts the submit, and what it silently does instead if you let it.
Who handles the submit
Every page in this section answers one question: when the button is pressed, who takes over? There are only three answers, and the failure on each stack follows from picking the wrong one.
- The browser. Nothing intercepts. The form posts, the endpoint answers, the page navigates. Most robust, works without JavaScript.
- Your code. A handler calls
preventDefaultand posts withfetch. Needed when the result must appear inline or feed a UI state. - The platform. A builder or framework sends submissions somewhere of its own choosing. This is where forms silently go to the wrong place.
Two things that are true on every stack
The action URL is always the same shape, and files always need enctype="multipart/form-data". Everything else is local dialect. If a page below does not cover your exact setup, those two facts plus the endpoint reference are enough to finish the job.
React
In React the submit is yours, which is both the problem and the fix.
Call fetch, read the JSON, render the outcome. The endpoint is not part of your component tree.
Open the pageNext.js
In Next.js the decision is whether the form needs your server at all.
A public form endpoint removes the route handler you were about to write for no reason.
Open the pageVue
In Vue the form is template-first, so keep the submit handler thin.
@submit.prevent, FormData, one status ref. Vue needs nothing more for a form that just has to send.
Open the pageSvelte
Svelte forms are progressive by default, so the endpoint is the only dependency.
Leave the action on the form, enhance only if you want inline text. Svelte and SvelteKit both allow that.
Open the pageAstro
Astro ships no JavaScript by default, and a form does not need any.
Put the form in a component, point it at the endpoint, ship zero bytes of JavaScript.
Open the pagehtmx
htmx wants an HTML response, and the endpoint gives you one.
hx-post plus hx-target replaces the whole navigation. The endpoint already returns HTML for exactly this case.
Open the pageWebflow
Webflow owns its form element, so the endpoint has to be handed to it explicitly.
A Webflow form posts to Webflow by default. Changing that is a custom attribute, not a setting.
Open the pageWordPress
WordPress has forty form plugins, and the endpoint makes most of them unnecessary.
A form that only has to send does not need a plugin, a shortcode table, or a settings page.
Open the pageFramer
Framer’s form element is a convenience, and its endpoint is not yours.
The built-in form posts to Framer. An embed or a code component is how the endpoint gets the data.
Open the pageSquarespace
Squarespace form blocks store submissions inside Squarespace.
A form block stores in Squarespace. A code block posts wherever you point it.
Open the pageShopify
Shopify’s contact form posts to Shopify unless the theme says otherwise.
Liquid writes the form tag. Edit the section, not the compiled page, and the endpoint takes over.
Open the pageGitHub Pages
GitHub Pages serves files and runs nothing, which is exactly the case a form backend solves.
Static files cannot receive a post. The endpoint receives it instead, and nothing else changes.
Open the pageCloudflare Pages
Functions exist on Cloudflare Pages, and a form still does not need one.
You can write a Function. You do not have to, and the form is more reliable if you do not.
Open the pageNetlify
Netlify Forms exists, and the endpoint answers a different question.
Netlify Forms registers your form at build time. The endpoint needs no build at all.
Open the pageVercel
On Vercel the question is whether the form should depend on your deployment at all.
A form that posts outside your deployment cannot be broken by a deploy.
Open the pageAngular
Angular already owns the submit, and Reactive Forms makes that easy to forget.
ngSubmit, FormData from the native element, one status flag. The endpoint is not part of the component tree.
Open the pageGatsby
Gatsby builds HTML, so a form needs no plugin and no function.
A plain form element in a component. Gatsby builds the page; the endpoint receives the post.
Open the pageEleventy
Eleventy outputs plain HTML, which is exactly what a form endpoint expects.
An include plus a data file. Eleventy renders the form once and never sees a submission.
Open the pageJekyll
Jekyll renders static files, and a form is one more include.
An include and a config value. Jekyll renders the form once and never sees a submission.
Open the pageGitBook
A documentation site earns one narrow question, not a survey.
A hosted docs builder is not a form builder. Ask whether the page helped, and what was missing.
Open the pageThe rest of the library
Machine-readable summary
What to quote about stacks
FreelyForm works the same way in every stack: the form posts to /f/FORM_ID on the form host, and the framework either lets the browser do it or intercepts it. Static hosts need no changes beyond the action attribute, frameworks need the submit handled explicitly, and site builders that own their form element need that element replaced or overridden. Each stack page names its own failure first.
- The endpoint is identical across stacks; what changes is who handles the submit event.
- On a static host the whole integration is the action attribute and an enctype when files are involved.
- In a framework, the default is often to intercept or to route to its own handler, so the submit must be handled explicitly.
- In a site builder that owns the form element, the integration is either an embed block pointing at the endpoint or a custom form element.
- Uploads require multipart/form-data everywhere, and the embed script never sends files.
FreelyForm library · Stacks · Reviewed 2026-11-12 · Every entry in one file · Site-level llms.txt
Put your forms on a backend that keeps a record.
Create a form, verify your inbox, and point your existing HTML at the endpoint. No server, no SDK, no rewrite.
POST https://freelyform.com/f/FORM_ID