Form Backend Tool vs Formspree

Both products do the same core job: your website's form posts to a hosted endpoint, the submission is stored, and you get notified, all without building or running a backend of your own. They are not identical products, though. Formspree is a broader platform with file handling, automation and team features. Form Backend Tool is a narrower service that meters submissions per form instead of per account. Which one fits depends on what your forms actually need, and this page works through the differences with the figures each product publishes. Formspree's figures below are from its official pricing page, checked in November 2026; prices and plans change, so confirm them there before you decide. The underlying concept is explained in What Is a Form Backend?

Quick comparison

CriterionForm Backend ToolFormspree
Hosted form endpointYesYes
Works with static HTMLYesYes
ReactYesYes
Next.jsYesYes
JSON / fetch submissionYesYes
SDK requiredNo (none is offered)No (an optional JavaScript library is offered)
Your own backend requiredNoNo
Dashboard for submissionsYesYes (the Formspree inbox)
Email notificationsYesYes
Spam protectionHoneypot field and per-visitor rate limitMachine-learning filtering (Formshield) and reCAPTCHA options
File uploads storedNoPaid (1 to 10 GB of storage by tier)
Outgoing webhooksNoPaid (a premium plugin, Professional and above)
AutoresponderNoPaid (Professional and above)
Submissions APINoPaid (Professional and above)
IntegrationsLimited (email and WhatsApp notifications)Yes (a large plugin library)
Submission analyticsNoYes (daily analytics reports in the inbox)
Team membersNoYes (on paid tiers)
WhatsApp notificationsPaid (Pro and Agency, verified number)Listed as a notification plugin
Free planYesYes
Free submissions250 per form per month, up to 3 forms50 per month across all forms
Paid plans start at$12 per month$15 per month billed monthly ($10 billed yearly)
Submission quota modelPer formAccount-wide

The rest of this page explains the rows that usually decide the choice: the quota model, files, automation and teams.

Pricing and the quota model

The headline prices are only half of the comparison, because the two products count submissions differently. Form Backend Tool gives every form its own monthly quota. Formspree gives the account one monthly pool that all of its forms share, with no limit on the number of forms. Neither model is wrong; they suit different shapes of use.

PlanPriceSubmissionsForms
Form Backend Tool Free$0250 per form / monthUp to 3
Form Backend Tool Pro$12 / month2,500 per form / monthNo cap
Form Backend Tool Agency$35 / month10,000 per form / monthNo cap
Formspree Free$050 / month in totalNo cap
Formspree Personal$15 / month ($10 billed yearly)200 / month in totalNo cap
Formspree Professional$30 / month ($20 billed yearly)2,000 / month in totalNo cap
Formspree Business$90 / month ($60 billed yearly)20,000 / month in totalNo cap

A worked example, using only the published limits. Say a site has three forms (contact, quote request and a service inquiry) and each receives about 100 submissions a month, 300 in total. On Formspree's Free plan the shared pool is 50 a month, and Personal raises it to 200, so this site needs Professional (2,000 a month) at $30 a month billed monthly, or $20 billed yearly. On Form Backend Tool's Free plan each of the three forms has its own 250, so the same traffic fits without a paid plan.

The same arithmetic runs the other way. One single busy form receiving 1,500 submissions a month fits Formspree Professional's 2,000 pool, and it also fits Form Backend Tool Pro's 2,500 per-form quota at $12 a month; but a single form receiving 5,000 a month exceeds every Form Backend Tool plan except Agency (10,000 per form), while on Formspree it needs Business (20,000). Count your forms and your per-form volume first; the model that fits follows from those two numbers. The live figures for this product are in the pricing section, and its exact technical ceilings are in the docs limits section.

File uploads

This is the clearest difference between the two products. Form Backend Tool does not store uploaded files: if a form contains a file input, the file is ignored and only the text values are kept. Formspree accepts file uploads on its paid plans, up to 5 files per submission at 25 MB per file, stored remotely with download links in the notification email, with total storage of 1 GB (Personal), 5 GB (Professional) or 10 GB (Business).

