Forms · Compared

Form field vs component vs block

A form field is any part of a form that collects an answer, such as a text box, a date picker or a set of radio buttons. A component is the general word for anything placed on a form, fields included. A block is a component that only displays something, like a heading or an image.

The words sound interchangeable, but the difference decides what becomes a column in your data, what can be marked required and what counts as a question when you estimate how long a form takes. Forms built without the distinction look complete on screen and export badly.

Nuwan Madhusanka · Co-founder

6 min read · Published 13 September 2026

The 41 component types in this builder, grouped
Group	Types	Collects an answer
Layout (5)	Heading, subheading, paragraph, divider, space	No
Input (7)	Short text, long text, number, full name, address, inline text with blanks, table	Yes
Choice (4)	Dropdown, radio buttons, checkboxes, rating matrix	Yes
Date and time (2)	Date picker, time picker	Yes
Advanced (4)	Photo upload, file upload, inline signing, e-signature	Yes
Media (2)	Image, video	No
Design (12)	Banner, card, badge, stat, chart, shape, list, quote, detail list, key values, data table, signature block	No
Outside the classic toolkit (5)	Email, phone, recording, profile, branding	Yes, except branding

Why the vocabulary drifts

The HTML standard talks about form controls, the inputs, selects and text areas a browser knows how to submit. Form builders then invent their own words on top: element, question, item, widget, block. Somebody asking for another field might mean a new question, a new heading or a new section, and a spec that says the form has thirty components tells you nothing about how much typing it involves. Settling on field for anything that holds an answer and block for anything that does not removes most of that confusion, and component stays as the umbrella for the whole toolkit.

What makes something a field

A field has a value. That one property brings everything else with it: it needs a label tied to it so a screen reader can announce what to enter, it can be required, it can carry validation rules such as a length or a range, and it produces something to store and export. Composite fields complicate the picture slightly. An address or a full name is one field made of several parts, and a rating matrix is one field made of several statements. They are one component on the canvas and one answer in the data, which is convenient for layout and matters later when somebody wants to chart a single part.

What blocks are for

Blocks carry structure and meaning. A heading tells people a new topic has started, a paragraph explains why a sensitive question is being asked, an image shows the product being registered, and a divider marks a break without adding a question. Accessibility guidance treats this structure as part of the form, recommending that related fields are grouped under a visible caption and that instructions sit where people will read them before answering. On paper forms that work was done by boxes and bold type; on a web form it is done by blocks, and a form with none reads as one undifferentiated list.

Mistakes the confusion causes

Putting a question inside a heading, so it looks asked but has nowhere to answer. Using a display table where an input table was meant, so respondents see a grid they cannot type into. Treating a signature block, which prints lines for signing on paper, as though it collects a signature. Counting blocks as questions when estimating completion time, which makes a short form sound long. And writing essential instructions as help text on a field in a builder that does not display that text, which hides them from the people who need them most.

Choosing the right component for each ask

Start from the answer you need rather than from the toolkit. A date needs a date picker, not a text box where people type dates in five formats. A choice between known options needs radio buttons or a dropdown, because free text produces spellings nobody can count. Parts of an identity or a location need the composite field that collects them separately, so a missing postcode is obvious. Anything the respondent has to read first needs a block above the field it explains. Working through a draft form with that one test, answer or display, usually removes a few text boxes and adds a couple of headings, and both changes make the export cleaner.

How the 41 types split in this builder

The type list holds 41 components. The classic toolkit offers 36 of them across Layout, Input, Choice, Date/Time, Advanced, Media and Design, and the conversational toolkit offers 25. Profile and recording are conversational only; e-signature and the 12 design blocks are classic only. Email and phone render only on conversational forms, and neither toolkit offers them as standalone fields, so a classic form uses short text instead. Photo, inline signing and e-signature do not work on a published conversational form, where they fall back to a plain text box. On a published classic form, a field description is shown only on file upload and photo, so instructions belong in a paragraph block. Exports write one column per input field, and blocks never become columns.

Questions people ask

Is a question the same as a field?

Usually, but not always. One question can use several fields, such as asking for a start and end date, and one field can hold several questions, as a rating matrix does with its statements. When counting questions for a time estimate, count the decisions a respondent makes, not the components on the canvas, and count each matrix row as its own small decision.

Can a display block be marked required?

No. Required means an answer must be present before the form can be submitted, and a heading or an image has no answer to check. In this builder the server ignores display components when it checks required answers on a submission, so a required switch only means something on a component that actually collects a value from the respondent.

What is the difference between a table field and a data table block?

A table field is an input: the respondent types into named columns, row by row, within the row limits you set, and the filled rows are stored as the answer. A data table block is display only, a table of fixed content you write, such as a price list or a schedule. Choose by asking who types into it, you or the respondent.

Why is there no email field in the classic toolkit?

The classic form renderer does not draw standalone email or phone components, so neither toolkit offers them and a classic form collects an address in a short text field labelled for it. A conversational form can render both. Anything that writes form data directly, rather than through the builder, should use short text for classic forms.

How does a composite field appear in an export?

As one column, not several. An address is written with its parts joined by commas, a full name with its parts joined by spaces, and a matrix as each statement with its answer, separated by pipes. If one part needs its own column for sorting or charting, split that column in the spreadsheet or ask that part as its own field.

Should a form have more blocks or fewer?

As many as it takes to make each section obvious and no more. A heading per section and a short paragraph wherever a question needs a reason usually does it. Decorative blocks that repeat what a heading already says add scrolling without adding meaning, and on a phone every extra block pushes the next question further away.

Make one with forms

The button opens the generator with this use case already described. Change the wording to match your own.

Create a form with OneCraft

Sources

Written and checked by the OneCraft team. Last checked 13 September 2026.