WordPress plugin
Drop a [splitforms] shortcode anywhere on your WordPress site. No PHP, no glue code — install the plugin and connect in one step.
View WordPress plugin →A public, plain-text view of every meaningful piece of work in flight or queued at splitforms. No vague themes, no fake dates — just what we're shipping, what's next, and what we're considering. Vote by email; paying customers get the deciding vote on order.
Free plan: 500 submissions/month, no credit card. Pro: $5/mo. 3-year plan: $59 for 3 years, then $59/year, 36 months of access. See full pricing.
Active engineering work this quarter.
Submission rate, drop-off, referrer, and UTM breakdowns scoped per form. Exportable as CSV or piped into your analytics stack via webhook.
Committed to ship in the next two quarters.
Point forms.yourdomain.com at our submit endpoint with a single CNAME. Pro and 3-year plans, no extra charge.
Forward uploaded files (not just metadata) into Slack and Discord channels alongside the submission body.
One-line <script> tag that mounts a styled, themable form on any page. For teams that don't want to hand-write HTML.
Native ConvertKit, Beehiiv, and MailerLite destinations. Subscribe a contact and post the submission in one step.
Save drafts of form configs, diff against the live version, and roll back any change. Audit log included.
Custom auto-responder copy per form, with markdown support and variable interpolation from submission fields.
Notify Bing IndexNow and submit canonical URLs to Google Search Console automatically when forms ship on a customer domain.
Free public tool that audits any form on the public web for accessibility issues — labels, focus order, error messaging, contrast.
Credible directions we're investigating.
Open-source core that small teams can run on their own infra. Same wire protocol, same dashboard, BYO database.
Chain plain HTML forms across pages with state preserved server-side. Works without JavaScript on the client.
Show or hide fields based on the values of other fields. Per-form rules editor; no code.
Brand the splitforms dashboard with your agency's logo and palette. Per-client workspaces, per-client invoicing.
Triage submissions, mark as spam, reply, and assign — all from inside Slack. No dashboard switching.
Native mobile app for the submissions inbox — push notifications, swipe-to-archive, offline reading.
Drop a [splitforms] shortcode anywhere on your WordPress site. No PHP, no glue code — install the plugin and connect in one step.
View WordPress plugin →Storage-backed file uploads with per-plan quotas and signed download links — 5 files per submission at 5 MB each on paid plans.
View File uploads (Storage integration) →Automatic retry on transient failures, plus a 30-day delivery log with per-attempt status, errors, and one-click replay of the original submission.
View Webhook retries & delivery log →Honeypots, timing traps, and AI scoring rank every submission for spam intent before it reaches your inbox. Suspected spam is quarantined, not deleted.
View AI spam detection →Charge a card on submit — for paid contact, deposits, paid waitlists, or order forms. Connect your own Stripe account, set an amount per form, submitters pay through Stripe Checkout. Money goes straight to your Stripe account.
View Stripe-payment forms →Crawlable index of sites running on splitforms — eight categories, free to be listed.
View Public showcase gallery →Production-ready HTML form snippets — contact, newsletter, lead, RSVP, support, feedback, beta, job, quote, demo.
View 10 copy-paste embed templates →Paste HTML, audit spam resistance, labels, accessibility, and form-backend wiring, then copy a safer version.
View Contact form spam checker →One-time $59 payment, 36 months of access, 15,000 submissions/month. Replaces the previous longest plan.
View $59 3-year plan →Added a $5/month Pro tier with 1,000 submissions and 10 forms, while keeping Free at 500 submissions with no credit card required.
View Starter tier added at 1,000 submissions/month →Per-form webhook destinations with HMAC-SHA256 signing and auto-formatted delivery to Slack, Discord, Telegram, and WhatsApp. Last delivery status shown per webhook; retries and a full delivery log are in progress.
View Outbound webhook delivery →The roadmap order is set by what users actually request, not by what we think would be neat to build. Every email and every dashboard feature-request gets read; recurring asks promote themselves into the "Next" column once we've heard the same thing from enough independent people. We log requests against a small spreadsheet, not a public leaderboard, because public leaderboards reward early-bird brigading more than they reward genuine demand.
Paying customers carry more weight in the order, not the contents. A Pro customer asking for ConvertKit integration counts more than a free-plan user asking for the same thing — not because their feature is more important, but because they've put real money behind the claim that they'll use it. We don't bump items from "Later" to "Now" for a single paying user; we adjust the order of items already in "Next."
We also reserve roughly a third of every cycle for technical debt — boring rewrites, perf work, schema cleanup, dependency upgrades. Public roadmaps tend to bias toward shiny-feature maximalism, and most form-backend competitors got into trouble by chasing features past the point where the underlying platform could carry them. We'd rather ship two features and one quiet rewrite than four features and a quietly-rotting core.
Email us with the feature, the use case it solves on your site, and (optionally) which competitor handles it well today. We read every message. Most additions to this page started as a single user email.
[email protected]The page is regenerated on every deploy, and we deploy multiple times per week. New cards appear as we start work; cards move to Shipped only after the corresponding feature lands in production. We publish the matching changelog entry at /changelog the same day a feature ships.
For now, voting is by email — send your top picks (and any context about how you'd use them) to [email protected] with the subject line 'Roadmap'. We tally votes manually for each planning cycle. A proper in-dashboard voting UI is on the roadmap itself; until then, email is the canonical channel.
Yes on ordering, not on secret access. Paid plans influence the sequence of items already in 'Next'; they never buy a private queue or a jump straight from 'Later' to 'Now'. Free-plan users are heard too, especially when a request overlaps with work already underway. See 'How we prioritize' above for the full logic.
We don't accept paid feature placements. The roadmap order is set by user demand and engineering reality, not by sponsorship. If you have a compelling commercial use case (annual contract, multi-seat, a public case study), we're happy to talk — but the conversation is about whether your need is real, not about a fee.
Some get promoted to 'Next' as demand stacks up; some get rewritten when we learn what users actually mean; some get dropped quietly. We do not commit to building everything in 'Later'. The column is a public scratchpad of credible directions, not a delivery contract.
Either we haven't heard about it from enough independent people yet, or we've decided it's a poor fit for the splitforms shape (e.g., we're not building a full survey/quiz product). Either way, email [email protected] — every suggestion is read, and repeated asks earn a place on the board.
An RSS feed at /changelog.xml is on the near-term plan. Until it ships, the /changelog page is reverse-chronological and stable enough to be polled or screen-scraped. The /roadmap page itself updates in place — subscribe to changelog and you'll see roadmap items announced as they ship.