Netlify Forms alternative
Netlify Forms is convenient if your site is already hosted on Netlify - but that's also its ceiling. Formpaste is a form endpoint that works on any host, with copy-paste components for HTML, React, TypeScript, JavaScript, and Astro, a quarantine folder you control, and an MCP server your AI agent can drive.
Formpaste vs Netlify Forms
| Feature | Formpaste | Netlify Forms |
|---|---|---|
| No backend or server required | Yes - POST to /submit | Yes - but only on sites hosted on Netlify |
| Works off-platform (any host) | Yes - any host, any framework | No - Netlify-hosted sites only |
| Framework components | 5 (HTML, Astro, React, TS, JS + CSS, Tailwind) | 0 - a form attribute, not a component |
| React/SPA forms | POST straight from your component, no extra markup | Needs a hidden static HTML form with every field, or a manual form-name hidden input, so the build-time parser can detect it |
| Automatic spam handling | Yes - heuristics + quarantine | Akismet on every submission, plus optional honeypot and reCAPTCHA 2 |
| Quarantine folder you review | Yes | Yes - a Spam submissions list, and you can flip a submission to verified |
| Copy-paste components | HTML, React, TypeScript, JavaScript, Astro | None - a form attribute and a hidden input |
| AI agent setup (MCP) | Yes | No |
| File uploads, webhooks, autoresponder | Yes | File uploads and webhooks yes; no autoresponder |
| No email server / DNS / MX records | Yes | Yes |
| Reply-to goes to the submitter | Yes - reply straight from your inbox | Yes - if your form includes a field named email |
| Free plan | 250 / month | Unlimited / month |
| Paid plans (from) | $9.99 / month | $9 / month |
Netlify Forms pricing verified July 2026. Check their pricing page for current numbers.
How it works
Three steps from sign-up to form submissions landing in your inbox.
Create Your Form
Sign up for an account. Verify your email and create an access key in your dashboard.
Create Contact Form
Add the code snippet using your favourite language to create the form.
<form action="https://api.formpaste.com/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_ACCESS_KEY_HERE">
<input type="email" name="email" placeholder="Your email" required>
<textarea name="message" placeholder="Your message" required></textarea>
<button type="submit">Send</button>
</form>Add Access Key
Replace with your access key to start receiving email submissions.
<input type="hidden" name="access_key" value="YOUR_ACCESS_KEY_HERE">Why switch from Netlify Forms?
Works on any host
Netlify Forms only works if your site is deployed on Netlify. Formpaste is a plain POST endpoint that works from any host, any static site, any framework.
No static-HTML blueprint required
Netlify's form detection parses your built HTML at deploy time, so JavaScript-rendered forms need a hidden static duplicate with every field present. Formpaste just needs a POST - no build-time detection step.
First-class components
Copy-paste form components for HTML, React, TypeScript, JavaScript, and Astro - with a live preview per template, instead of hand-wiring `data-netlify` attributes.
Common Netlify Forms issues Formpaste solves
Your form only works because your site happens to be on Netlify
Formpaste is a plain POST endpoint that works from any host - move your site later and your form keeps working.
React or Vue forms need a hidden static HTML duplicate just so Netlify's build step can detect the fields
Formpaste POSTs straight from your component. There's no build-time HTML parser to satisfy and no field list to keep in sync.
Wiring the form attribute and hidden inputs by hand for every framework
Copy-paste components for HTML, React, TypeScript, JavaScript, and Astro come pre-wired, with a live preview per template.
Your AI coding agent can't set the form up for you
An MCP server lets Claude Code, Cursor, or Codex create the form and return a wired snippet on the first try.
No way to auto-reply to submitters without wiring your own email flow
Formpaste supports autoresponders out of the box, so a submitter gets a reply without you building that yourself.
Why people leave Netlify Forms
Netlify Forms works well for the exact case it’s built for: a static or Jamstack site deployed on Netlify. The catch is in that last part. Netlify detects forms by parsing your built HTML at deploy time, so the moment your form is rendered by JavaScript - a React component, a Vue app, anything client-side - the fields aren’t in the static HTML Netlify’s build step actually sees. The workaround is a hidden duplicate form with every field present, or manually adding a hidden form-name input and hoping the field list never drifts out of sync with your real form. It’s a genuine tax on React and SPA users that a plain HTML site never pays. The bigger constraint is host lock-in: Netlify Forms only works because your site is deployed on Netlify. Move your site to Vercel, Cloudflare Pages, or your own server, and the form stops working entirely. Formpaste has no such dependency - it’s a POST endpoint that works the same way regardless of where your site lives.
Migrating from Netlify Forms
Switching takes a few minutes. Point your form’s action at https://api.formpaste.com/submit, add a hidden access_key input with the key from your dashboard, and remove the data-netlify attribute along with the hidden form-name input Netlify relies on. If you were maintaining a separate static HTML duplicate of a JavaScript-rendered form purely to satisfy Netlify’s build-time form detection, you can delete it - Formpaste accepts a POST from any rendering path, static or client-side, with no build step involved. Your existing field names keep working as-is.
Who should switch - and who shouldn’t
Switch if your site isn’t on Netlify, if you’re tired of maintaining a hidden static form just to keep a React or Vue form working, or if you want copy-paste components, a quarantine folder for false positives, or an MCP server so an AI coding agent can wire the form up for you. If your site is firmly on Netlify and your forms are simple static HTML with no SPA rendering involved, Netlify Forms’ build-time detection is a non-issue for you, and switching buys you components and MCP setup rather than solving an active pain point - worth weighing against the migration effort.
Netlify Forms alternative FAQ
Paste a form. Get submissions.
Instantly without setting up any backend, servers or databases. 250 submissions/mo free - no credit card.
What you get with Formpaste
No server, no DNS
Point your form at Formpaste - no backend, no DNS, no email server to run.
Spam filtered automatically
Heuristics + a quarantine folder you control. Real messages always get through.
Quarantine you control
Suspicious submissions land in a folder you review - nothing silently dropped.
Built for AI agents
An MCP server your coding agent calls to create a form and wire it up.
Copy-paste components
Accessible, copy-paste form code for HTML, React, TypeScript, JavaScript, and Astro.
Simple dashboard
Manage forms, inbox, quarantine, and delivery from one place.