Phone Number Validator & Formatter
Validate any phone number against the official numbering plans, see whether it is real or just plausible, and get E.164, international, national and RFC3966 formats side by side.
About this tool
Phone numbers look simple and are not. A British mobile typed into an American form gets rejected; a leading zero disappears; a number that is "10 digits long, so it must be fine" turns out to be nobody’s number at all. The rules that decide all of this live in each country’s numbering plan — hundreds of them, updated regularly — and nobody keeps them in their head.
This tool checks a number against those plans. Pick the country the number belongs to (or just type the number with its + country code) and you get three separate answers: whether the number is valid — that is, it matches a real, currently assigned number range; whether it is merely plausible — the right length for the country but matching no real range; or neither. The distinction matters: a plausible-but-invalid number is the classic typo that survives naive length checks and then bounces.
Alongside the verdict you get the standard formats side by side: E.164 (the unambiguous +countrynumber form databases and APIs want), the international and national display formats with correct spacing, and the RFC3966 tel: URI for click-to-dial links. The number’s type — mobile, fixed line, toll free, VoIP — is shown where the plan identifies it. Example numbers for every country come from the same dataset, so you always have something valid to try.
The validation data is Google’s libphonenumber dataset, bundled into the page: no number you enter is sent anywhere, and the tool works offline.
What the number type tells you, and where it cannot
Where the numbering plan identifies it, the tool labels the number as mobile, fixed line, toll free, VoIP and so on. In countries that share one range between fixed and mobile lines, the label reads "fixed line or mobile" rather than guessing one.
The type comes from the same dataset that decides validity: every range inside a plan is tagged in advance, so a number that falls in a mobile range is reported as mobile. It is a property of the range, not something inferred from the digits at read time.
Where a country allocates a single block to both kinds of line, no honest answer exists, so the tool shows the combined label instead of picking a side. Where the dataset carries no designation at all, the type is shown as unknown rather than left blank.
The type is information, not a promise about the line. A number in a mobile range may be a VoIP service or a landline that has been ported; the plan describes the block, not the subscriber behind it.
Where the list of country names comes from
The country names in the picker are generated by the browser itself, from its own locale data, rather than shipped as a translation table. That is why hundreds of countries appear in your own language without the page carrying a single translated name.
Each entry pairs a localised name with its ISO country code and dialling prefix, and the whole list is sorted by that localised name, so the country you want appears where you would look for it alphabetically — not in English order.
If a runtime cannot produce a name for a code, the code itself is shown instead. A missing translation degrades to something you can still act on, rather than an empty row.
The country the page starts on is guessed from the browser’s own language setting, falling back to the United States when nothing usable is found. It is only a starting point for numbers written without a country code, and it never overrides a number that already carries one.
Why the input box never reformats itself
The as-you-type formatting is a separate preview, not a rewrite of the field. The text you typed stays exactly as typed, so the cursor never jumps to the end in the middle of an edit.
Reformatting a field while someone types is a familiar trick with a familiar bug: the cursor jumps, and the next keystroke lands in the wrong place. This tool formats a copy for display and leaves the input alone.
It also means the raw number you entered is preserved for re-checking. If a verdict surprises you, the exact string that produced it is still there, rather than a version the page quietly rewrote.
Possible and valid answer two different questions
A number can have exactly the right length for its country and still not be dialable, because length is a shape check and validity is an allocation check.
Type 12345678901 with China selected and the tool reports possible true, valid false, and no type at all. Eleven digits starting with 1 is the correct shape for a Chinese mobile number, but 123 is not a prefix anybody has been assigned, so no such line exists.
Keeping the two apart matters because the fix is different. If the length is wrong the user edits the digits; if the length is right the number is simply not in service or was mistyped in a way length cannot reveal. Collapsing both into one red mark would send people to edit the one thing that is already correct.
It is also why an invalid number comes back with no formatting at all. Grouping rules live inside each numbering plan, per prefix and per length, so a number that matches no plan has no grouping to apply and is echoed exactly as typed. The absence of spaces is not a bug, it is the honest answer.
Frequently asked questions
What is the difference between "valid" and "plausible"?
Plausible means the length fits the country’s plan. Valid means the number matches an actual assigned range within it — 10 digits is a plausible US number, but 131-234-5678 is not one anybody has. Forms should demand validity; length checks alone let these typos through.
Why do I need to pick a country if I already type the + code?
You often don’t: a number written with its + country code is self-describing and the country picker is ignored. The picker is for numbers written the local way — without the + prefix — like 020 7946 0958, which only means something once the country is known.
What is E.164 and why do databases want it?
E.164 is the international standard form: a leading +, the country calling code, then the national number with no spaces, zeros removed, at most 15 digits. It is unambiguous — the same number written three different ways collapses into one E.164 string — which is exactly why APIs, CRM systems and verification services store numbers in this format.
A number shows as valid. Does that mean it exists?
No — and no offline tool can tell you that. Valid means the number sits inside a range that the country’s operator actually assigns numbers from. Whether this particular number is in service, and who holds it, can only be learned by contacting it (for example with an SMS verification flow).
How current is the data?
It is Google’s libphonenumber dataset — the same one behind Android’s dialer and most phone verification libraries — bundled at build time. Numbering plans do change, so treat an unexpected "invalid" as a reason to double-check rather than a court ruling.
Are the numbers I check stored or sent anywhere?
No. The dataset ships with the page and everything runs in your browser, so the tool keeps working with no connection at all.
Related tools
Convert a date and time across time zones, with correct daylight-saving handling — including wall-clock times that do not exist on that date.
Test a regular expression against your own text, see every match and capture group highlighted, get each piece of the pattern explained, and check what JavaScript, PCRE and RE2 actually support. Everything runs in your browser.
Generate names, emails, usernames, UUIDs, IP and MAC addresses, Luhn-valid card numbers and more — seeded so the same seed always yields the same rows, entirely in your browser.