WPForms alternative: your own HTML form, one endpoint

The most common trigger is host migration. A team decides to move from WordPress to a static site, a Next.js app, or a headless CMS — and discovers WPForms doesn't follow them, because the submissions and the plugin both live in the WordPress database. Every form has to be rebuilt on a new backend during the migration. splitforms is host-agnostic: the form action URL works the same regardless of where the page is served, so moving hosts (or moving off WordPress entirely) doesn't touch the form layer at all.

The second trigger is wanting the form data outside WordPress. WPForms stores submissions in your WordPress MySQL database, which means backups, exports, and integrations all flow through WordPress. For a small site that's fine; for any team that wants submissions flowing into a CRM, a Slack channel, an AI agent, or a dedicated analytics tool, the WPForms path requires add-ons (sometimes paid) and WordPress-side plugins. splitforms ships HMAC-SHA256 signed webhooks (one retry after ~2s on network errors, timeouts and 5xx; not on 4xx; 8-second timeout) on paid plans, plus an open REST API and MCP server on every plan.

The third trigger is deliverability. WPForms relies on whatever SMTP plugin you've configured in WordPress (WP Mail SMTP, also from Awesome Motive). If you haven't configured transactional SMTP, your form-submission emails are sent via PHP `mail()` — one of the worst-rated email delivery paths on the modern web, with high spam-folder rates. splitforms stores accepted submissions before attempting owner notification email. Delivery time and inbox placement depend on the mail provider and recipient settings.

Host requirement

splitforms works on any host. WPForms only works on WordPress-hosted sites — there is no non-WordPress deployment path.

Builder UI

WPForms wins clearly here. The drag-and-drop builder inside wp-admin, the template gallery, and the add-on ecosystem are mature and polished. splitforms is a backend — you write the HTML.

Submission storage

splitforms stores every submission in a dedicated backend with search and filter on every plan (no automatic expiry on any plan), and CSV export on paid plans. WPForms stores submissions in your WordPress database, surfaced through a wp-admin submissions panel that requires add-ons for CSV export on the free tier.

Webhooks

splitforms unlocks HMAC-SHA256 signed webhooks (one retry after ~2s on network errors, timeouts and 5xx; not on 4xx; 8-second timeout) on paid plans. WPForms needs paid add-ons (Zapier or webhook add-ons) to send submissions anywhere outside WordPress.

Spam protection

splitforms uses a smart spam filter on top of honeypot. WPForms leans on honeypot plus whatever anti-spam plugin (Akismet, reCAPTCHA) you've installed in WordPress.

Notifications

splitforms stores accepted submissions before attempting email; delivery and inbox placement depend on provider and recipient settings. WPForms uses your WordPress mail configuration.

API

splitforms ships an open REST API and MCP server on every plan. WPForms has no documented public REST API for submissions; you're querying the WordPress database directly or using add-ons.

Pricing model

splitforms tiers on submission volume. WPForms tiers on yearly license + site count + feature gates simultaneously.

• “We're moving off WordPress and our forms are trapped in the WP database.”

  splitforms is host-agnostic. Migrate to Next.js, Astro, or a static site whenever you want; the forms keep working without changes.

• “I want submissions in my CRM via webhook, not in my WordPress admin.”

  splitforms includes HMAC-SHA256 signed webhooks (one retry after ~2s on network errors, timeouts and 5xx; not on 4xx; 8-second timeout) on paid plans. Wire submissions directly into HubSpot, Salesforce, or your own service.

• “My WPForms emails are landing in spam because PHP mail is unreliable.”

  splitforms uses owner email notifications, not PHP `mail()`.

• “I'm getting AI-generated spam that the WordPress anti-spam plugins can't catch.”

  splitforms runs every submission through smart spam filtering: automatic, rule-based scoring of content signals such as links, spam phrases and disposable email addresses.

• “I want to drive form submissions from a Claude or Cursor agent.”

  splitforms ships an MCP server natively. WPForms has no equivalent.

• “I want my form data outside my WordPress database for security isolation.”

  splitforms stores submissions in a dedicated backend. Your form data isn't coupled to your WordPress install's security perimeter.

Step 1: sign up at splitforms.com for a free access key — no credit card required. Step 2: rebuild your form as standard HTML. For each WPForms field, write a corresponding `<input>`, `<textarea>`, or `<select>` inside `<form action="https://splitforms.com/api/submit" method="POST">`. WPForms field types map cleanly: text to text input, textarea to textarea, dropdown to select, checkboxes to checkbox group, radio to radio group. Step 3: submit a test entry and confirm it lands in the splitforms dashboard.

Past submissions stay in your WordPress database for as long as you keep WPForms installed; splitforms starts collecting from the moment you switch. If you want to backfill historical submissions into splitforms, the open REST API accepts server-to-server POSTs so you can replay your WPForms export through a small migration script.

If you were using WPForms' Stripe add-on to collect a fixed fee, splitforms has a native equivalent on paid plans: connect your own Stripe account in one click, set the amount in Form settings under Payments, and submitters are redirected to Stripe Checkout after they submit. The submission is stored either way and marked paid or unpaid in the dashboard, and refunds, receipts, and payouts stay in your own Stripe dashboard. For PayPal, for itemized order totals, or for amounts that vary per respondent, the client-side pattern still applies — run Stripe Elements or a PayPal button on the page and POST the resulting token alongside the form fields.

Is splitforms a true WPForms alternative? For the backend layer — POST endpoint, submission storage, dashboard, webhooks, spam filtering, file uploads, notifications — yes, with a real dedicated backend and an open API. For WPForms' drag-and-drop builder and add-on ecosystem, splitforms doesn't try to replicate those.

Does splitforms work inside WordPress? Yes — splitforms is just an HTML form action. You can use it inside a WordPress page (via the HTML block or a custom shortcode) or outside WordPress entirely. The form action URL is host-agnostic.

What about WPForms' Stripe and PayPal add-ons? splitforms has native Stripe payments on paid plans — connect your own Stripe account, set a fixed amount per form, and submitters pay through Stripe Checkout after submitting, with each submission marked paid or unpaid. Square is coming soon. PayPal has no native equivalent, and neither do itemized carts or variable amounts; for those you'd run a PayPal button or Stripe Elements client-side and POST the resulting token.

Will my WPForms submissions carry over? Past submissions stay in your WordPress database. splitforms starts collecting from the moment you switch. You can backfill historical data through the open REST API if needed.

Is there a yearly plan? Yes. Annual is $49/year for 15,000 submissions/month with every Pro feature; a yearly WPForms Pro license is $159.50.