---
title: "Autocomplete Reference Guide"
slug: "autocomplete-reference-guide"
updated: 2025-09-26T08:42:38Z
published: 2025-09-26T08:42:38Z
canonical: "docs.unqork.io/autocomplete-reference-guide"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Autocomplete Reference Guide

Some components in Unqork support the **Autocomplete** setting. Autocomplete detects end-user data saved in a browser and uses it to fill relevant fields. For example, in Express View, if there is a [Text Field](/v1/docs/text-field-component) component labeled **First Name**, and an end-user clicks into the field, the end-user's browser autofill function suggests first names saved to the browser.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/autoCompleteExample.webm?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

By default, Unqork's autocomplete function is set to `ON` and detects a component's label to map the correct autofill value to the field. For example, if a Text Field component's Label Text value contains the word **Last**, then autocomplete fills the field using the end-user's browser-saved **Last Name** value.

> Discover how to inspect and debug Chrome autofill data in Google's autofill article: [https://developer.chrome.com/docs/devtools/autofill](https://developer.chrome.com/docs/devtools/autofill).

## Supported Components

The following components support the autocomplete function:

### [Date Input Component](/v1/docs/date-input-component)

Learn how to let end-users enter dates in your applications.

### [Number Component](/v1/docs/number-component)

Learn how to let end-users enter number values in your applications.

### [Phone Number Component](/v1/docs/phone-number-component)

Learn how to let end-users enter USA-specific phone numbers in your applications.

### [Text Area Component](/v1/docs/text-area-component)

Learn how to let end-users enter multiple sentences of text in your applications.

### [Text Field Component](/v1/docs/text-field-component)

Learn how to let end-users enter short sentences of text in your applications.

## Unqork Autocomplete Values

Unqork supports autocomplete for a variety of inputs. The list below contains the Unqork autocomplete values and a description of each.

