You may have seen a short HTML attribute change how a field, image, or link behaves. This guide is about Button Type Values: Submit, Reset, and Button. The type attribute on button decides whether clicking it submits a form, resets it, or just triggers a separate action.
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 |
|---|---|
submit | Submit the form; default for buttons associated with a form. |
reset | Restore form controls to initial values. |
button | A plain button with no automatic submit or reset behavior. |
A practical example
<form action="/feedback" method="post">
<label for="feedback">Feedback</label>
<input id="feedback" name="feedback" required>
<button type="submit">Send feedback</button>
<button type="reset">Clear</button>
<button type="button" id="show-help">Help</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 button without an explicit type inside a form usually submits it. A type="button" control needs JavaScript or declarative browser commands to perform an action.
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
Remove type="button" from Help and notice why it begins submitting the form.
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
- Accidentally submitting a form by using a button without type="button".
- 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
- Always write the type you intend, especially inside forms.
- 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.