Keep your form backend independent from your hosting provider. Form Plume works across static hosts, frontend frameworks, site builders, and future migrations—with uploads, a real inbox, and one signed webhook included on Free.
Side by side
Netlify Forms is a hosting-native feature, while Form Plume is a standalone form backend. The practical choice is less about HTML syntax and more about portability, framework setup, upload constraints, retention, and whether form operations should follow your host.
| Decision point | Form Plume | Netlify Forms |
|---|---|---|
| Hosting portability | Works with any host or frontend stack Point HTML, React, Next.js, Webflow, or another client at one endpoint. | Native to a Netlify project and deploy Netlify scans a site's deployed HTML after form detection is enabled. |
| Free form submissions | 500 / month Unlimited forms with a dedicated form-service allowance. | Free and unlimited on credit-based plans Netlify stopped charging credits per form submission in April 2026. |
| Paid-plan context | $12 / month for a form backend 10,000 submissions, unlimited forms, integrations, and API access. | $9 Personal · $20 Pro Site-wide plans bundle deploy, bandwidth, compute, request, and collaboration credits. |
| Framework and runtime forms | Submit directly from rendered forms No build-time form discovery or duplicate static form definition is required. | Static form definition required Runtime-rendered framework forms may need a static HTML blueprint and AJAX submission. |
| File uploads | 10 files · 10 MB per file 100 MB on Free and 10 GB on Pro. | 8 MB maximum form request One file per upload field; uploads time out after 30 seconds. |
| Spam protection | Layered controls with recoverable quarantine Four CAPTCHA options, domain controls, rate limits, blocklists, and adaptive scoring. | Akismet, honeypot, and reCAPTCHA 2 Akismet spam is reviewable; honeypot and CAPTCHA failures are rejected. |
| Automation and delivery | 1 signed webhook on Free Pro adds unlimited signed webhooks, native apps, Zapier, Make, and MindCloud. | Email, HTTP POST, Slack, Zapier, and n8n Verified submissions can also invoke a hosting-native Netlify Function. |
| Inbox, API, and retention | 60 days on Free · 2 years on Pro Searchable inbox, explicit retention windows, CSV export, and API access by plan. | Forms UI, CSV export, and API Submissions remain user-managed; Netlify recommends regular export and deletion for PII. |
Where Form Plume pulls ahead
Netlify's build-time integration feels effortless on a compatible static deployment. Form Plume removes that hosting dependency, so the same endpoint workflow survives a framework change, a platform migration, or a portfolio of client sites on different infrastructure.
A standalone Form Plume endpoint can receive submissions from Netlify, Vercel, Cloudflare Pages, traditional hosting, Webflow, or a local application without moving the site or reproducing a hosting-specific form configuration.
Netlify must detect a form definition in deployed static HTML, and some runtime-rendered framework forms require a hidden blueprint plus AJAX. Form Plume accepts the rendered form's POST directly, leaving one source of truth for its fields.
Form Plume exposes clear submission, storage, member, and retention allowances for form work. That separation is useful when hosting traffic, production deploys, compute, and forms should not share one purchasing or migration decision.
Choose by situation
Static marketing site already on Netlify
Netlify Forms
Deploy-time detection and unlimited free submissions make the native option difficult to beat when the site will stay on Netlify.
Agency using several hosting providers
Form Plume
One host-independent form workspace avoids teaching and operating a different submission path for every client stack.
React or Next.js form rendered at runtime
Form Plume
Direct endpoint submission avoids maintaining the static form blueprint Netlify may require for framework-generated markup.
Workflow built around Netlify Functions
It depends
Netlify's verified-submission event is deeply integrated; Form Plume is stronger when the destination should be portable signed webhooks and external apps.
FAQ
Form Plume is built for host-independent forms. Add its endpoint to a standard HTML form or submit with fetch, then keep the same backend when you move between static hosts, application platforms, site builders, or custom infrastructure.
Yes for Netlify's current credit-based plans. In April 2026, Netlify made form submissions free and unlimited across those plans. Hosting still uses credits for production deploys, bandwidth, compute, and web requests, and legacy account billing can differ.
Yes. Hosting the frontend on Netlify does not require using Netlify Forms. Create a Form Plume endpoint, set it as the form action or fetch destination, and test the success state, notifications, spam controls, and any webhook delivery before publishing.
Netlify detects forms by parsing static HTML during deployment. A form created only in the browser may not exist when that scan runs, so framework projects can need a static HTML definition with matching field names. A Form Plume React form posts to its endpoint at runtime without that detection step.
Form Plume is more accommodating when submissions contain several or larger files: its documented default is ten files per submission and 10 MB per file. Netlify supports one file per upload field and caps the entire form request at 8 MB.
Netlify automatically runs submissions through Akismet and supports honeypot fields and reCAPTCHA 2. Form Plume combines honeypots, time traps, rate limits, domain rules, blocklists, email hygiene, adaptive scoring, four CAPTCHA choices, and a recoverable spam quarantine.
It covers the core delivery job and expands the routes. Form Plume sends email notifications, includes one signed webhook on Free, and adds native integrations plus Zapier, Make, and MindCloud on paid plans. Netlify offers email, HTTP POST, Slack, Zapier, n8n, and form-triggered Functions.
Usually. Keep the visible fields and styling, replace Netlify's form attributes and hidden form-name field with a Form Plume action URL, then test normal posts, validation, redirects, files, and automation. Runtime framework forms can use the same endpoint through fetch.
Form Plume publishes a 60-day Free retention window, two years on Pro, and lifetime retention on Team. Netlify provides a submission UI, CSV export, API access, and manual deletion, while advising customers collecting personal information to export and delete it regularly.
Keep it when your static site already deploys on Netlify, automatic detection works reliably, unlimited submissions matter most, and your workflow benefits from Netlify Functions. Choose Form Plume when host portability, runtime form support, larger upload requests, explicit retention, or broader signed delivery solves a real constraint.
One line. Zero backend.
