You may have seen a short HTML attribute change how a field, image, or link behaves. This guide is about Input Type Values: Number vs Range. Number and range accept numerical values but offer very different interactions.
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 |
|---|---|
number | Editable numeric value with native number validation. |
range | Slider for choosing an approximate value between boundaries. |
A practical example
<form action="/preferences" method="get">
<label for="items">Items per page</label>
<input id="items" type="number" name="items" min="1" max="50" step="1">
<label for="volume">Volume</label>
<input id="volume" type="range" name="volume" min="0" max="100" value="35">
<button type="submit">Save</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.
A range slider cannot communicate every precise numeric value easily; number is better for exact quantities. Neither automatically shows a live value label unless you add one.
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
Try entering a decimal in a number field with step="1", then use step="0.5" and compare.
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
- Using range for an exact payment amount where precise entry is essential.
- 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
- Match the control to the precision users need.
- 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.