A Contact Form 7 alternative built for shipping.

Contact Form 7 is genuinely one of the longest-running free contact form options on the web. Maintained continuously since 2007, it ships the form markup and the mail-sending logic, runs entirely inside WordPress, and costs nothing. For a WordPress site owner who wants a free contact form, is comfortable bolting on a separate SMTP plugin for deliverability, a separate storage plugin for submissions, and a separate anti-spam plugin for spam, Contact Form 7 is the lightweight, no-cost baseline.

splitforms is the right pick when you want the backend handled. The free tier is 500 submissions/month with a real dashboard, AI spam filtering, and dedicated SMTP for deliverability — all built in, no plugins to install, no PHP version compatibility to worry about. And splitforms works on any host, not just WordPress, which means moving off WordPress (or running a mix of WordPress and non-WordPress sites) doesn't break your forms.

The most common trigger is the missing submission storage. Contact Form 7 by default sends an email and forgets — there's no submissions table, no audit trail, no way to search or export. The standard workaround is the companion Flamingo plugin (also by the same author), which stores submissions in the WordPress database. That works, but it's another plugin to install, another update to track, and another piece of WordPress infrastructure to maintain. splitforms ships a real submission dashboard with permanent storage, search, filter, and CSV export on every plan, including free.

The second trigger is deliverability. Contact Form 7 sends mail via `wp_mail()`, which by default uses PHP `mail()` — one of the worst-rated email delivery paths on the modern web, with high spam-folder rates. The standard workaround is the WP Mail SMTP plugin (or similar), which lets you route mail through a real SMTP provider. That works, but again it's another plugin. splitforms uses dedicated SMTP with proper SPF/DKIM out of the box, so submissions actually land in the inbox without any plugin configuration.

The third trigger is host lock-in. Contact Form 7 only runs on WordPress. If you ever want to move a site to Next.js, Astro, or a static site, your forms break. splitforms is host-agnostic — the form action URL works the same regardless of where the page is served.

The fourth trigger is wanting real integrations. Contact Form 7 doesn't ship webhooks. Routing a submission to Slack, a CRM, or an AI agent requires yet another add-on plugin (often paid). splitforms ships HMAC-SHA256 signed webhooks (single delivery attempt, 8-second timeout) on paid plans, plus an open REST API and MCP server on every plan including free.

Price

Contact Form 7 is free forever. splitforms is free for 500 submissions/month, $5/mo for 5,000, or $59 every 3 years for 15,000/month over 36 months. For pure $0 cost on a WordPress site, Contact Form 7 wins.

Host requirement

splitforms works on any host. Contact Form 7 only works on WordPress-hosted sites.

Submission storage

splitforms stores every submission permanently in a dedicated backend with search, filter, and CSV export. Contact Form 7 stores nothing by default — you need the Flamingo companion plugin to keep submissions in your WordPress database.

Deliverability

splitforms uses dedicated SMTP with SPF/DKIM out of the box. Contact Form 7 uses `wp_mail()` / PHP `mail()` by default, which has poor deliverability without a separate SMTP plugin.

Spam protection

splitforms uses an AI classifier on top of honeypot. Contact Form 7 needs Akismet or reCAPTCHA add-ons for spam filtering.

Webhooks

splitforms unlocks HMAC-SHA256 signed webhooks (single delivery attempt, 8-second timeout) on paid plans. Contact Form 7 has no webhook support without add-on plugins.

API

splitforms ships an open REST API and MCP server on every plan. Contact Form 7 has no documented public REST API for submissions; you're querying the WordPress database directly via Flamingo or another storage add-on.

Maintenance

splitforms is fully managed — no plugin updates, no PHP version compatibility, no WordPress security perimeter. Contact Form 7 plus its companion plugins (Flamingo, WP Mail SMTP, Akismet, reCAPTCHA) is a multi-plugin stack you maintain inside WordPress.

• “A submission disappeared and I have no record of it.”

  splitforms stores every submission permanently. Contact Form 7 by default sends an email and forgets.

• “My contact-form emails are landing in spam because PHP `mail()` is unreliable.”

  splitforms uses dedicated SMTP with SPF/DKIM out of the box.

• “I'm getting flooded with bot submissions.”

  splitforms runs every submission through an AI classifier specifically trained on modern LLM-written form spam.

