Content · Web Development · HTML

HTML formaction, formmethod, and formenctype on Buttons

formaction, formmethod, and formenctype on Buttons: The markup gives the browser a clear starting point for formaction. Look at the labels, names, and values rather than only the visual appearance. Includes a practical HTML example and an explanation.

1 views Published Oct 19, 2026 Updated Oct 19, 2026 Admin

A form should feel easy to use. The visitor sees a question, gives an answer, and needs to know what will happen next.

What You Need to Know


Here is a small, realistic example focusing on formaction.

In this example: create Save and Publish actions in one form.

Try the Example


Take a look at the example. We’ll explain the important lines right below it.

<form action="/publish" method="post">
    <label for="post-title">Post title</label>
    <input id="post-title" name="post-title" required>
    <button type="submit">Publish</button>
    <button type="submit" formaction="/preview">Preview instead</button>
</form>

Let’s Read the Code


  • type: Type changes what sort of control or resource the browser uses.
  • <form>: The form groups controls and identifies where submitted data goes.
  • <label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
  • for: For connects a label or output with a control by ID.

What the example shows: The markup gives the browser a clear starting point for formaction. Look at the labels, names, and values rather than only the visual appearance.

What Happens in the Browser?


The HTML controls work in the browser, but saving an answer requires the example action path to be handled by a real server.

Where does the answer go? The example uses the submitted name(s) post-title. Those names help the receiving server identify each answer. A label is for people; a name attribute is for the form data; an ID connects elements in the page.

Your Turn


Check which destination each submit button uses and why a plain button would behave differently.

Common Beginner Mistakes


  • Copying the example without giving the fields a clear label and a usable name.
  • A browser may render the control differently from another browser without changing the HTML meaning.

Key Takeaways


  • A control needs a clear label and, when submitted, a meaningful name and value.
  • type: Type changes what sort of control or resource the browser uses.
  • Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.
Share this resourceSend this page to someone who may find it useful.