Point any HTML form at one endpoint. 500 free submissions — no card, no time limit — and unlimited forms.
Create free accountThe differences that affect a real project
This comparison is published by SplitForms, a competing form backend. Vendor facts were checked on October 14, 2026 using the linked pricing and documentation pages. It is a documentation-based comparison, not a claim of hands-on delivery testing. Prices are in USD and should be checked again before purchase.
| Question | Formspark | Formcarry | SplitForms |
|---|---|---|---|
| Free allowance | 250 total; 10 forms | 50/month; 1 form | 500 total; unlimited forms |
| Entry paid offer | $25 once for 50,000 submissions; promotional price | Starter $6/month or $5/month billed annually; 500/month | Pro $5/month; 5,000/month |
| Upload approach | Third-party upload service; stores the file URL | Paid plans; native files up to 10 MB each | Paid plan + Storage; 5 files of 5 MB each |
| Automation | Webhooks; paid REST API | REST API and documented MCP tools | API and MCP; signed webhooks on paid plans |
References: Formspark pricing · Formcarry pricing · SplitForms pricing · Formspark upload docs · Formcarry upload docs
Compare allowances over the life of the site
A total allowance and a monthly allowance answer different questions. At a hypothetical ten submissions a month, 250 total submissions would cover 25 months before other constraints; a recurring allowance of 50 would not be exhausted at that pace. At higher volume, both free options can be insufficient. These are arithmetic examples, not usage forecasts.
Prepaid credits can be attractive for a brochure site whose traffic is slow or seasonal. A recurring plan can be easier to budget when a team expects ongoing lead volume and uses paid integrations. Include renewal terms, file storage, collaborator access and the cost of any additional upload provider in the decision.
SplitForms Pro is a strong candidate for an active site needing 5,000 submissions a month at $5/month. Formspark can still cost less for a small site that uses a prepaid bundle slowly. Paying a subscription is justified by the features and operating model you need, not by an assumption that prepaid service is inferior.
References: Formspark allowance rules · Current SplitForms allowances
Neither competitor is just a CAPTCHA wrapper
Formspark documents automatic filtering, honeypots and optional verification providers. Formcarry also documents automatic spam detection and a reviewable spam category, with reCAPTCHA as an additional option. It would be inaccurate to describe either product as having only a honeypot or forcing a puzzle on every visitor.
Evaluate the outcome you need: whether suspected spam is retained for review, whether it consumes allowance and how genuine users recover from a rejection. SplitForms combines form-level controls with a dashboard workflow; its value should be assessed through that workflow rather than an unsupported claim of perfect spam detection.
References: Formspark spam protection · Formcarry spam protection · SplitForms spam documentation
For automation, check authentication and recovery
Formspark explicitly states that its webhook requests are not signed. SplitForms paid webhooks use HMAC-SHA256 signatures with a documented timeout and limited retry behavior. That distinction matters when your receiver needs to authenticate a delivery before creating a CRM record or triggering work.
Formcarry now documents an MCP connection for managing forms and submissions, so MCP availability alone does not distinguish SplitForms from it. Compare the operations your client needs, the scopes granted and whether your team can revoke access. An AI assistant connection is privileged account access, separate from the public endpoint that visitors submit to.
References: Formspark webhook verification · Formcarry MCP tools · SplitForms webhook delivery
When to put SplitForms on the shortlist
Start with SplitForms when you already own the form markup, want a stored lead record plus notification email, and need a low-cost path to signed webhooks and recurring monthly volume. Start with a small representative form and verify its fields, files, redirects and receiving workflow before migrating the rest.
Keep Formspark on the shortlist if avoiding recurring billing is the central requirement. Keep Formcarry on it when its upload limits, integrations or team workflow fit better. A useful evaluation ends with a working flow and clear ongoing costs, rather than a winner declared from a single plan number.
References: SplitForms migration checklist
Frequently asked questions
Is Formspark’s free allowance monthly?
No. Formspark documents an initial total balance. Formcarry’s free allowance resets monthly, so the two numbers should not be compared as if they had the same billing period.
Does Formcarry support AI agents?
Yes. Its current documentation describes an MCP connection for form and submission operations. Check the vendor’s connection guide for current client setup.
Why consider SplitForms alongside them?
SplitForms combines unlimited forms, an initial free allowance, recurring paid submission limits and HMAC-signed webhooks on paid plans. Compare those features against your volume, upload and collaboration requirements.