• “I need submissions in my CRM via webhook.”

  splitforms includes HMAC-SHA256 signed webhooks (single delivery attempt, 8-second timeout) on paid plans. Contact Form 7 needs add-on plugins for any webhook delivery.

• “I want a real dashboard to search and export submissions.”

  splitforms ships one on every plan. Contact Form 7 needs the Flamingo companion plugin, and even then the search and export surface is thinner.

• “I want to move off WordPress and my forms are stuck.”

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

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

  splitforms ships an MCP server natively. Contact Form 7 has no equivalent.

Contact Form 7 is genuinely free, and that's hard to argue with. The honest cost calculation is in the surrounding stack: to get anywhere near splitforms's feature surface, you need Flamingo (storage), WP Mail SMTP (deliverability), Akismet or reCAPTCHA (spam), and a webhook add-on (integrations). Each plugin is its own update cycle, its own PHP-compatibility constraint, its own potential security surface, and its own debugging path when something breaks.

splitforms's free tier is also $0 — 500 submissions/month with a real dashboard, AI spam filtering, and dedicated SMTP. For a WordPress site owner who's already paying for premium SMTP service, premium anti-spam, and premium storage plugins, the question isn't 'free vs paid' — it's 'free plus four plugins plus maintenance burden' vs 'free plus a single managed backend.'

The honest test: if you've already installed Flamingo, WP Mail SMTP, and Akismet on top of Contact Form 7, you've effectively rebuilt the bottom half of splitforms inside WordPress. The question is whether you'd rather maintain that stack or have it managed for you.

Step 1: sign up at splitforms.com for a free access key — no credit card required. Step 2: replace the Contact Form 7 shortcode (`[contact-form-7 id="123" title="Contact form 1"]`) with a real HTML form on the page. For each Contact Form 7 field tag (`[text* your-name]`, `[email* your-email]`, `[textarea your-message]`), write a corresponding `<input>` or `<textarea>` inside `<form action="https://splitforms.com/api/submit" method="POST">`. Step 3: submit a test entry and confirm it lands in the splitforms dashboard.

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

If you were using Contact Form 7's mail-tags templating for the notification email subject or body, the splitforms equivalents are configured in the dashboard rather than in shortcode markup. Existing field names (your-name, your-email, your-message) carry over unchanged.

If you're already running a stable Contact Form 7 + Flamingo + WP Mail SMTP + Akismet stack on a WordPress site, the migration cost outweighs the benefit. The stack works, it's free, and the maintenance burden — once you've configured it — is low. Switching to splitforms means rebuilding the form markup in HTML, migrating any Flamingo data you care about, and re-configuring notification templates in a new dashboard.

Same answer if you specifically need to keep everything inside WordPress for security or compliance reasons — form data in your WordPress database, no third-party vendor with access to submission data, no external API surface. Contact Form 7 plus Flamingo keeps your submission data entirely inside your WordPress install's security perimeter. That's a real architectural choice for some buyers.

And if you're a hobby developer with a single WordPress site and a low-traffic contact form, Contact Form 7 is genuinely the simplest free option. The setup is one plugin install and one shortcode; no account, no dashboard, no external vendor. The friction tax of creating a splitforms account (no credit card, but you do need an email and a password) isn't worth paying for a form that gets two messages a month.

Is splitforms a true Contact Form 7 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. Contact Form 7 ships the form markup and mail logic, but you bring your own SMTP, storage, and spam stack.

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 outside WordPress entirely. The form action URL is host-agnostic.

Will my Contact Form 7 submissions carry over? By default Contact Form 7 doesn't store submissions — it sends an email and forgets. If you've been using Flamingo for storage, that data stays in your WordPress database; splitforms starts collecting from the moment you switch. You can backfill historical data through the open REST API.

Does splitforms require an SMTP plugin? No. splitforms uses dedicated SMTP with proper SPF/DKIM out of the box. No WP Mail SMTP plugin required.

What about Akismet for spam? splitforms uses an AI classifier that's specifically trained on modern form spam, including LLM-generated submissions. Most teams find it more accurate for new spam patterns than Akismet.

Is there a long-term plan? Yes — $59 for the 3-Year plan at 15,000 submissions/month for 36 months. Useful for a developer who wants a managed backend with no monthly billing and no WordPress plugin maintenance.