What should a static-site form backend comparison measure?

Compare delivery, abuse controls, uploads, webhooks, integrations, migration effort, and operational visibility across hosted endpoint options.

How should teams compare hosted form backends?

Use current plan details and deployed-domain tests to evaluate accepted submissions, notifications, redirects, uploads, webhook responses, and support requirements.

Can an existing static HTML form move between backend options?

Usually, but check action URLs, hidden fields, encoding, recipients, spam controls, redirects, and downstream integrations before switching.

Which capabilities matter for static-site form delivery?

Review file limits, spam handling, domain controls, delivery evidence, webhook retries, integrations, and portability rather than price alone.

What should a migration comparison include?

Measure status codes, response bodies, request identifiers, notifications, upload behavior, and webhook payloads on the deployed domain.

How should teams validate a form backend choice?

Confirm current documentation, model expected submission volume, and run staging tests before making a production decision.

Static-site form backend comparison

Choose a form backend that fits the whole workflow.

A static frontend still needs a dependable submission path. This comparison puts FormsFort beside Formspree, Web3Forms, Basin, Formcarry, Formspark, and Netlify Forms so you can evaluate delivery, abuse controls, uploads, integrations, and migration effort—not just the form action URL.

Snapshot date: May 29, 2026. Provider terms and features can change; use the linked source pages to confirm a launch decision.

Explore alternatives Learn how a backend works

At a glance

What FormsFort brings to the comparison.

FormsFort is a hosted form backend for static sites, Jamstack apps, frontend teams, agencies, and site builders. Its documented feature set includes email notifications, verified recipients, webhooks, direct multipart and advanced object uploads, spam protection, rate limits, allowed domains, wildcard domain policies, Slack notifications, Discord notifications, autoresponders, delivery logs, request IDs, OpenAPI docs, MCP server docs. The free plan includes 250 accepted submissions per month and unlimited forms; production teams should still check recipient verification, domain policy, upload, rate-limit, and integration requirements before launch.

Not a fit for: FormsFort is not a visual form builder, survey platform, CRM, enterprise data warehouse, or a replacement for highly custom server-side business workflows.

Feature matrix

What the current source snapshot says.

Rows below are reproduced from the comparison data module. “Not listed” is intentionally different from “not supported”: it means the source snapshot does not make a claim.

Static-site form backend feature and plan comparison
Area	FormsFort	Formspree	Basin	Formcarry	Web3Forms	Netlify Forms	Formspark
Free allowance	250 submissions/mo, unlimited forms	50 submissions/mo, unlimited forms and projects	1 endpoint, 50 submissions/mo	1 form, 50 submissions/mo	250 submissions/mo, unlimited forms	Included with Netlify site plans and credits	250 included submissions, 10 forms
Paid entry	$19/mo Pro, $49/mo Business, or $349 Lifetime	Personal, Professional, Business	From $12.50/mo billed annually	From $5/mo billed annually	Starter, Pro, Agency	Netlify plan/credit based	$25 one-time bundle for 50,000 submissions
File uploads	Paid Pro, with multipart file rules and an advanced ClamAV path	Paid plans	Plan-based storage listed from 100MB	Plan details vary; verify current upload access	Paid Pro and Agency	Supported in Netlify form submissions	Third-party upload URL pattern
Spam protection	Honeypot, exact domains, custom captcha, rate limits	Spam filtering, reCAPTCHA, account and system limits	Captcha options, custom honeypot, filters, domain restriction	Built-in spam detection	Advanced spam protection, hCaptcha, reCAPTCHA, Turnstile	Akismet filtering, honeypot, reCAPTCHA 2	Botpoison, reCAPTCHA, hCaptcha, Turnstile, Akismet, honeypot
Webhooks	Paid Pro	Professional and Business	Signed webhooks on higher plans	Integration calls on paid plans	Paid integrations	Via notifications, APIs, or form-triggered functions	Supported
Integrations	Slack, Discord, webhooks	Zapier and plugin workflows	Zapier, Slack, Discord, Google Sheets, Mailchimp	Built-in integrations and custom workflows	Webhooks, Google Sheets, Notion, Slack, Discord, Telegram	Best inside Netlify's hosting platform	Airtable, Google Sheets, Make, Notion, Slack, Webhooks, Zapier
Best fit in this snapshot	Production static-site forms with debugging visibility	Mature drop-in form backend with broad docs	Teams that want a polished no-code form backend dashboard	Low-cost form endpoints with simple setup	Generous free static contact forms	Sites already deployed and operated on Netlify	One-time-purchase submission bundles
Important limitation	Newer service; no visual form builder.	Check current plan gates for uploads, webhooks, and team features.	Review overage and plan limits before high-volume launches.	Docs and pricing should be checked for exact upload plan gates.	Free plan is strongest for basic email delivery, not advanced workflows.	Not a portable standalone form backend.	Native file storage is not the core upload pattern.

