E.164 Phone Number Formatter
Convert phone numbers to E.164 international format for ad platform APIs. Supports US, CA, UK, AU, and custom country codes.
What is E.164 Format?
E.164 is the international telephone number format defined by the International Telecommunication Union (ITU). It standardizes phone numbers worldwide using a consistent structure:
+[country code][subscriber number]Examples:
- US:
(555) 123-4567→+15551234567 - UK:
020 7946 0958→+442079460958 - AU:
(02) 9374 4000→+61293744000
Why Ad Platforms Require E.164
Every major ad platform API requires E.164 for phone number matching:
- Google Ads Enhanced Conversions: Phone must be E.164 formatted before SHA-256 hashing
- Meta Conversions API (CAPI):
phfield requires E.164 + SHA-256 - Microsoft Ads: E.164 for offline conversion phone matching
- TikTok Events API: E.164 + SHA-256 for phone-based matching
The reason is consistency: (555) 123-4567, 555-123-4567, and 5551234567 are the same number, but they produce three completely different SHA-256 hashes. E.164 ensures everyone hashes the same input.
Common Formatting Mistakes
- Missing country code —
5551234567instead of+15551234567 - Including formatting characters —
+1 (555) 123-4567instead of+15551234567 - Wrong country code — Using
+1for a UK number - Leading zero not removed —
+610293744000instead of+61293744000(AU)
After formatting to E.164, hash with SHA-256 using our SHA-256 Hasher tool.
Frequently Asked Questions
E.164 is the international phone number format defined by the ITU. It starts with a + sign, followed by the country code and subscriber number, with no spaces, dashes, or parentheses. Example: +15551234567 (US), +442071234567 (UK). All major ad platforms require phone numbers in E.164 format for offline conversion uploads and Enhanced Conversions.
Ad platforms need a standardized format to match your uploaded phone numbers against their user records. Without E.164 normalization, the same phone number could appear as (555) 123-4567, 555-123-4567, 5551234567, or +15551234567 — all representing the same number but producing different SHA-256 hashes. E.164 eliminates this ambiguity.
Yes. For Enhanced Conversions and server-side event APIs, you must first convert to E.164 format, then SHA-256 hash the result. The order matters — hash the E.164-formatted number, not the raw input. Use our SHA-256 Hasher tool to hash the formatted output.
No. This tool runs entirely in your browser. No phone numbers are sent to any server or stored anywhere. You can verify this by disconnecting from the internet — the tool will still work.