The autocomplete attribute tells the browser what a field represents. Accurate tokens can reduce typing and mistakes, especially on mobile devices, without changing where the form submits.
Use purpose-specific tokens
Use name for a full name, given-name and family-name for separate fields, email for an email address, tel for a phone number and organization for a company. The token should describe the data, not the visual label.
<label for="full-name">Name</label>
<input id="full-name" name="name" autocomplete="name">
<label for="email">Email</label>
<input id="email" name="email" type="email" autocomplete="email">
<label for="phone">Phone</label>
<input id="phone" name="phone" type="tel" autocomplete="tel">Keep stable names and labels
Browsers use several signals when offering autofill. A stable field name, matching input type, visible label and valid autocomplete token work together better than an arbitrary token.
Do not disable useful autofill by default
Autocomplete off is a hint and browsers may not always follow it. Use it only when stored values would be inappropriate for the task, not as a general design preference.
Test without assuming stored profile data
Check the form with and without saved browser details. Autofill must not obscure labels, break validation or fill one person’s value into an unrelated field.
Frequently asked questions
Is autocomplete the same as the input name?
No. The name becomes part of submitted data; autocomplete describes the field purpose to the browser.
Does autocomplete send data to FormToInbox?
No. It only helps the browser fill the exported form; the selected destination controls submission.
Should a message field use autocomplete?
A free-form enquiry usually does not need a contact-information token. Use tokens only when they accurately describe the expected value.
Primary sources
Turn the guide into a working form
Start from a template, change the fields and take the code with you.
Open the free builder