How do I tell people which fields in a contact form are required?
Quick answer
Choose one labeling pattern and explain it before the first field. A straightforward option is to mark each mandatory field “(required)” and each non-mandatory field “(optional).” If you use an asterisk instead, define it clearly, such as “* Required.” Keep labels, instructions, and error messages consistent, and review the form from a visitor’s point of view.
The question, the details, the next step.
What’s the clearest way to show which fields on my contact form are required?
Pick one convention and use it throughout the form. For example, put “(required)” beside every field people must complete and “(optional)” beside fields they can skip. That spells out the distinction right where people need it.
You could instead mark required fields with an asterisk, but explain the symbol before the first field—for example, “* Required.” Don’t use an asterisk without defining it, or switch between symbols and words without a clear reason.
Do I need to label every field, or can I just explain that some are required?
If you label only the optional fields, say so plainly before the form: “Fields marked ‘(optional)’ may be left blank. All other fields are required.” This can work well when most fields are mandatory.
If the form has a mix of required and optional fields, labeling each one can make the status easier to spot while scanning. Avoid making visitors infer that a blank-looking field is optional unless your introduction explicitly establishes that rule.
Can you show me how that would look in a short contact form?
Here’s a copyable example using words rather than a symbol:
“Fields marked ‘(required)’ must be completed. Fields marked ‘(optional)’ may be left blank.”
Name (required) Email address (required) Phone number (optional) How can we help? (required)
“Send message”
Treat this as a wording example, not a prescribed form design. Replace the labels and fields to match what your form actually asks for. If you choose the asterisk pattern, use it consistently and include the explanation before people reach the fields.
What should happen if someone leaves a required field empty?
Make the message identify the specific field and the action needed. For example: “Enter your email address to continue.” Keep the wording consistent with the field label; if the label says “Email address,” avoid calling it “Contact details” in the error.
If a field is optional, don’t describe leaving it blank as a mistake. For fields that become required only in certain situations, explain that condition next to the field or in the instruction that makes it relevant, rather than relying on a general note alone.
How can I review the finished form to catch confusing labels?
Read the introduction, field labels, and any example errors together, as if you had not seen the form before. Check that a visitor can answer three questions without guessing: What must I fill in? What can I skip? What should I do if I miss something?
Then compare each field’s label with the form’s actual expectations. If “Phone number (optional)” is treated as mandatory later, the wording is misleading. Ask someone unfamiliar with the draft to describe which fields they think they can leave blank; use any disagreement to revise the labels or explanation.
A practical checklist
Choose either explicit “(required)” and “(optional)” labels or a clearly explained symbol.
Put the explanation before the first field.
Use the same wording and marking pattern throughout the form.
Make optional fields genuinely skippable, and explain any conditional requirements near the relevant field.
Write missing-field messages that name the field and say what to do.
Review the form with a reader unfamiliar with the draft.
A few more useful answers
Should I mark optional fields too?
It depends on the pattern. If you label only optional fields, state clearly that all unmarked fields are required. If the form mixes field types, labeling both types can make the distinction easier to spot.
Is an asterisk enough to show that a field is required?
Not by itself. If you use an asterisk, explain its meaning before the fields, for example, “* Required,” and apply it consistently.
How should I label a field that is required only sometimes?
Explain the condition close to the field or in the instruction that makes it relevant. Avoid presenting it as unconditionally required if visitors can skip it in some cases.