Form builders software glossary and key terms
The language of form builders, from conditional logic and submissions to webhooks, payment fields and HIPAA, defined in plain terms and in the context that matters to a buyer.
Form builders look simple from the outside, but the buying decision hides a stack of jargon about logic, limits, billing and compliance. This glossary defines the terms you will meet while shopping for and running a form tool, in plain language and in the context that matters to a buyer.
For how these terms show up in price, see the pricing and cost guide; for rollout, the implementation guide; and for the ranked tools, our best form builders software hub.
The tool reviews linked below carry affiliate links marked rel="sponsored"; we may earn a commission. Our rankings are editorial and are never for sale. See our disclosure.
Form builder terms, defined
Rules that show, hide or change parts of a form based on earlier answers, also called branching or skip logic. It keeps forms short by asking only relevant questions and is one of the clearest lines between basic and paid tools.
A single input on a form, such as a text box, dropdown, date picker or file upload. Some tools cap the number of fields per form on lower tiers, so a complex form can push you to upgrade.
One completed entry of a form. Submissions are the main billing meter in this category, so the volume you collect each month usually decides which plan you need.
The cap on responses a plan accepts in a billing period. Free and entry tiers cap submissions, and crossing the cap can stop a form collecting or force an upgrade, so plan for your busiest month.
The person filling in your form. Worth distinguishing from a user, who is a member of your team with an editor seat; the two are billed very differently.
An editor account on the platform. Tools like Formstack and Cognito Forms price by seat or bundle only a few, so a growing team can raise the bill without adding a single form.
A form that shows one question at a time, the style Typeform made popular. It can lift completion on engaging surveys but feels slow for long, data heavy forms where a single page is faster.
A form split across several steps with a progress indicator. Breaking a long form into pages reduces the sense of effort and often improves completion on registrations and applications.
A field that computes a value from other answers, such as a quote, score or running total. Cognito Forms and Jotform are known for strong calculations; many simpler tools lack them.
A field that collects money through a processor such as Stripe, Square or PayPal. Some builders add their own percentage fee on payments taken through lower tiers, on top of the processor cut.
A percentage the form builder takes from each payment collected, separate from the payment processor fee. It often drops to zero on higher tiers, so heavy sellers should weigh upgrading to remove it.
A field that captures a typed or drawn signature on a form. Useful for consent and agreements, but for legally binding contracts a dedicated signature tool with an audit trail is usually the better fit.
A field that lets respondents attach documents or images. Plans often cap storage and per file size, so high volume or large files can be a hidden reason to move up a tier.
Filling fields in advance from a link or known data, so a respondent confirms rather than retypes. Prefill speeds completion and reduces errors on renewals and updates.
A field the respondent never sees that captures context such as a source, campaign or account id passed in the URL. Hidden fields tie a submission back to where it came from.
Letting a respondent stop partway and return later without losing entries. Important for long applications and intake forms, and often a paid tier feature.
A captured record of answers from someone who started but did not finish a form. It helps you see where people drop off and, where consent allows, follow up on abandoned entries.
Placing a form inside your own website rather than hosting it on the vendor page. Inline, popup and slider embeds are common; an embedded form keeps the experience on your brand.
Taking the vendor logo or "powered by" mark off your forms. Free plans usually keep the branding on; removing it is one of the most common reasons buyers move to a paid tier.
An automatic message a form sends to another system the moment a submission arrives, carrying the data with it. Webhooks let developers wire forms into custom workflows without polling.
A prebuilt connection to another app, such as a spreadsheet, CRM or email tool, often through Zapier or Make. Where data needs to go after a submission shapes which builder fits.
An automatic email or message sent to the respondent after they submit, such as a receipt or confirmation. Useful for registrations and orders; check whether it is on your tier.
Defenses against junk submissions, from CAPTCHA challenges to invisible honeypot fields and rate limits. Public forms attract bots, so good spam protection keeps your data clean.
If forms collect protected health information in the United States, you need a builder that signs a business associate agreement and offers HIPAA features, which sit on higher tiers. Treat compliance features as help, not legal advice.
The European data protection law that governs how you collect and store personal data. For forms it shapes consent wording, data retention and where responses are hosted; many builders offer features to support it.
The share of people who start a form and finish it. Length, logic and layout move it more than design polish, and it is the metric most worth watching as you refine a form.
How pricing terms show up across tools
Pricing as of June 2026; check each vendor for current pricing. Scores are editorial assessments against our form builders rubric, not vendor claims.
Go deeper
Conditional logic, sometimes called branching or skip logic, shows, hides or changes parts of a form based on what someone answers. It keeps forms short by asking only relevant questions, and it is one of the clearest dividing lines between basic free tools and paid builders.
A form builder is built to collect structured data and trigger actions, such as registrations, orders, payments or support requests, often with logic and integrations. A survey tool leans toward asking questions at scale and analyzing responses with reporting and statistics. Many products do both, so judge by the job rather than the label.
A submission limit is the cap on how many responses a plan accepts in a billing period. Free and entry tiers cap submissions, and crossing the cap can stop a form from collecting or force an upgrade. Estimate your busiest month, not your average, before choosing a plan. Verified June 2026; check the vendor for current pricing.
If your forms collect protected health information in the United States, you need a builder that will sign a business associate agreement and offer HIPAA features, which usually sit on a higher tier. Compliance features help you meet the law but are not legal advice; confirm your obligations with counsel.
One email when the rankings move. The shortlist, the tradeoffs, the price changes. No filler.