send.webforms.toRead the docs →

Comparison

The Formcarry alternative for forms that go more than one place

Formcarry is a developer-focused endpoint service with its own integration-call metering. WebForms adds conditional routing and per-attempt delivery visibility.

Start freeSee pricing

Formcarry is built for developers: unlimited forms on every paid plan, your own SMTP server if you want it, and white-label support down to the Starter tier. Its integrations are metered separately from submissions, counted as integration calls per month, which is a detail worth checking if you plan to push every submission through several connected apps.

What is not part of the product is conditional routing or a per-destination delivery log. Submissions go to the same configured destinations every time, and there is no dashboard record of what response a webhook returned versus what an email send did.

WebForms fans a submission out to email, Slack, Discord, Telegram and webhooks together, can route it differently based on field values, and logs every delivery attempt with its status and response so a missing notification is diagnosable.

When to stay with Formcarry

Switching has a real cost. These are the cases where we would not bother.

WebForms vs Formcarry

Capability by capability, then their published prices. Anything we quote for Formcarry was read off their own pricing page on the date shown, but prices change - check their pricing directly before deciding.

CapabilityWebFormsFormcarry
SetupPoint form action at your endpoint. Works on fully static sites.Same endpoint-per-form model.
Forms includedUnlimited forms on every plan, including free.Unlimited forms from the Starter tier up; the free Baby plan is limited to one.
Submission storageStored, searchable, exportable as CSV or JSON.Stored and exportable.
Fan-out per submissionEmail, Slack, Discord, Telegram and webhooks from one submission.Built-in integrations metered as integration calls per month.
Conditional routingRoute on field values to different destinations per rule.Not a documented core feature.
Delivery logPer-destination status, response and retry history.No per-destination delivery log documented.
Spam filteringHoneypot, Turnstile, rate limits and an AI classifier that learns from your marks.Spam filtering included; check their docs for specific methods.
Own email serverNot supported; sends go through our verified sending domain.Use your own SMTP server from the Starter tier up.
File uploadsSupported on paid plans, with per-plan storage and retention.Supported, 1GB to 30GB by plan.

Formcarry pricing

Read from their pricing page on . Prices in USD.

PlanPriceSubmissions
Baby$01 form, 1 team member50 / month
Starter$5 / monthBilled annually only; no monthly option for this tier500 / month
Basic$19 / month$15 / month billed yearly2,000 / month
Premium$99 / month$80 / month billed yearly30,000 / month

Moving from Formcarry

  1. Export your submissions

    Download your submission history from Formcarry before changing anything.

  2. Create matching forms

    Add one WebForms form per Formcarry form and copy each endpoint URL.

  3. Update the action attributes

    Swap the endpoint URL in your markup. Field names and AJAX submissions carry over without modification.

  4. Rebuild destinations, then add routing

    Recreate the integrations you rely on, then add routing rules if a form needs different destinations depending on what was submitted.

Try it without deciding anything

The free plan includes 300 submissions a month, unlimited forms, email delivery, stored submissions and spam filtering, with no card required and no expiry. Point one form at it and keep Formcarry running on the others until you are convinced.

Questions

The markup change is one line per form, since both use a plain endpoint URL. Recreating destinations in the dashboard is the bulk of the work.

Other comparisons