If your form exists to receive documents, CVs, images or briefs, that settles the choice: use Formspree, or your own backend. If your forms are text (contact messages, quote requests, inquiries, signups), file storage is a capability you would be paying for without using, and either product handles the form itself.

Webhooks, autoresponders and integrations

Form Backend Tool delivers a submission to exactly two places: the dashboard (with CSV export) and a notification, by email on every plan and by WhatsApp on Pro and Agency for a verified number. It has no outgoing webhooks, no autoresponder and no submissions API, so nothing is pushed into other systems automatically.

Formspree is built further in this direction. Its plugin library connects submissions to tools such as Google Sheets, Airtable and Notion, chat tools such as Slack, Discord and Telegram, CRMs such as HubSpot, Salesforce and Pipedrive, newsletter tools, support desks, and Stripe for payments. A webhook plugin and Zapier are in the premium set, available on Professional and above, as are autoresponses and API access. Its Business tier adds a rules engine that routes submissions based on their content.

So the deciding question is what happens after a submission arrives. If a person reads it in a dashboard or an inbox and replies by hand, Form Backend Tool covers the whole flow. If the submission must immediately create a spreadsheet row, a CRM contact or a ticket, or the visitor must receive an automatic confirmation email, Formspree is the suitable choice of the two.

Team and client workflows

Formspree supports shared work: you can link client email addresses to your account (2 on the Free plan), send submissions to multiple recipients, group forms into projects, and add team members with their own logins (one included on Professional, more on Business). Its Business tier adds custom email templates and sending domains, which agencies use to present notifications under the client's brand. Formspree also lists compliance badges including SOC 2 Type II on its homepage, which can matter when a client's procurement process asks.

Form Backend Tool is a single-account product. There are no team seats, no client sub-accounts, no white-label dashboard and no per-client billing inside one account. A freelancer can still run several client forms from one account, with each form notifying the client's own verified email, or hand a client their own account; the two honest models are described in Form Backend for Freelancers and Agencies. But if clients need their own logins or branded notifications today, that is Formspree territory.

Choose Form Backend Tool if

  • You want a simple hosted endpoint. Point an HTML form or a fetch call at it and you are done; there is no SDK to install and no server to run. The static websites guide shows the whole setup.
  • Dashboard storage and an email notification are the whole job. Submissions are stored first, then delivered, and can be exported to CSV.
  • You have several modest forms rather than one huge one. The per-form quota means each form carries its own allowance, on Free and on paid plans.
  • You want the $12 Pro plan as a monthly price. It is $12 a month without an annual billing commitment to reach that figure.
  • WhatsApp alerts matter to you. On Pro and Agency, a form can notify a verified WhatsApp number as well as an inbox.
  • You do not need files, webhooks, an autoresponder, integrations or team seats. If none of those are on your requirements list, you are not missing anything by choosing the narrower product.

Choose Formspree if

  • Your forms receive files. Uploads with real storage are available on its paid plans and do not exist here.
  • You need webhooks or downstream automation. Submissions must flow into Sheets, a CRM, a support desk or your own systems through its plugins, webhook or API.
  • Visitors need an automatic confirmation. Autoresponses are a Professional-and-above feature there and are not offered here.
  • You work in a team or for clients who need access. Linked emails, projects, team logins and branded email options are built for that.
  • You want submission analytics and routing rules. Daily analytics reports in the inbox, and a rules engine on the Business tier.
  • You prefer an established provider. Formspree has operated for years at a scale it publishes on its homepage. Form Backend Tool is a new product, and this page will not pretend otherwise.

Project scenarios

Personal portfolio with one contact form

Both fit, on free plans. A portfolio form rarely passes Formspree's 50 submissions a month, and it is far inside Form Backend Tool's 250 for that form. Choose by the rest of your site: a second form (a newsletter signup, say) gets its own 250 here, while on Formspree both forms share the same 50.

Small business with contact, quote and inquiry forms

