5 Form Builders with Conditional Logic: Features and Examples
Compare field visibility, section branching, calculations, and routing in five form builders, with a practical FormBuilder example and a checklist for testing every path.
A form builder with conditional logic changes the questions a respondent sees based on earlier answers. For a contact form, that might mean showing a phone-number field only when someone chooses a phone call. For a longer survey, it might mean sending someone to a different section.
Start with the behavior you need. FormBuilder supports field-level show/hide rules. Google Forms branches between sections. Microsoft Forms branches forward through questions or sections. Jotform offers several condition types, including page skipping and calculations. Typeform combines branching with a visual logic map. Those are different capabilities, even when each product calls them “conditional logic.”
This comparison is published by FormBuilder, one of the products below. We checked our implementation and the linked providers’ documentation on October 7, 2026. The examples are practical configurations, not a claim that we ran a controlled benchmark of all five products. Plan limits and availability can change.
Compare the kind of logic you need
| Form builder | Useful starting point | Key distinction | Free-plan note |
|---|---|---|---|
| FormBuilder | Show a follow-up field when an answer matches | Field visibility, calculations, and submission routing are configured separately | Conditional logic; 5 active forms and 100 responses/month |
| Google Forms | Send different answers to different sections | Answer-based section navigation works on multiple-choice and dropdown questions | Available with a Google account |
| Microsoft Forms | Skip forward to a relevant question or section | Branching must go forward, not back to a previous question | Check the limits for your personal or organization account |
| Jotform | Combine field conditions with page navigation or calculations | Offers distinct condition types for these actions | Check its current Starter allowances before publishing |
| Typeform | Design a branching, one-question-at-a-time questionnaire | A visual logic map helps review the paths | Logic included; 10 responses/month |
1. FormBuilder: field visibility with a draft-first workflow
FormBuilder is a practical choice for contact forms, inquiries, registrations, and feedback forms where some questions apply only to certain people. Start with a template or describe the form to the AI form generator. Review the questions and rules in the editor before you publish.
Worked example: ask for a phone number only when needed
Create a required Radio Button or Dropdown question called How should we contact you?, with Email and Phone as its options. Add an email field and a phone field after it.
- Select the phone field, because that is the field whose visibility should change.
- In Conditional Logic, choose + Add Condition.
- Choose Show, select How should we contact you?, choose equals, and enter Phone as the value.
- Select the email field and add the equivalent show rule for Email.
- Preview both answers, then change an answer you already selected to confirm the form updates correctly.
| Respondent’s answer | Email field | Phone field |
|---|---|---|
| No answer yet | Hidden | Hidden |
| Shown | Hidden | |
| Phone | Hidden | Shown |
| Change Phone to Email | Shown again | Hidden again |
This example uses one condition per field. The rule engine supports matching all or any conditions; the field editor’s added condition rows use all matching conditions by default. Keep your initial rules simple and check the saved behavior before combining dependencies.
Separate visibility from calculations and routing
A show/hide rule controls a field. It does not itself jump to another page, calculate a total, or select an email recipient. Multi-page forms organize a long form into steps; calculation fields handle formulas separately. Review each configuration in its own settings.
Submission routing is also separate from what respondents see. The builder provides routing rules for notification recipients and post-submit redirects. Configure and test those destinations explicitly. An ordinary email notification does not automatically choose a team from an answer just because a visibility rule exists.
Limits and fit
The Free plan includes 5 active forms, 100 responses per month, and conditional logic. It works well for trying the contact-preference example before moving a real intake process over. Check the current pricing page for higher allowances.
Choose FormBuilder when field-level follow-up questions and editable drafts fit the job. If your central requirement is a visual branching map or explicit skip-to-page rules, compare those capabilities directly before choosing a tool. AI drafts still need a human review of fields, rules, and required answers.
2. Google Forms: section-based branching
Google Forms can direct respondents to a section or end the form based on an answer. Its Go to section based on answer control is available for multiple-choice and dropdown questions. Create the sections first, then assign the destination for each answer. Google’s branching guide explains the supported question types.
This is a useful fit when, for example, volunteers and attendees need different sections of an event survey. Plan your section structure first; section navigation is a different workflow from toggling an individual follow-up field on the same page.
3. Microsoft Forms: forward branching
Microsoft Forms lets you add branching from a question or section. You choose where an answer should send the respondent next. Its important constraint is direction: branches must lead to a later question or the end of the form. A backward branch can break the intended experience. See Microsoft’s branching instructions.
It is worth considering when your organization already uses Microsoft Forms and your survey can follow a forward-only sequence. Sketch the question order first, then test each route after you rearrange questions. Verify the account limits that apply to your Microsoft plan.
4. Jotform: multiple condition types
Jotform’s Conditions area separates actions such as showing or hiding fields, updating or calculating values, skipping or hiding pages, changing a thank-you page, and changing an email recipient. Its conditional-logic guide documents these options.
That makes it a candidate when a workflow requires several kinds of rules. For a multi-page form, check its page-skipping instructions and test the interaction between rules. Compare the current pricing and plan limits against expected submission volume, storage, and any payment requirements instead of relying on an old starting-price quote.
5. Typeform: branching with a visual map
Typeform provides logic on its Free plan and a visual logic map for reviewing the paths through a form. It is a candidate when you want to inspect how a conversational questionnaire branches. Its Logic overview explains the workflow.
The Free plan currently allows 10 responses per month. That can be enough to evaluate a small branching prototype, but it is a meaningful constraint for a live intake form. See Typeform’s Free-plan details and its current pricing. Our free Typeform alternative comparison puts the relevant FormBuilder allowances alongside it.
Test every path before publishing
A form that works on the first answer can still fail when someone changes their mind. Use this checklist with any of the five tools:
- Start with blank answers and confirm the intended initial state.
- Try every choice that controls another field or section.
- Change an earlier answer after entering a follow-up response.
- Check that hidden required questions do not block the intended route.
- Review the submitted response as well as the preview.
- Test notification and redirect rules separately, using destinations you control.
- Repeat the main paths on a phone-sized screen.
For the example above, the expected result is simple: Email shows the email field, Phone shows the phone field, and switching the choice switches the follow-up. Start there before adding extra rules.
Draft a form with AI or browse form templates, then review the logic in the editor.