LanderKit

Templates written in French — fully translatable in minutes

How many form fields does a converting form need?

Published on 18 July 2026 · 9 min read

It is the most asked question in landing page optimisation, and a short answer does exist: for a lead-generation form, 3 fields is the sweet spot in most studies (HubSpot measured the best conversion rate on 3-field forms, across a sample of more than 40,000 forms). But the short answer is misleading: a 5-field form with well-chosen fields beats a 3-field form with poorly chosen ones, and there are cases where adding fields is the right call. Here is how to decide, field by field.

What the studies actually say

Three lessons stand out from the major industry studies (HubSpot, Unbounce, Baymard Institute, WPForms):

  • Friction is real but not linear. Going from 6 to 4 fields produces a clear gain; from 4 to 3 a smaller one; below 3 fields the gain becomes marginal. The first job is removing superfluous fields, not chasing a magic number.
  • Fields don't all cost the same. A "first name" field costs almost nothing. A required "phone" field can cut conversion by 5 to 39% depending on the study — visitors anticipate cold calls. A 15-option dropdown or an open question costs more than a short text field.
  • Volume and quality pull in opposite directions. Fewer fields = more leads, but less qualified ones. If your team calls every lead back, a qualifying field that filters out the merely curious saves real sales time — that is a business trade-off, not a UX rule.

The cost of each field, one by one

Indicative impact per field — synthesis of HubSpot, Baymard and WPForms studies
FieldConversion costWhen to ask for it
EmailNear zero (it's the price of entry)Always — often the only truly indispensable field
First nameLowIf you personalise your emails; otherwise remove it
Full nameLow to moderateQuotes, appointments, B2B — useless for a lead magnet
PhoneHigh (up to -39% when required)Only if you genuinely call back; otherwise make it optional and say why you ask
Company / roleModerateB2B with sales qualification; move it to step 2 if possible
Budget / timelineModerate to highA deliberate filter to receive only serious leads (quotes, services)
Free-text messageModerateClassic contact form; never required on a landing page
Postal addressVery highOnly when the service depends on it (trades, real estate, delivery)

The rule that sums up this table: ask only for what you need for the next step, not for the whole sales relationship. An email is enough to send an ebook. An email and a phone number are enough to call a prospect back. The rest can be collected later, once trust is established.

3 configurations that work, by goal

Email capture (newsletter, lead magnet, waitlist): 1 field

A single email field, a button that describes the reward, one line of GDPR reassurance ("No spam, one-click unsubscribe"). That is the configuration of our SaaS waitlist and newsletter templates: any extra field destroys value there, because the goal is subscriber volume, not qualification.

Appointment booking or quote request: 3 to 4 fields

First name, email, phone (with the reason stated: "to agree on a time slot"), possibly one short context field. That is the format of the coach & consultant template or the local business template. Here the phone field is legitimate — the visitor is explicitly asking to be contacted — but every field must still be justified by the next step.

Complex qualified lead: the two-step form

When you genuinely need 6 pieces of information or more (property valuation, financing file, custom project), split the form. Step 1: the easy, engaging questions (property type, surface area, postcode — clicks, not typing). Step 2: contact details. This split exploits two biases: step 1 is painless and creates commitment (sunk-cost effect — "I've already answered 4 questions, might as well finish"), and the contact details arrive once the visitor has already invested. Our property valuation template is built on exactly this pattern: two-step forms show completion rates 30 to 60% higher than equivalent long forms in published tests (Venture Harbour reports up to +59% on its own funnels).

The 6 rules that matter more than field count

  1. Never a required phone field without a displayed reason. If it is optional, say so explicitly ("optional"): an unmarked optional field is treated as required by visitors.
  2. A label above the field, not a placeholder that vanishes on typing — Baymard ranks this among the costliest mistakes on mobile.
  3. The right mobile keyboard: type="email", type="tel", inputmode="numeric". Typing an email on a standard alphabetical keyboard multiplies errors and abandonment.
  4. Error messages in the right place: under the field concerned, at input time, in human language ("This email looks incomplete") — never a global alert at the top of the page after submission.
  5. Reassurance right under the button: a line like "Your data will never be shared" under the CTA removes the last hesitation. The button copy itself matters enormously — we dedicate a full article to it: 12 CTA examples that convert.
  6. Measure abandonment, not just conversion: a tool like Microsoft Clarity (free) shows on which field visitors give up. That is the field to remove or push to step 2.

How to decide for your page

List your current fields and ask three questions for each: do I need it before the first contact? Can I get it later? What actually happens if I remove it? Any field that fails this interrogation disappears or becomes optional. Then measure for two weeks, and only then test a variant. The form is just one of the 12 optimisation levers of a page — for the full picture, reread our guide on increasing your landing page conversion rate, and check that your page follows the 9 sections of a landing page that converts: a perfect form won't save a page with a blurry promise.

The LanderKit templates apply these rules out of the box: 1-field capture on signup pages, 3 justified fields on booking pages, a two-step form on the property valuation page — with visible labels, correct mobile keyboards and reassurance under every button. You start from an already optimised form; all that's left is plugging in your email tool. And if you want to go beyond a plain email notification, plug the form into a ready-to-import n8n workflow: AI lead triage, database logging, automatic follow-ups — the FlowKit packs cover the whole chain after submission.

FAQ

Frequently asked questions

What is the ideal number of fields for a landing page form?

For lead generation, studies converge on 3 fields (the best conversion rate measured by HubSpot across more than 40,000 forms). For simple email capture, one field is enough. But which fields you keep matters more than how many: remove the required phone field and open questions first, before chasing a precise number.

Does a phone field really hurt conversion?

Yes — it is the most expensive field: when required, it can cut conversion by 5 to 39% depending on the study, because visitors anticipate cold calling. Three workarounds: make it clearly optional, explain why you ask for it ("to agree on a time slot"), or move it to the second step of the form.

Do two-step forms convert better than long forms?

In the vast majority of published tests, yes: 30 to 60% higher completion than the same form in one step. The key is the order: start with the easy, commitment-free questions (clickable choices, not typing), end with contact details. A visitor who invested in step 1 rarely abandons at step 2.

Do fewer fields degrade lead quality?

Yes, mechanically: less friction lets more window-shoppers through. If your team calls every lead back, a qualifying field (budget, timeline, project type) can pay off even if it reduces volume. The trade-off should be computed in cost per qualified lead, not raw conversion rate.

Should GDPR consent be a checkbox?

For a newsletter, an explicit, un-pre-ticked consent checkbox is the safest practice (usefully completed by double opt-in). For a contact or quote form, a clear information line with a link to your privacy policy is enough: replying to a visitor's own request does not require separate consent.

Read next

Related articles