HTML Native Form Data Serialization Examples

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

FormData collects successful controls as name/value entries. An unchecked checkbox is normally absent.

Try the Example

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

<form id="student-form">
    <label for="student-name">Name</label>
    <input id="student-name" name="student-name" value="Alex">
    <label><input type="checkbox" name="subscribe" value="yes"> Subscribe</label>
    <button type="submit">Inspect data</button>
</form>
<script>
    const studentForm = document.querySelector("#student-form");
    studentForm.addEventListener("submit", (event) => {
        event.preventDefault();
        const studentData = new FormData(studentForm);
        console.log([...studentData.entries()]);
    });
</script>

Let’s Read the Code

<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.
id: An id uniquely identifies an element on this page.
for: For connects a label or output with a control by ID.

Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.

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 gets sent? With ordinary form submission, the browser builds a set of name/value entries. For checkboxes, only checked choices are normally included. Radio buttons in the same group contribute one selected value. Open the browser Network panel to see the request rather than guessing.

Your Turn

Toggle Subscribe and observe whether the subscribe entry exists in the console output.

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
Disabled controls and controls missing a name are not included in FormData.

Key Takeaways

A control needs a clear label and, when submitted, a meaningful name and value.
<form>: The form groups controls and identifies where submitted data goes.
Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.