§ 01
Short answer: which one should you pick?
Mailform is the right call if you specifically need to mail a printed letter or generate a signed PDF from a form submission — it's one of the few backends with a real postal-delivery integration. If your workflow ends in 'this needs to arrive on paper at a physical address', Mailform earns the slot.
splitforms is the right call for everything else. If 'a user filled out a form' should result in storage, spam classification, webhook fan-out, and an inbox notification — without paying for postal infrastructure you'll never use — splitforms is leaner and cheaper at every volume tier.
§ 02
Why developers switch from Mailform to splitforms
The most common trigger is realizing the postal-mail and PDF features were never actually used. Mailform's pricing reflects those features whether or not you use them — pay-as-you-go fees and tiered plans tuned to physical-mail volume. splitforms is priced purely on submission volume with no per-event surprises.
The second trigger is the dashboard. Mailform's UI is tuned for the compliance/government-vendor buyer, which makes it heavier than developers usually want. splitforms ships a fast, search-and-filter-first dashboard that's faster to inspect submissions in.
The third trigger is webhooks and API surface. Mailform has webhooks, but the API and developer documentation are thinner than a developer-first product. splitforms ships an open REST API, signed webhooks with retries, and an MCP server on every plan.
§ 03
Mailform vs splitforms: feature comparison
Postal mail: Mailform yes, splitforms no. If you need this, Mailform wins.
PDF generation: Mailform yes, splitforms no (use a separate PDF service like DocRaptor + a webhook).
Storage: both store submissions; splitforms's search and filter is faster.
Spam protection: splitforms uses AI classification plus honeypot. Mailform uses CAPTCHA.
Pricing model: splitforms tiers on submission volume only. Mailform tiers on event types (email vs PDF vs postal).
API: splitforms ships a documented open REST API and MCP server. Mailform's API is less developer-focused.
Free tier: splitforms 1,000 submissions/month. Mailform free is low-volume email only.
§ 04
Common Mailform issues splitforms solves
"I'm paying for postal-mail features I never use." splitforms has flat per-submission pricing and no per-event upcharges.
"The dashboard feels heavy." splitforms is built for fast inspection: search, filter, export, re-deliver.
"I want a real REST API." splitforms ships an open REST API and MCP server on every plan, including free.
"I want signed webhooks with retries." splitforms includes them on every plan.
§ 05
How to migrate from Mailform to splitforms
If you don't use the postal-mail or PDF features, migration is the standard action-URL swap — change your form's action to `https://splitforms.com/api/submit` and you're done. If you do use those features, keep Mailform for the specific workflows that need them and route everything else to splitforms.
§ 06
Frequently asked questions
Is splitforms a viable Mailform alternative? Yes for everything except physical-mail and PDF delivery. If those aren't on your workflow, splitforms is cheaper, faster, and developer-first.
Can splitforms send postal mail? No. If you need that, keep Mailform for the postal-mail routes and use splitforms for everything else.
What about PDF generation? Use a service like DocRaptor or Carbone, wire it to splitforms via a webhook.
Is there a one-time payment plan? Yes — $59 for the 4-Year plan at 15,000 submissions/month for 48 months.