Getform alternative (now Forminit): same HTML form, one new URL

The most common trigger is the form-count cap. Getform/Forminit's free plan is capped at 1 form, which pushes agencies running multiple low-volume client sites onto a paid plan for reasons unrelated to actual traffic. splitforms removes that ceiling entirely: unlimited forms on every tier, including Free.

The second trigger is price. Forminit Pro is $19/month (or $190/year) for 5,000 submissions a month and 15 forms. splitforms Pro is $5/month for the same 5,000 with unlimited forms, and the $49/year Annual plan covers 15,000 a month.

The third trigger is field naming. Forminit says existing Getform endpoints keep working, but new Forminit forms only store inputs named with the fi- prefix (fi-sender-email, fi-text-message), so rebuilding a form on the new setup means renaming fields. splitforms stores whatever input names your form already uses, ships HMAC-SHA256 signed webhooks (one retry after ~2s on network errors, timeouts and 5xx; not on 4xx; 8-second timeout), and an MCP server so AI agents can read and act on form data without a custom integration.

Free tier

splitforms 500 submissions total with unlimited forms; Getform/Forminit 100 submissions/month on 1 form. Forminit's allowance renews each month but covers one form; every splitforms plan, including Free, includes unlimited forms.

Form-count limits

splitforms has none on any plan. Getform/Forminit caps the free plan at 1 form, forcing an upgrade for agencies running more than one form.

Webhooks and API

splitforms ships HMAC-SHA256 signed webhooks (one retry after ~2s on network errors, timeouts and 5xx; not on 4xx; 8-second timeout), per-form webhook scoping, a REST API and an MCP server. Forminit also signs webhooks with HMAC-SHA256, retries failed deliveries and keeps delivery logs; its webhooks and REST API start on Pro.

Spam protection

splitforms uses smart spam filtering plus honeypot. Forminit has built-in spam filtering on every form, plus optional Cloudflare Turnstile, reCAPTCHA v3, hCaptcha, a honeypot and authorized domains.

Notifications

splitforms stores accepted submissions before attempting email; delivery and inbox placement depend on provider and recipient settings.

Host requirement

both work on any host. Forminit publishes setup guides for HTML, React, Next.js, Webflow, WordPress and more; splitforms works on Webflow and anywhere else as a regular HTML form action.

• “I'm hitting the 1-form cap on Free.”

  splitforms gives you unlimited forms on every plan, including Free. You scale by total submissions instead of paying for arbitrary tiny form buckets.

• “New Forminit forms want fi- prefixed field names.”

  splitforms accepts the input names your form already has.

• “My agency is running 30 client sites and the per-form pricing is killing margins.”

  splitforms gives you unlimited forms on every plan, including Free, and the $49/year Annual plan (15,000 submissions/month) for high-traffic clients.

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

  splitforms ships an MCP server that exposes submissions, webhooks, and configuration to AI agents natively.

• “I'm seeing AI-generated spam slip past CAPTCHA.”

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

Concrete numbers for an agency running 30 client sites, average 200 submissions/month per site, two to three forms each: with Getform/Forminit's 1-form cap on Free, nearly every client needs the $19/month Pro plan ($190/year) as soon as a second form or more than 100 submissions/month is needed. Annualized agency spend adds up fast across 30 sites, billed forever.

On splitforms, the same 30 sites can run on a mix of free tiers (small clients under 500 total) and the $5/mo Pro plan (anyone larger), with high-traffic clients on the $49/year Annual plan (15,000 submissions/month). Across 30 sites, the yearly difference adds up to thousands of dollars.

Beyond the price, the operational difference is real: no per-form planning constraint. You stop budgeting which forms a client "gets" and start treating forms as free. The accounting question becomes total submission volume across the agency, not form count per client — which is a much simpler number to forecast.

Step 1: sign up at splitforms.com for a free access key. Step 2: in each form's HTML, swap `https://getform.io/f/YOUR_ENDPOINT` in the action attribute for `https://splitforms.com/api/submit`. Step 3: trigger a test submission and confirm it lands in your dashboard.

If you have file upload fields, splitforms accepts the same `multipart/form-data` encoding Getform uses — your existing `<input type="file">` markup works without changes. Copy each webhook URL into the splitforms dashboard and update the receiver for the splitforms payload. For agencies, the recommended migration order is: pick one low-traffic client site, migrate as a pilot, run both endpoints in parallel for 24 hours, then roll out across the rest of the portfolio.

Day 1, minute zero: you open the Webflow project (or the Next.js repo, or the Astro site) and run `grep -r 'getform.io/f/' .`. In a typical agency setup you'll find the endpoint hardcoded in a Webflow form's action field via Designer, or referenced as `https://getform.io/f/abc123def` in a `components/ContactForm.tsx`. For Webflow: open Designer, select the form, replace the action URL with `https://splitforms.com/api/submit`, and add a hidden `access_key` field with your splitforms key. For a code-managed site: change the URL inline and include `access_key` in the form body. File upload fields keep their existing `multipart/form-data` markup — splitforms accepts the same encoding Getform does, so no field-name changes.

Minute fifteen: deploy the staging branch (`vercel deploy --target preview`, or in Webflow, publish to a staging subdomain). Trigger a real submission with a real email address and a real file attachment. Watch it land in the splitforms dashboard within seconds, including the file URL. Now run shadow mode: in your client-side form handler, fire a `Promise.allSettled([fetch(getformUrl, {...}), fetch(splitformsUrl, {...})])` so every production submission hits both backends for 24 hours. Compare the two dashboards — submission counts should match exactly, and you can sanity-check that file uploads, CC recipients, and any custom redirect URLs work identically before flipping the cutover switch.

Day 2: remove the Getform `fetch` call, leave splitforms as the sole backend, redeploy. Migrate Zapier triggers by re-pointing each Zap's webhook trigger at splitforms, then re-map fields, because the payload shape differs. Once the new path has run a full day clean, archive the Getform endpoint from their dashboard and downgrade the subscription. Splitforms's free tier (500 total, unlimited forms) covers the parallel shadow window for any single client, and Pro at $5/mo (5,000/month) or Annual at $49/year (15,000/month) covers a portfolio mid-cutover.

Is splitforms a true Getform alternative? Yes. Every core capability — POST endpoint, file uploads, dashboard, webhooks, spam filtering, custom redirects, CC recipients — is covered, with unlimited forms on every plan, including Free.

Does it work on Webflow? Yes. splitforms is just an HTML form action — Webflow's form element accepts it natively. Paste the splitforms URL into the form's action field and you're done.

What about file uploads? Yes, on paid plans (Pro and Annual). Standard `multipart/form-data` encoding.

Will my Zapier integration break? splitforms supports webhooks on paid plans; point a Zapier webhook trigger at the splitforms webhook URL and you have the same downstream automation.

Is there a per-form limit? No. Every plan — Free, Pro and Annual — includes unlimited forms.

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