HTML Profile Editing Form with Optional and Required Fields

Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.

What You Need to Know

This example puts a readable label next to each control and gives each submitted value a name.

Try the Example

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

<form action="/submit-profile" method="post">
    <label for="display-name">Display name</label>
    <input id="display-name" name="display-name" type="text" autocomplete="nickname" required>
    <button type="submit">Continue</button>
</form>

Let’s Read the Code

required: Required asks the browser to stop a normal submission when this control has no acceptable value.
<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: A browser can display and check the fields, but an address such as /submit-contact needs server code to actually save a response.

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.

What happens to the file? Choosing a file does not upload it immediately. The browser sends it when the form is submitted to an endpoint that accepts file uploads. The server must check the file type, size, and permissions before storing it.

Your Turn

Change one label and one name attribute. Which change affects what people see, and which changes the name sent to the server?

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
If this page is opened as a local file, it will display, but its submit destination is only an example until you build a server endpoint.

Key Takeaways

A control needs a clear label and, when submitted, a meaningful name and value.
required: Required asks the browser to stop a normal submission when this control has no acceptable value.
Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.