You may have seen a short HTML attribute change how a field, image, or link behaves. This guide is about Input Type Values: Text vs Search vs Password. Text, search, and password inputs all accept typed text, but their purpose and browser presentation differ.
The useful question is not simply “Which value should I memorize?” It is “What should people be able to do on this page?” First decide the goal, then choose an HTML value that matches it.
How the values work
| Value | Meaning |
|---|---|
text | Ordinary single-line text input. |
search | Search input, sometimes with a built-in clear button. |
password | Masks typed characters in the interface; does not encrypt the value. |
A practical example
<form action="/login" method="post">
<label for="account">Account</label>
<input id="account" name="account" type="text" autocomplete="username">
<label for="secret">Password</label>
<input id="secret" name="password" type="password" autocomplete="current-password">
<button type="submit">Sign in</button>
</form>Understanding the code
Start by finding the attribute in the example. The HTML element tells the browser what kind of thing it is displaying; the attribute supplies an extra instruction or hint about that particular element. If you remove the attribute, the element usually still exists, but one part of its behavior may change.
Password masking hides characters from nearby observers, but does not replace HTTPS, secure authentication, or safe password storage.
If a file path or form action appears in the code, it is an example project path. Create the matching file or server endpoint before expecting the complete behavior to work. This distinction is important: HTML describes the page, but it does not automatically build a server or create missing resources.
When to use it
Use type only where its documented behavior helps someone complete a task. Ask whether the choice improves clarity, keyboard access, performance, or correct data collection. If an extra attribute has no clear purpose, leaving it out may be safer than relying on a poorly understood hint.
Try it yourself
Build a search page with type="search" and compare it with type="text" on mobile.
Save the code in a local HTML file, open it in a current browser, and inspect the relevant control or request. When the feature depends on a server, use a small local development server rather than guessing from the source alone.
Common Beginner Mistakes
- Sending passwords through a GET form because the password field looks hidden.
- Assuming every browser provides identical controls or follows a hint in exactly the same way.
- Copying a demonstration without providing the files or server behavior it expects.
Key Takeaways
- The type improves semantics and user experience; the server still handles security.
- Choose the value based on what the visitor needs to do, not only on how the source looks.
- Test the result in the browser, including keyboard access and submitted values where relevant.