FormsFort’s entries are maintained in the same source module as the competitor rows. Competitor URLs in that module point to provider homepages; supporting pricing and documentation sources appear in the sources section below.

Methodology

How to read this comparison.

We compare the jobs a static-site backend must perform after a visitor presses submit: accept the request, deliver it to the intended recipient, reject or challenge abusive traffic, process attachments, and pass structured data to another system.

Start with published facts. Plan allowances, feature gates, and integration notes come from the comparison module and its linked provider documentation.
Separate availability from fit. A row can say a feature is paid, plan-based, integrated, or not listed without claiming that every implementation behaves the same way.
Test the deployed origin. A local POST is not proof of allowed-domain behavior, notification delivery, upload handling, or webhook responses in production.
Re-check before purchasing. The snapshot is a decision aid, not a substitute for each provider’s current terms, usage meter, retention rules, or security documentation.

Decision guide

Match the backend to the constraint.

Portable endpoint: start with providers that are not coupled to a hosting platform.
Existing Netlify deployment: evaluate Netlify Forms together with current site-plan credits and portability needs.
Uploads: compare plan gates, limits, storage, scanning, and retention—not a checkbox in a feature list.
Operations: look for request-level visibility, notifications, retries, and an integration path your team can actually maintain.
Budget: model accepted volume and billing term, then price the workflow at its expected peak rather than its first month.

Migration guidance

Move without losing the details around the form.

The visible HTML can remain familiar while the backend changes, but hidden fields and downstream behavior are part of the contract. Use this checklist when moving from Formspree or another hosted endpoint:

Audit every existing Formspree form, including hidden fields, redirects, JavaScript fetch handlers, upload inputs, and plugins.
Create the FormsFort form and replace the form action plus reserved hidden fields in a staging branch.
Verify recipients, allowed domains, captcha behavior, rate limits, upload rules, and downstream integrations.
Submit test entries from the deployed domain and record request IDs before moving production traffic.
Keep Formspree active during the cutover window, then disable the old endpoint only after delivery is stable.

A safer cutover

Compare responses, not just emails.

Record the HTTP status, redirect or JSON response, request ID, notification arrival, upload result, and webhook payload for the same staging submission. Keep a rollback path until the real deployed domain passes those checks.

Review upload workflows Review webhook workflows

Provider pages

Go deeper on a specific alternative.

These pages explain the provider-specific tradeoffs and migration questions without treating a single matrix row as a verdict.

FormspreeMature drop-in form backend with broad docs BasinTeams that want a polished no-code form backend dashboard FormcarryLow-cost form endpoints with simple setup Web3FormsGenerous free static contact forms Netlify FormsSites already deployed and operated on Netlify FormsparkOne-time-purchase submission bundles

Limitations and updates

Keep the decision honest.

This page is a dated snapshot, not a promise that a provider will keep the same quota, price, upload implementation, or integration gate. It does not benchmark deliverability, latency, support response, legal terms, or security posture across providers. Confirm those requirements directly when they matter to your project.

