# Fields

Name your form fields so Form Plume captures every input in your inbox, emails, and exports, plus how browser validation and reserved names work.

Your form's inputs decide what it collects. Every field with a `name` attribute is included in the submission, so naming fields well is the single most important part of form setup:

```html
<label>
  Email
  <input type="email" name="email" required>
</label>

<label>
  Message
  <textarea name="message" required></textarea>
</label>
```

## Name every field

The `name` becomes the field name in your inbox, emails, [exports](/docs/submissions/export), and [integrations](/docs/integrations). An input without one is ignored.

Use short names that will still make sense later. `email`, `company`, and `message` are better than `field_1`.

## Validation stays in your form

Browser attributes such as `required`, `type="email"`, and `minlength` give visitors fast feedback. Form Plume validates the request again when it arrives.

Client-side validation improves the experience. It never replaces server-side validation.

## Reserved names

Fields beginning with an underscore can control Form Plume behavior. They are not stored as ordinary answers.

See [Special fields](/docs/forms/special-fields) before adding one.