Website form fields have a habit of piling up. Most forms start small: a name and an email. Then someone in sales wants the phone number. Marketing wants the company size. Someone else wants to know how they heard about you. A year later the contact form has nine fields, and nobody remembers who asked for the last five.
Every one of those fields is a small ask of the person filling it in. Here’s what the research actually says about how many is too many, and how to decide which fields stay.
Quick summary, if you’re short on time:
- Baymard Institute’s 2024 checkout research found the average checkout asks for 11.3 form fields, while “most sites need only 8.”
- Baymard also found that what matters most is the number of fields users must consider, not the number of steps.
- Google’s web.dev guidance is blunt: “Don’t ask for data you don’t need! The simplest way to reduce form complexity is to remove unnecessary fields.”
- Google also says to use a real label on every field, never a placeholder alone, and to add autocomplete attributes where they exist.
- There’s no magic number that applies to every form. The right count depends on what the person is getting in return.
Jump to a section:
- What the data actually says
- Why there’s no magic number
- How to decide which fields stay
- Making the fields you keep easier
- A prompt to trim your form fields
- Questions worth answering directly
What the data actually says
Baymard Institute’s checkout research is one of the few sources that measures this properly instead of guessing. Its 2024 analysis found the average checkout flow shows 11.3 form fields, slightly down from 11.8 in 2021 and 12.7 in 2019. Its conclusion is that “most sites need only 8 form fields in total.”
The more useful finding is what Baymard says drives the experience. It isn’t the number of steps or pages. It’s “the number of form fields users must consider.” A short form spread over three screens can feel heavier than a slightly longer form on one.
One honest caveat: this is checkout data, where the person already wants to buy. A contact form or quote request is a different situation, and Baymard’s numbers shouldn’t be read as a rule for lead forms. What carries over is the principle. Fields you don’t need are friction you’re choosing to add.
Why there’s no magic number
You’ll find plenty of articles claiming exact conversion drops at five fields, seven fields or ten. Most trace back to aggregated benchmarks with no clear method behind them, so we’ve left those numbers out. What holds up is simpler: a person will share more when they clearly get more back.
Someone requesting a quick callback will tolerate two fields. Someone asking for a detailed website quote will reasonably expect to describe their project. Google’s own guidance frames it the same way, saying to collect extra data “only when users see a clear benefit from providing that data.”
How to decide which fields stay
Go through the form one field at a time and ask a single question: what will we do with this answer this week? If the honest answer is “nothing yet” or “we might want it later,” the field is a candidate to remove.
Three checks help:
- Can we get it another way? Company size can often be found later. A phone call can collect what a field would have.
- Does anyone read it? If nobody acts on the answer, it’s decoration.
- Does it change our reply? A field like “what do you need help with” changes what you say. “Job title” usually doesn’t.
Also avoid doubling up. Google’s guidance notes that forcing people to enter the same value twice, like an email address, “might reduce errors for a few users, but causes extra work for all users.”
Making the fields you keep easier
Once the list is trimmed, the remaining fields should be effortless. Google’s form best practice guide covers the two mistakes we see most often.
First, labels. It says not to use placeholders on their own instead of labels, because “once you start entering text in an input, the placeholder is hidden, so it can be easy to forget what the input is for.” Keep a visible label above every field.
Second, autocomplete. Google’s advice: “If an appropriate autocomplete value is available for a form field, you should use it.” That lets the browser fill in a name, email or phone number in one tap, which matters most on a phone.
A short form also needs a button that makes sense. Where that button sits and what it says is covered in our post on CTA placement, and it works best when the form is visible without scrolling, as we explain in above-the-fold design.
A prompt to trim your form fields
Every extra field can cost you a lead. The prompt below helps you decide which fields you really need. Fill in your form details, then test the shorter version yourself.
Act as a conversion-focused web editor. Help me trim my contact form.
My form:
– What the form is for: [quote request, booking, callback]
– Fields I have now: [list them]
– What I actually need to reply well: [describe]Please do the following:
1. Say which fields I can remove or make optional, and why.
2. Suggest any field I could add only if it truly helps me reply.
3. Write a short line to put above the form that explains what happens next.Rules:
– Do not assume things about my customers that I did not tell you.
– Keep the form as short as reasonable.
– Use plain words.
Make the change, then compare form submissions for a few weeks. Keep the shorter form if enquiries hold or improve.
Questions worth answering directly
How many fields should a website contact form have?
There’s no single correct number. Ask only for what you’ll use in your first reply, which for many small businesses is a name, a way to contact them and a short message. Baymard’s checkout research found most sites need only 8 fields even for a full checkout, so a contact form should usually be well under that.
Is a multi-step form better than a long single form?
Not automatically. Baymard found that the number of fields a person must consider matters more than the number of steps. Splitting a form into steps doesn’t help if the total number of fields stays the same.
Should I use placeholder text instead of labels?
No. Google’s guidance says not to use placeholders on their own instead of labels, because the hint disappears once someone starts typing and people forget what the field was asking for. Use a visible label and keep the placeholder for an example only.
Do fewer form fields always mean more enquiries?
Not automatically. There’s no magic number, and Google’s guidance is to collect extra data only when people see a clear benefit from giving it. Baymard’s data is from checkout, so use it as a principle for other forms, not a fixed rule.
Should I ask for a phone number on a contact form?
Only if you’ll use it in your first reply. Ask what you’ll do with the answer this week, and whether you could get it another way. A phone call can collect what a field would have.
Should I ask people to type their email twice?
Google’s form guidance says double-up inputs might reduce errors for a few users but cause extra work for all users. For most contact forms one email field, clearly labelled, is enough.
Where this actually matters
A form is the last step between a visitor and an enquiry. Every unnecessary field is a small reason to close the tab, and most of them exist because nobody ever questioned them. Trimming the list is one of the cheapest improvements a website can get.
Not sure whether your own forms are asking for too much? We review this as part of every website development project we build.