This is the multi-form shape from the pricing example, and it is where the quota models diverge. Three forms at moderate volume fit Form Backend Tool's Free plan, or Pro at $12 a month as volume grows. On Formspree the shared pool means the same site is on Professional ($30 a month billed monthly, $20 yearly) once it passes 200 submissions a month in total. If the business also wants submissions in a spreadsheet automatically, the balance flips: that is a Formspree plugin, and it does not exist here. The business side of this product is covered in Form Backend for Small Business Websites.

Agency managing forms for several clients

Formspree is designed for this: linked client emails, projects per client, team logins, and branded notifications on higher tiers. Form Backend Tool can run the forms, with each client's inquiries landing in the client's own inbox, but clients get no login of their own and nothing is white-labelled. If client-facing access is part of what you sell, choose Formspree; if you keep form operations inside your own team and the clients just want their leads by email, either can work.

Application form with CV uploads and a CRM

Formspree, or your own backend. Form Backend Tool cannot store the CVs and cannot push submissions into a CRM, so it is simply not a candidate for this shape. On Formspree, the file storage is on paid plans and the webhook and CRM plugins are on Professional and above.

Switching between the two

Both products are hosted endpoints used the same way, so moving a form between them is a configuration change, not a rebuild. In practice it means: create the form in the new service, change the form's action (and any fetch URL) to the new endpoint, replace service-specific fields and settings (Form Backend Tool uses fields such as _redirect and _honey; Formspree has its own special fields and per-form plugin settings), and set the notification address again. Neither side offers a one-click migration for the other. Submissions already stored do not move automatically, although both dashboards offer CSV export, and Formspree's Custom tier lists full-service onboarding. The field-level details for this product are in the HTML form integration guide and the documentation.

Comparison FAQ

Is Form Backend Tool cheaper than Formspree?

Its paid plans start lower ($12 a month against $15 billed monthly), but the honest answer depends on your shape, because the quotas are counted differently: per form here, account-wide there. The worked examples in the pricing section show cases in each direction, so neither product is simply the cheaper one.

Does Form Backend Tool support file uploads?

No. File inputs are ignored and uploaded files are not stored; only text values are kept. If you need uploads, Formspree stores them on its paid plans.

Does Formspree support webhooks?

Yes, as a plugin in its premium set, on the Professional plan and above. Form Backend Tool does not offer outgoing webhooks.

Which one is better for a static HTML site?

Both are built for exactly that; a static site is the core case for each. The differences are the quota model and the feature set around the endpoint, not the basic integration. Our step by step tutorial shows what the integration looks like here.

Do I need an SDK for either?

No. Both work with a plain form post or a fetch call. Formspree additionally offers an optional JavaScript library; Form Backend Tool offers no SDK and needs none.

Can I use React or Next.js with both?

Yes. Both accept submissions from anything that can send an HTTP request. For this product, the React guide and the Next.js guide cover the two submission modes each.

Which one uses per-form quotas?

Form Backend Tool. Formspree meters one account-wide pool shared by all of your forms.

When should I build my own backend instead?

When the form is really an application: user accounts, payments, bookings, multi-step state, custom validation logic on every submission, or data that must stay inside infrastructure you control. In those cases neither hosted endpoint is the right tool, as the general FAQ also sets out.

Verdict

The better choice depends on what your forms actually need. If the job is a hosted endpoint, stored submissions, a dashboard and an email (or WhatsApp) notification, and your volume is spread across several forms, Form Backend Tool's per-form quotas and $12 Pro plan may be the better fit. If your forms need file storage, webhooks, an autoresponder, integrations, team access or analytics, Formspree covers those requirements and may be the better fit. And if the form is really an application in disguise, skip both and build the backend. If you are still unsure which shape yours is, the support page reaches the founder directly, including if the honest answer turns out to be Formspree.

The companion comparison, Form Backend Tool vs Web3Forms, covers the other common pairing: the same per-form model set against an inbox-led service with an account-wide pool.