Form Backend vs Form Builder: What's the Difference?

The short answer

A form builder gives you a drag-and-drop UI to create the form. You design it inside their tool, then embed the result on your site as an iframe or hosted link. The form lives on their domain. Examples: Typeform, Tally, Jotform, Google Forms.

A form backend gives you an endpoint that receives HTML form submissions. You write the form yourself, point its action attribute at the endpoint, and the service handles the submission (email, storage, spam filtering). The form lives on your domain. Examples: splitforms, Formspree, Web3Forms, Basin.

Different jobs, different trade-offs. Pick the form builder if you can't (or don't want to) write HTML and you need conditional logic, payments, or a visual editor. Pick the form backend if you can paste an HTML snippet and you want the form on your own domain with your own design.

Side-by-side comparison

When to pick a form backend

• You have a static site or SPA (Astro, Next.js, Hugo, Webflow, Carrd, GitHub Pages).
• You want the form to live on your own domain for SEO and trust.
• You care about the form looking exactly like the rest of your site — fonts, colors, spacing.
• You only need a contact form, lead form, or simple data capture — no quizzes, no payments, no branching.
• You're cost-sensitive. Free tiers are 10–20× larger than form-builder free tiers.
• You're comfortable pasting HTML into a page (or your no-code tool accepts embed code).

Read: Add a Contact Form in 60 Seconds, What Is a Form Backend?.

When to pick a form builder

• You can't (or don't want to) write HTML. Typeform's editor is genuinely faster for non-developers.
• You need conditional logic — branching questions, skip patterns, scoring quizzes.
• You're building a multi-step survey with progress bars, page transitions, and partial save.
• You need payments tied to the form as a single flow.
• You want built-in analytics on form completion rates, drop-offs per question, etc.
• You're happy with the form living on the builder's domain (or you don't mind the iframe trade-off).

Compare specific builders: Typeform vs Jotform, Tally vs Typeform, Google Forms vs Typeform vs Splitforms.

The hybrid approach: use both

You don't have to pick one tool for everything. A typical SaaS stack in 2026 uses:

• Form backend (splitforms) for the contact form, demo request, and waitlist signup on the marketing site — short forms, on-brand, fast to set up.
• Form builder (Tally or Typeform) for the long onboarding survey, NPS survey, and customer feedback form — branching logic, completion analytics.

Each tool does what it does best. The cost is still under $40/month combined for most indie companies.

Decision framework: when to pick which

If you are still unsure, answer these four questions:

1. Can you paste HTML into a page? If yes, a form backend is viable. If no, you need a form builder.
2. Do you need conditional branching, multi-step pages, or payments in the form? If yes, use a form builder. If no, a form backend handles the simple case.
3. Does the form need to live on your domain for SEO or branding? If yes, use a form backend. If the form is a one-off survey where URL does not matter, a builder is fine.
4. Are you submitting more than 100 forms/month? If yes, a form backend is dramatically cheaper. If under 10, both are effectively free.

This maps to a simple decision flow. Non-developers with complex form needs go to Typeform or Tally. Developers or anyone who can paste HTML, building contact or lead forms on their own domain, go to a form backend. Teams with both needs use a hybrid setup.

Migration guide: switching from form builder to form backend

If you already have a Typeform, Jotform, or Tally embed and want to move to a form backend, the migration is straightforward. You are replacing an iframe with native HTML on your own domain. Here is the process:

1. Copy your form fields. List every field from the builder — names, types, required status, placeholder text, and any conditional logic. This is your source of truth.
2. Recreate the form as HTML. Use the splitforms HTML form generator or write the HTML manually. For simple forms (under 7 fields), this takes about 10 minutes.
3. Replace the embed code. Remove the iframe or script tag from your page and paste the new form HTML in its place. Style it with your site's existing CSS classes.
4. Configure the backend. Create a form in splitforms, set the email recipient, enable spam protection, and add your domain to the allowed list.
5. Redirect the old form URL. If the form builder was on a separate page (like yoursite.com/apply pointing to typeform.com), update that page to render the new HTML form instead. If the iframe was inline, the URL does not change.
6. Test both versions temporarily. Keep the old form accessible for a week while you confirm the new one delivers submissions correctly. Then remove the old embed.

The only part that needs attention is conditional logic. If your Typeform had branching questions ("if answer is A, skip to page 3"), you need to implement that in client-side JavaScript or accept that the new form will be a flat single-page form. For most contact and lead forms, there is no branching to recreate.

Cost comparison: TCO at different submission volumes

The free-tier comparison is well-known, but total cost of ownership over a year is the real number. Here is what you pay across different submission volumes, including the hidden costs:

At the low end (under 1,000 submissions), the form backend is free while builders charge $29/month. At scale, the gap narrows in absolute dollars but remains large in percentage terms. A form backend at 50,000 submissions costs roughly a fifth of what Typeform charges. The comparison does not include hidden costs like the developer time spent integrating builder iframes, the performance overhead of loading a third-party widget, or the SEO value of having the form on your own domain. See splitforms pricing for the full plan breakdown.

The SEO impact people forget

When you embed a Typeform iframe on yoursite.com/contact, the form HTML is served from typeform.com. Google sees an iframe on your page, not a form. You miss out on:

• ContactPage structured data signals.
• Form-field keywords being indexed as part of your page content.
• Trust signals — visitors on a sensitive form (lead, payment, support) seeing the iframe's domain change in dev-tools or address-bar copy/paste.

For lead-generation pages where contact form ranking matters, a form backend keeps everything on your domain.

FAQ

Where to go next

• Try splitforms free — 500 submissions/month, no credit card.
• Read What Is a Form Backend? for the full definition.
• Compare Formspree vs Tally vs Splitforms for a real-world matchup.
• See top 10 form-to-email services.