Use Email to collect an address with email-syntax validation. Optional confirmation asks the visitor to type the address twice to catch differences. It does not send a verification message or prove that the visitor owns the inbox.
Availability: Core (Free).
Add and configure the field
- Open the form in Build and add Email from Add fields.
- Select its canvas card to open Field options, then configure the controls below.
- Save the form and check its saved Preview and embedded page.
Field-specific settings
| Setting | What it does |
|---|---|
| Enable email confirmation | Adds a repeat email input when enabled. Only the primary email is saved. |
| Confirmation label | The second input's label. Defaults to Confirm email. |
| Confirmation placeholder | An optional hint inside the empty repeat input. The primary Default value or population source does not fill this repeat. |
Applicable shared options
This field also provides Description placement, Validation message placement, Label, Description, Required, Required message, Invalid value message, CSS classes, Hide label, Admin label, Visibility, Placeholder, Default value, Autocomplete. See common field options for their behavior.
Review Visible, Hidden and Internal before changing presentation. Static hiding differs from conditional applicability.
Dynamic population offers Disabled, Parameter, Current user. Its applicable Parameter name and User property controls select the initial source; submitted or cleared answers are not refilled.
No duplicates and Duplicate value message require Pro. They compare accepted entries for this form and field, separately from Required.
Answers and behavior
One normalized email string is saved under this field. The repeat is used only for submission matching and is not another entry value, merge-tag component or notification destination.
Confirmation compares trimmed strings case-sensitively. An optional empty primary/repeat pair is valid; a nonempty primary needs a matching partner. Inputs share one field width, sit side by side on larger screens and stack on narrow screens. Static Hidden visibility omits the inaccessible repeat while retaining primary email validation.
Example and checks
For a visitor receipt, create an Email field called Your email, enable Required and optionally confirmation. In the notification editor, choose this field tag for Send to. For an admin alert, keep an authorized website sender and use the visitor field for Reply-To.
Test malformed syntax, mismatched confirmation and a matching pair. Use an inbox you control for a deliberate send. An accepted email value is not proof that the website can deliver mail to it; check Notifications separately.
Use the testing checklist to check validation and the saved entry. Explore all fields provides live examples.
