How many fields should a form have? Counts from 140 finished forms

A form should have as many fields as the decision it feeds, and on this site that number has a clear centre. Counted on 13 September 2026 across the 140 finished form examples, the median form carries 15 fields, the shortest carries 4 and the longest carries 29. Half of all forms fall between 11 and 18. The spread is not random: it follows the kind of form, and the table under this article shows how far.

The dataset behind the counts

The corpus is every form example published under /examples/forms/: 140 forms, 100 of them classic page forms and 40 conversational forms that ask one question per screen. Between them they hold 2,073 labelled fields. Each form is stored as a list of fields with a kind, a label and a required flag, so the counting is mechanical rather than a judgement made by eye.

Three rules decide what counts. A field is anything a respondent answers, so section headings are excluded. A composite field counts once: a full name with title, first and last parts is one field, an address block is one field, a table of referees is one field, and a rating grid of six statements is one field. Paragraph blocks and images are not fields at all.

Each form was then placed in one of eight types by the words in its name, so every form with “intake” in it is an intake form and every form with “application” or “nomination” is an application. The rule is published in the method so the grouping can be checked, and it is blunt on purpose: a gym membership form sits with registrations because it signs a person up.

This is what the examples on this site contain, not a sample of every form on the internet. The corpus grows as new examples are built, and the counts will be rerun when it does.

Field counts by form type

The table ranks the eight types by median field count, and the ranking reads like a scale of consequence.

At the top are forms that create a record somebody relies on later. Workplace requests have a median of 19 fields, because a leave request, a payroll change or an IT access request has to carry enough detail for a second person to approve it without a conversation. Intake and client records sit at 18: a clinic cannot treat safely without a history, and the patient intake form runs to 25 fields for that reason.

In the middle are applications at 15 and reports and claims at 16. These forms screen or decide, so each field has to earn its place by changing an outcome.

At the bottom are the forms a person fills in by choice and can walk away from. Registrations sit at 12, bookings and enquiries at 11 and surveys at 9. The contact us form is 8 fields: name, email, how to reply, an optional phone number, a subject, an optional order number, the message and an optional screenshot. Nothing on it exists for the business’s filing.

The same pattern shows inside types. Registrations range from a 6 field newsletter signup to a 29 field summer camp enrolment, and the long end of that range is where a child will be in somebody’s care.

How much of each form is required

Across all 2,073 fields, 76% are marked required. The typical form requires 80% of what it asks, 13 forms require every field, and 9 require fewer than half.

The required share climbs with stakes, not with length. Applications require 85% of their fields, the highest of any type, because an incomplete application cannot be assessed and the applicant usually wants to be assessed. Consent and checks follow at 82%. Surveys are lowest at 66%, and that is the right answer for them: an optional open question at the end of a survey still gets answered by the people with something to say.

The low outliers are deliberate. The event RSVP form requires 2 of its 8 fields, because a guest who is not coming should be able to say no and leave. The payroll change form requires 7 of 22 because a person changing only their bank account should not be made to retype their address and super fund.

The longest and shortest forms

The longest forms in the corpus are a summer camp registration at 29 fields, a rental application at 27, a patient intake and an exhibitor booking at 25, and three forms at 24: a course enrolment, an employee onboarding form and a training request. Every one is a classic page form, and every one is broken into four to seven sections: the camp enrolment groups its 29 fields under which weeks, the camper, who may collect, health and consent.

The shortest is the NPS survey form at 4 fields: the 0 to 10 question, the reason, permission to reply, and an email if permission is given. Behind it come a customer feedback survey, an employee pulse survey and a newsletter signup at 6 fields each. All four are conversational.

That split is the clearest single signal in the data. Classic forms have a median of 16 fields and conversational forms a median of 10. None of the 40 conversational forms goes past 16 fields. Surveys are 89% conversational; intake records, reports and consent forms are entirely classic.

What the numbers say about length

Three things stand out once the counts sit side by side.

Length follows accountability. The forms with the most fields are the ones where a missing answer causes harm or a dispute later: a child’s allergy, a tenant’s rental history, a contractor’s licence. Baymard’s checkout research found most checkouts need only 8 fields yet average 11.3; the equivalent waste in this corpus would show up as optional fields that no approver reads, and the low required shares on long forms are where to look for it.

Format follows length. Conversational forms stay short because one question per screen turns every field into a tap. Once a form needs a table, a signature or a long record, it moves to a classic page. The data does not show conversational forms being better, only that they are used for a different job.

Required marks follow intent. A form a person wants to finish, such as an application, can require nearly everything. A form a person is doing you a favour by filling in, such as a survey, should require the minimum.

How to apply it to your own form

Start from the median for your type in the table and treat it as a check, not a target. If you are above it, go field by field and ask what decision each one changes. Nielsen Norman Group’s guidance puts it bluntly: remove fields whose answers can be derived another way, collected later, or simply omitted. In Australia, the Privacy Act’s collection principle adds a second test, because an organisation may only collect personal information that is reasonably necessary for what it does.

If you are well below the median, check you have not pushed a question into an email chain that should have been a field. A booking form that omits dietary needs saves one field and creates twenty replies.

Then decide the format. A form under about 12 fields that people will open on a phone suits a conversational layout; a form that needs sections, tables or a signature suits a classic page. Conversational forms explains the difference in a paragraph.

The AI form builder writes a first draft from a description, and the guide to creating a form with AI walks through editing its fields. If completion is the problem rather than length, the post on how to improve form completion rate covers the other levers.