HTML Phone Number Inputs with Country Calling Codes

Think of filling out a sign-up page. Clear fields make the job simple; confusing fields make people leave.

What You Need to Know

The country calling code and national number are separate submitted values. The server can combine and normalize them.

Try the Example

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

<form action="/contact" method="post">
    <label for="calling-code">Country calling code</label>
    <select id="calling-code" name="calling-code">
        <option value="+1">+1</option>
        <option value="+44">+44</option>
        <option value="+81">+81</option>
    </select>
    <label for="phone-number">Phone number</label>
    <input id="phone-number" name="phone-number" type="tel" autocomplete="tel-national">
    <button type="submit">Save number</button>
</form>

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

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.

Where does the answer go? The example uses the submitted name(s) calling-code, phone-number. 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

Change the calling code and explain why a national number may need different formatting.

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
Country calling codes are not always one-to-one with countries; validate and normalize phone numbers on the server.

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.