send.webforms.toRead the docs →

Formcarry or Formspree: control over sending, or breadth of plugins

Formcarry is the choice when you care how the email is sent: your own SMTP server and white-label notifications come from its lowest paid tier. Formspree is the choice when you care where the submission goes next: CRM and helpdesk plugins, payments and form rules.

The difference that decides it

Formcarry is developer-focused and generous where other services gate features to top tiers. Its Starter plan, billed annually only, includes unlimited forms, sending through your own SMTP server and white-labelled notifications. Built-in integrations are metered as integration calls per month, which is worth reading closely if one submission fans out to several tools.

Formspree's strength is the other end of the pipe. Its plugin catalogue reaches CRMs and helpdesks natively, it can take payments through Stripe, and it supports form rules and managing forms as code. It costs more to get there, and its free tier is small.

Side by side

CapabilityFormcarryFormspree
Stored submissionsStored and exportableStored, searchable, exportable
DestinationsBuilt-in integrations, metered as integration callsPlugins per form plus a large catalogue
Routing rulesNot a documented core featureForm rules on their plans
Payments in the formNot a documented featureStripe plugin

"Not a documented feature" means it is not in their published documentation as we read it, not that it can never be done. Check with them before ruling something out.

Which to choose

Choose Formcarry if

Choose Formcarry when you want mail sent from your own server or domain, white-labelling on a small budget, or unlimited forms without paying for a higher tier.

Choose Formspree if

Choose Formspree when submissions need to land in a CRM or helpdesk directly, when you take payments in forms, or when you want routing rules.

Pricing, as each lists it

Copied from each pricing page on the date shown. Prices change without notice, so check the current figure before deciding.

Formcarry

As listed on , in USD. Current pricing

  • Baby: $0, 50 / month (1 form, 1 team member)
  • Starter: $5 / month, 500 / month (Billed annually only; no monthly option for this tier)
  • Basic: $19 / month, 2,000 / month ($15 / month billed yearly)
  • Premium: $99 / month, 30,000 / month ($80 / month billed yearly)

Formspree

As listed on , in USD. Current pricing

  • Free: $0, 50 / month (Testing and development)
  • Personal: $15 / month, 200 / month ($10 / month billed yearly)
  • Professional: $30 / month, 2,000 / month ($20 / month billed yearly)
  • Business: $90 / month, 20,000 / month ($60 / month billed yearly)

A third option, honestly assessed

If the thing you want from both is fan-out to several tools, look at how each one counts it: metered integration calls in one, a plugin per destination in the other. WebForms counts a submission once however many destinations it reaches, and routes by field value on its paid plans. For your own SMTP server specifically, Formcarry is the better answer.

WebForms vs Formcarry · WebForms vs Formspree · Our pricing

Related comparisons