Think of filling out a sign-up page. Clear fields make the job simple; confusing fields make people leave.
What You Need to Know
Datetime-local includes date and clock time but no time-zone offset.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/book" method="get">
<label for="start-time">Appointment (local time)</label>
<input id="start-time" name="starts" type="datetime-local" value="2026-12-10T09:30" required>
<button type="submit">Book time</button>
</form>Let’s Read the Code
- value: The value is the actual data associated with a control or choice.
- <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.
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.
Look at the submitted value. The picker may display a friendly calendar or local clock, while form values use specific machine-readable formats. A local date and time does not automatically carry a time-zone identifier. Compare what you see with what your application receives.
Your Turn
Submit the value and check that there is no Z or +hh:mm time-zone marker.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- The server needs to know the intended time zone if appointments span different regions.
Key Takeaways
- A control needs a clear label and, when submitted, a meaningful name and value.
- value: The value is the actual data associated with a control or choice.
- Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.