What is the E.164 phone number format?
E.164 is the ITU-T standard for the international public telecommunication numbering plan. An E.164 number is written as a plus sign, followed by the country code, followed by the national subscriber number — all digits, with no spaces, dashes, parentheses, or trunk prefixes. A UK mobile stored in E.164 looks like +447700900123.
Three structural rules cover every E.164 number:
- Maximum 15 digits after the plus sign, excluding the + itself.
- Country code of 1–3 digits (1 for the US and Canada, 44 for the UK, 91 for India).
- No punctuation and no trunk prefix — the leading 0 most countries dial domestically is dropped, so UK
07700 900123becomes+447700900123, not+4407700900123.
How to convert a local number to E.164
- Drop the trunk prefix — the leading 0 (UK, Germany, India, Australia). US and Canada numbers are stored as +1 followed by the 10-digit national number; the domestic "1" is the country code, not a trunk prefix to remove.
- Remove every space, dash, dot, and parenthesis.
- Prepend
+and the country code.
Example: a Berlin landline dialed locally as 030 123456 becomes +4930123456 in E.164 — trunk 0 removed, country code 49 added, spacing removed.
Why APIs require E.164
Telecom and messaging APIs expect numbers in E.164 because it is the only format that is unambiguous across countries — the same 10 digits can be valid in several national formats, but only one E.164 string exists per number. The WhatsApp Business API, common CPaaS providers such as Twilio, and most carrier lookup and validation endpoints accept or require E.164 input, so normalizing your list before API submission prevents silent failures and mis-routed messages.
E.164 also improves list hygiene: the same phone number typed as (415) 555-0123, 415.555.0123, and 4155550123 is three duplicate CRM records until it is normalized to one canonical +14155550123.
Common E.164 formatting mistakes
- Keeping the trunk prefix:
+4407700900123instead of+447700900123. - Keeping punctuation:
+1 (415) 555-0123fails strict E.164 parsers. - Missing the country code:
4155550123is a national number, not E.164. - Storing display format in databases: formatted-for-humans fields break deduplication and API calls.
Use cases for E.164 normalization
Use E.164 normalization before bulk phone validation, API submissions, CRM imports, SMS sending, WhatsApp filtering, and global phone list cleaning.
The per-country digit counts and trunk prefixes that normalisation depends on are tabulated for 50 countries in the phone number format reference, with a CSV of the same rows.
When format is not enough
A correctly formatted number can still be invalid, unreachable, fixed line, VoIP, or wrong for your campaign. Pair format checks with Validate International Phone Numbers, line type detection, Phone Validation API, and UK Phone Number Checker for deeper validation.
Security and limits
Formatting validates shape, not ownership. Do not use format checks as identity proof. Review Security and Privacy Policy for data handling.
FAQ
What is the E.164 phone number format?
E.164 is the ITU-T international phone number standard: a plus sign, the country code, and the subscriber number written as one string with no spaces or punctuation, such as +447700900123.
How many digits can an E.164 number have?
An E.164 number has a maximum of 15 digits after the plus sign, made up of a country code of one to three digits plus the national subscriber number.
How do I convert a local number to E.164?
Remove the trunk prefix (usually a leading 0), remove spaces, dashes, and parentheses, then add the country code with a plus sign. For example, UK 07700 900123 becomes +447700900123.
Does E.164 formatting mean a number is valid or active?
No. E.164 only defines the shape of the number. A correctly formatted number can still be invalid, disconnected, or the wrong line type, so pair format checks with validation.
Can I normalize a whole CSV to E.164?
Yes. Use Phone List Cleaning to normalize and validate phone numbers in bulk.
Which APIs require E.164 phone numbers?
Most telecom and messaging APIs expect E.164, including the WhatsApp Business API and common CPaaS providers such as Twilio, so numbers should be normalized before API submission.