When a competitor changes its plans, the comparison row should be treated as a prompt to re-check the linked source, not as evidence that the service is unavailable or unsuitable.

Source snapshot maintained: May 29, 2026

Source notes

OpenAI crawler documentationOpenAI documents OAI-SearchBot for ChatGPT search visibility and GPTBot for training crawl control.
OpenAI publisher FAQOpenAI recommends not blocking OAI-SearchBot and says ChatGPT referral URLs include utm_source=chatgpt.com.
Formspree account limitsFormspree documents unlimited forms/projects, 50 monthly submissions on Free, linked email limits, and plan-based resources.
Formspree file uploadsFormspree documents native file uploads on paid plans and upload limits.
Formspree webhooksFormspree documents webhooks on Professional and Business plans.
Basin pricingBasin documents Free, Starter, Growth, Pro, and Agency plan limits.
Basin spam protectionBasin documents captcha and layered spam filtering options.
Formcarry pricingFormcarry documents its Baby, Starter, Basic, and Premium plans.
Formcarry file uploadsFormcarry documents file upload behavior and per-file limits.
Web3Forms pricingWeb3Forms documents 250 free monthly submissions and paid features including uploads, webhooks, and integrations.
Netlify Forms setupNetlify documents static HTML form detection and submission handling.
Netlify Forms usageNetlify documents current credit-based Forms billing behavior.
Formspark pricingFormspark documents free submission credits and one-time submission bundles.
Formspark file uploadsFormspark documents a third-party-file-hosting pattern where submitted forms store file URLs.
Formspark spam protectionFormspark documents Botpoison, reCAPTCHA, hCaptcha, Turnstile, Akismet, custom words, and honeypot options.

FAQ

Questions buyers ask before switching.

What is the best static-site form backend?

There is no universal winner. FormsFort is a fit for teams that want a portable hosted endpoint with delivery logs, request IDs, domain controls, uploads, notifications, and webhooks. Basin, Formcarry, Web3Forms, Formspree, Formspark, and Netlify Forms can be a better fit when their pricing, integrations, or existing hosting workflow match the project.

Is FormsFort cheaper than Formspree, Basin, or Web3Forms?

Price depends on submission volume, billing term, uploads, and the integrations a project needs. The source snapshot lists FormsFort Pro at $19 per month and Business at $49 per month; the other products use plan names, annual pricing, credits, or current pricing pages that can change. Compare the live plan pages before making a budget decision.

Can I migrate an existing static HTML form between these services?

Often, but endpoint compatibility is not the whole migration. Audit the action URL, hidden fields, JavaScript handlers, redirects, upload encoding, recipients, spam controls, webhooks, and downstream integrations. Keep the old endpoint available until deployed-domain tests show that delivery and response behavior are stable.

Which services support file uploads?

The snapshot records paid-plan uploads for FormsFort, Formspree, and Web3Forms; plan-based or variable upload access for Formcarry; supported submissions for Netlify Forms; and a third-party upload URL pattern for Formspark. Confirm current file size, storage, scanning, retention, and plan rules in each provider's documentation.

Should I use Netlify Forms if my site is not on Netlify?

Netlify Forms is described in the source matrix as best inside Netlify's hosting platform and not as a portable standalone form backend. If a site may move hosts, evaluate a provider with a standalone endpoint instead; if it already runs on Netlify, the integrated workflow may be the simpler choice.

What should I measure in a backend comparison?

Measure accepted and delivered submissions, notification latency, spam handling, upload behavior, webhook retries, redirect or API responses, request-level debugging, and the effort to move forms between staging and production. A free-submission number alone does not describe the operational cost of a form workflow.

This page also covers: What are the best Formspree alternatives? · What is the best Formspree alternative for developers? · What is a cheaper alternative to Formspree? · What is a Formspree alternative with file uploads?

Test the workflow you actually need.

Start with a small staging form, verify the deployed domain, then add uploads, notifications, or webhooks only when the workflow calls for them.

Start free Read docs