Choosing the Right Field Type (and Why It Changes Your Data)

Most people treat field type as a cosmetic choice — text box, dropdown, whatever. It isn't. The type you pick decides what people can enter, which decides what your data looks like when you go to use it. A "country" text field gives you USA, U.S., United States, and 🇺🇸. A country dropdown gives you one clean value every time.

Here's a practical tour of the field types we offer and the judgment behind each, drawn from the patterns we see in real forms.

Text: short vs. long

Short text is for answers that fit on a line: a name, a company, a job title. The single-line box itself signals "keep it brief."
Long text is for paragraphs: feedback, a description, "anything else we should know?" The larger box invites a fuller answer. Use it deliberately — a long-text box where you only needed a word makes responses harder to scan.

Typed inputs: email, number, phone, url, date

These look like text but carry built-in expectations, and that's the point — they validate format and, on mobile, summon the right keyboard.

Email rejects malformed addresses before submission, so you're not emailing john@gmail later.
Number keeps math clean and lets you set min/max. Reach for it for quantities, ages, counts — not phone numbers (leading zeros and + get mangled).
Phone uses the telephone input type and the phone keypad on mobile.
URL validates that a link is actually a link.
Date gives a real date picker instead of asking people to guess your preferred format.

Rule of thumb: if a value has a shape, use the typed field for it. You're moving validation from your inbox to the form, where it belongs.

Choices: select, radio, multi-select, yes/no

When the set of valid answers is known, let people choose, don't let them type. This is the single biggest lever for clean data.

Select (dropdown) suits long lists — countries, departments, plans — where saving vertical space matters.
Radio suits short lists (say two to five options) where seeing all choices at once helps the decision.
Multi-select is for "pick all that apply." Don't use it when only one answer is valid; you'll get contradictory combinations.
Yes/No is the cleanest possible binary. Use it for a single clear question rather than a two-option radio.

Rating

A rating field captures sentiment on a fixed scale (1 to 5 by default). It's the right tool for "how satisfied were you?" Keep the scale consistent across a form so responses stay comparable.

File upload

A file field collects documents, images, or attachments on the hosted form. One note worth planning around: file uploads work on the hosted form page but are disabled in embedded copies, where we can't process them securely. If you need files, send people to the hosted form.

Payment

A payment field collects money as part of the submission — useful for event tickets, deposits, or paid applications. It connects to your own payment account, so funds go to you. Treat it like any other required step in the flow rather than a bolted-on afterthought.

Statement: the field that collects nothing

A statement isn't an input at all — it's a block of text you drop between fields. Use it to set context, add a short instruction, or reassure people before a sensitive question ("We never share this"). A well-placed statement can do more for completion than any clever input.

The throughline

Every choice above is really the same decision: constrain input to match the answer's real shape. The more structure you give a field, the less cleanup you do later — and the more you can actually trust what people send you. Pick the type that matches the answer, not the one that's quickest to drop in.