| Autocomplete Value | Description |
| --- | --- |
| on | Autocomplete is enabled. This setting uses the Label Text value to detect what autocomplete value to input. For example, if a Text Field component's **Label Text** value contains the word **Last**, then autofills the field using the end-users browser-saved `Last Name` value. The Autocomplete setting defaults to this value. |
| off | Autocomplete is disabled. When selecting a field, it does not display the browser's autofill function. |
| address-line1 | The first line of an address, as highlighted in red text below: `1234 First Lane Rd` `Building 3a` `Suite C. ` `Black Mesa, New Mexico 96003` |
| address-line2 | The second line of an address, as highlighted in red text below: `1234 First Lane Rd` `Building 3a` `Suite C.` `Black Mesa, New Mexico 96003` |
| address-line3 | The third line of an address, as highlighted in red text below: `1234 First Lane Rd ` `Building 3a` `Suite C.` `Black Mesa, New Mexico 96003` |
| address-level1 | The state or province of an address, as highlighted in red text below: `1234 First Lane Rd` `Building 3a` `Suite C.` `Black Mesa, New Mexico 96003` |
| address-level2 | The city name in an address, as highlighted in red text below: `1234 First Lane Rd` `Building 3a` `Suite C.` `Black Mesa, New Mexico 96003` |
| address-level3 | The third level of an address is in addresses that have three or more levels. |
| address-level4 | The fourth level of an address in addresses that have four levels. |
| street-address | The full address, including `address-line1`, `address-line2`, and `address-line3`. Typically, street-address does not include `address-level1` through `4`. |
| country | The country or territory code. For example, `United States` becomes `US`. Autofill might predict this value based on the postal code or state address. |
| country-name | The country or territory name. For example, the country `Canada` in `British Columbia`, `Canada`. Autofill might predict this value based on the postal code or state address. |
| postal-code | The postal code (ZIP code) value in an address, as highlighted in red text below: `1234 First Lane Rd` `Building 3a` `Suite C.` `Black Mesa, New Mexico 96003` |
| name | The full name value. Includes `honorifics`, `given-name`, `additional-name`, `family-name`, and `nickname` values. For example: `James Lee Smith`. |
| additional-name | The middle name value. For example, the middle name `Lee`, in `James Lee Smith`. |
| family-name | The last, or family name value. For example, the last name `Smith`, in `James Lee Smith`. |
| given-name | The first name value. For example, the first name `James`, in `James Lee Smith`. |
| honoric-prefix | The title, like Mr., Mrs., and so on. For example, the prefix `Mr.`, in `Mr. James Lee Smith`. |
| honoric-suffix | The name suffix. For example, the suffix `Jr.` (Junior), in James Lee Smith Jr.. |
| nickname | The nickname or user handle. This value is different than `username`. |
| organization-title | The job title. For example, a `Machine Learning Engineer`. |
| username | The username or account name. |
| new-password | The new password. Use this setting to prevent the browser from accidentally filling a new password field with the current or existing password. |
| current-password | The current password. |
| bday | The full birth date. Includes the `bday-day`, `bday-month`, and `bday-year` fields. For example, `07/21/1986`. |
| bday-day | The day of the birth date. For example, `07` in `07/21/1986`. |
| bday-month | The month of the birth date. For example, `21` in `07/21/1986`. |
| bday-year | The year of the birth date. For example, `1986` in `07/21/1986`. |
| sex | The gender identity. Examples include `Male`, `Female`, `Nonbinary`, and so on. |
| one-time-code | Selects the one-time password (OTP) for verification. End-users receive this value from an external service, usually SMS, email, or an authenticator application. |
| organization | The company name. |
| cc-name | The full name as displayed on a credit card. Includes `cc-given-name`, `cc-additional-name`, and `cc-family-name`. |
| cc-given-name | The first name as displayed on a credit card. For example, the first name `James`, in `James Lee Smith`. |
| cc-additional-name | The middle name as displayed on a credit card. For example, the middle name `Lee`, in `James Lee Smith`. |
| cc-family-name | The last name as displayed on a credit card. For example, the last name `Smith`, in `James Lee Smith`. |
| cc-number | The credit card number. |
| cc-exp | The credit card expiration date. Includes `cc-exp-month` and `cc-exp-year`. For example, `05/2025`. |
| cc-exp-month | The credit card expiration month. For example, `05` in `05/2025`. |
| cc-exp-year | The credit card expiration year. For example, `2025` in `05/2025`. |
| cc-csc | The credit card CVC code. Typically, a 3 or 4-digit code. |
| cc-type | The credit card's payment type. For example, `Visa`, `Mastercard`, `Amex`. |
| transaction-currency | The currency type for the transaction. Example values include `USD` (US Dollar), `EUR` (Euro), and `INR` (India). |
| transaction-amount | The amount of currency in the `transaction-currency` type. |
| language | The preferred language. Specified as an [IETF BCP 47 language tag](https://en.wikipedia.org/wiki/IETF_language_tag). |
| url | The web address URL. Examples include a homepage, company website, or other address, depending on the context of the fields in the form. |
| email | The email address. For example, `gordon.freeman@blackmesa.com`. |
| photo | The URL of an image displaying the person, company, or contact information, depending on the context of the fields in the form. |
| tel | The full phone number. For example, `1-888-999-9999`. |
| tel-country-code | The country code from a phone number. For example, the country code for the United States is `1` in the following phone number: `1-888-999-9999`. |
| tel-national | The phone number without the country code. For example, `888-999-9999`. |
| tel-area-code | The phone number's area code. For example, the value `408` in the following phone number: `888-408-9999`. |
| tel-local | The phone number does not include a country code or area code. For example, `999-9999`. |
| tel-local-prefix | The phone number's local prefix. |
| tel-local-suffix | The phone number's local suffix. |
| tel-extension | The phone number's extension code. |
| impp | The URL of an instant messaging protocol endpoint. For example, `xmpp:username@example.net`. |

## Resources

- [Building Accessible Applications in Unqork](/v1/docs/accessibility-in-unqork)

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View.

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.