Code Quality Rank: L1
Monthly Downloads: 0
Programming language: JavaScript
License: GNU General Public License v3.0 or later
Tags: Number     Browserify     Format     Wrapper     Formatting     Standardize     Rfc3966     Phonenumber     Phone     Libphonenumber     International     E164    
Latest version: v3.2.11

google-libphonenumber alternatives and similar modules

Based on the "Parsing" category.
Alternatively, view google-libphonenumber alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of google-libphonenumber or a related project?

Add another 'Parsing' Module



The up-to-date and reliable Google's libphonenumber package for node.js. Zero dependencies.


npm version build status install size


Google's libphonenumber is a library that parses, formats, stores and validates international phone numbers. It is used by Android since version 4.0 and is a phenomenal repository of carrier metadata.

Although it compiles down to Java, C++ and JS, its JS port is tightly coupled to the Google Closure library. This makes it more difficult to directly require and use the code on a node.js project.

Google eventually started publishing google-closure-library directly to NPM, ending years of ill-maintained community packages. However, running the original library on node.js remains a cumbersome process.

After all these years, Google's libphonenumber is still not officially available on NPM. What is the best way to use Google's libphonenumber on node.js then? If you're looking for a convenient and easy method, that's what this package is all about.


Install the package via npm:

npm install --save-prod google-libphonenumber


The following is a simple phone information extraction example similar to what can be viewed on the official demo page.

โš ๏ธ Most libphonenumber functions expect to receive an instance of libphonenumber.PhoneNumber which can be obtained by calling phoneUtil.parse or phoneUtil.parseAndKeepRawInput on a raw (string) number, otherwise it will throw errors like TypeError: a.getCountryCodeOrDefault is not a function.

This will work:

phoneUtil.isValidNumberForRegion(phoneUtil.parse('202-456-1414', 'US'), 'US');

This will not work:

phoneUtil.isValidNumberForRegion('202-456-1414', 'US');

More API examples after parsing the raw string:

// Require `PhoneNumberFormat`.
const PNF = require('google-libphonenumber').PhoneNumberFormat;

// Get an instance of `PhoneNumberUtil`.
const phoneUtil = require('google-libphonenumber').PhoneNumberUtil.getInstance();

// Parse number with country code and keep raw input.
const number = phoneUtil.parseAndKeepRawInput('202-456-1414', 'US');

// Print the phone's country code.
// => 1

// Print the phone's national number.
// => 2024561414

// Print the phone's extension.
// =>

// Print the phone's extension when compared to i18n.phonenumbers.CountryCodeSource.

// Print the phone's italian leading zero.
// => false

// Print the phone's raw input.
// => 202-456-1414

// Result from isPossibleNumber().
// => true

// Result from isValidNumber().
// => true

// Result from isValidNumberForRegion().
console.log(phoneUtil.isValidNumberForRegion(number, 'US'));
// => true

// Result from getRegionCodeForNumber().
// => US

// Result from getNumberType() when compared to i18n.phonenumbers.PhoneNumberType.

// Format number in the E164 format.
console.log(phoneUtil.format(number, PNF.E164));
// => +12024561414

// Format number in the original format.
console.log(phoneUtil.formatInOriginalFormat(number, 'US'));
// => (202) 456-1414

// Format number in the national format.
console.log(phoneUtil.format(number, PNF.NATIONAL));
// => (202) 456-1414

// Format number in the international format.
console.log(phoneUtil.format(number, PNF.INTERNATIONAL));
// => +1 202-456-1414

// Format number in the out-of-country format from US.
console.log(phoneUtil.formatOutOfCountryCallingNumber(number, 'US'));
// => 1 (202) 456-1414

// Format number in the out-of-country format from CH.
console.log(phoneUtil.formatOutOfCountryCallingNumber(number, 'CH'));
// => 00 1 202-456-1414

Using the "As You Type" Formatter

The "As You Type" formatter is a specialized tool that show the formatting progress as it attempts to discover the right format for the given number. It requires registering every keystroke (input digit) on a new instance of the AsYouTypeFormatter as shown below.

// Require `AsYouTypeFormatter`.
const AsYouTypeFormatter = require('google-libphonenumber').AsYouTypeFormatter;
const formatter = new AsYouTypeFormatter('US');

console.log(formatter.inputDigit('2')); // => 2
console.log(formatter.inputDigit('0')); // => 20
console.log(formatter.inputDigit('2')); // => 202
console.log(formatter.inputDigit('-')); // => 202-
console.log(formatter.inputDigit('4')); // => 202-4
console.log(formatter.inputDigit('5')); // => 202-45
console.log(formatter.inputDigit('6')); // => 202-456
console.log(formatter.inputDigit('-')); // => 202-456-
console.log(formatter.inputDigit('1')); // => 202-456-1
console.log(formatter.inputDigit('4')); // => 202-456-14
console.log(formatter.inputDigit('1')); // => 202-456-141
console.log(formatter.inputDigit('4')); // => 202-456-1414

// Cleanup all input digits from instance.


A quick glance at Google's libphonenumber rich API. Descriptions sourced from original files.


The class that offers the main utilities to work with phone numbers, such as formatting, parsing and validating.


  • format(number, numberFormat) - formats a phone number in the specified format using default rules.
  • formatInOriginalFormat(number, regionCallingFrom) - formats a phone number using the original phone number format that the number is parsed from.
  • formatOutOfCountryCallingNumber(number, regionCallingFrom) - formats a phone number for out-of-country dialing purposes.
  • getNumberType(number) - gets the type of a valid phone number.
  • getRegionCodeForNumber(number) - returns the region where a phone number is from.
  • isPossibleNumber(number) - returns true if the number is either a possible fully-qualified number (containing the area code and country code), or if the number could be a possible local number (with a country code, but missing an area code).
  • isValidNumber(number) - tests whether a phone number matches a valid pattern.
  • isValidNumberForRegion(number, regionCode) - tests whether a phone number is valid for a certain region.
  • parseAndKeepRawInput(numberToParse, defaultRegion) - parses a string and returns it in proto buffer format while keeping the raw input value.
  • parse(numberToParse, defaultRegion) - parses a string and returns it in proto buffer format.


The type of the phone returned after a string number has been parsed via PhoneNumberUtil.parse() or PhoneNumberUtil.parseAndKeepRawInput().


  • getCountryCode()
  • getCountryCodeSource()
  • getExtension()
  • getItalianLeadingZero()
  • getNationalNumber()
  • getRawInput()


Lists the following enums in order to compare them with the output of Phone.getCountryCodeSource():

  • CountryCodeSource.UNSPECIFIED
  • CountryCodeSource.FROM_NUMBER_WITH_IDD
  • CountryCodeSource.FROM_DEFAULT_COUNTRY


Lists the following enums in order to pass them to PhoneNumberUtil.format():

  • PhoneNumberFormat.E164
  • PhoneNumberFormat.INTERNATIONAL
  • PhoneNumberFormat.NATIONAL
  • PhoneNumberFormat.RFC3966


Lists the following enums in order to compare them with the output of PhoneNumberUtil.getNumberType():

  • PhoneNumberType.FIXED_LINE
  • PhoneNumberType.MOBILE
  • PhoneNumberType.FIXED_LINE_OR_MOBILE
  • PhoneNumberType.TOLL_FREE
  • PhoneNumberType.PREMIUM_RATE
  • PhoneNumberType.SHARED_COST
  • PhoneNumberType.VOIP
  • PhoneNumberType.PERSONAL_NUMBER
  • PhoneNumberType.PAGER
  • PhoneNumberType.UAN
  • PhoneNumberType.VOICEMAIL
  • PhoneNumberType.UNKNOWN



  • connectsToEmergencyNumber(number, regionCode) - tests whether the short number can be used to connect to emergency services when dialed from the given region.
  • isPossibleShortNumber(number) - tests whether a short number is a possible number.
  • isPossibleShortNumberForRegion(number, regionDialingFrom) - tests whether a short number is a possible number when dialed from the given region.
  • isValidShortNumber(number) - tests whether a short number is a possible number.
  • isValidShortNumberForRegion(number, regionDialingFrom) - tests whether a short number matches a valid pattern in a region.
// Get an instance of `ShortNumberInfo`.
const shortInfo = require('google-libphonenumber').ShortNumberInfo.getInstance();

// Get an instance of `PhoneNumberUtil`.
const phoneUtil = require('google-libphonenumber').PhoneNumberUtil.getInstance();

// Result from connectsToEmergencyNumber().
console.log(shortInfo.connectsToEmergencyNumber('911', 'US'));
// => true

// Result from isPossibleShortNumber().
console.log(shortInfo.isPossibleShortNumber(phoneUtil.parse('123456', 'FR')));
// => true

// Result from isPossibleShortNumberForRegion().
console.log(shortInfo.isPossibleShortNumberForRegion(phoneUtil.parse('123456', 'FR'), 'FR'));
// => true

Unavailable methods and classes

The following methods or classes are unavailable on the original JS port of Google's libphonenumber:

  • findNumbers - finds numbers in text (useful for highlighting or linking phone numbers inside text messages).
  • PhoneNumberOfflineGeocoder - provides geographical information related to a phone number.
  • PhoneNumberToCarrierMapper - provides carrier information related to a phone number.
  • PhoneNumberToTimeZonesMapper - provides timezone information related to a phone number.


Metadata issues

Most of the issues submitted to this repository are related to carrier metadata - things like unexpected phone validations, errors in formatting numbers, unknown carriers and so on.

First, try the same input using the official demo page. If the result is different, then it might mean that a metadata update is due on this package, as the demo page always runs on the latest and official metadata version.

If the result is the same, it means there might be an issue with the currently available metadata. In that case, you should report your issue in the original project's issue tracker (moved out of GitHub on 05/12/2017).

This note will be posted on every issue regarding metadata troubles and it will be automatically closed.

Differences from other packages

google-libphonenumber does not try to be more than what it really is - a pre-compiled Google libphonenumber bundle that works on node.js. It is a 1:1 mirror of the original library without any further simplifications or optimizations.

  • All classes available from libphonenumber are exported as-is. No magic methods.
  • Always based on the latest google-closure library version available from Google with performance and bug fixes.
  • Relies on a simplified and well-documented update process to keep the underlying libphonenumber library always up-to-date.

If you're looking for a slightly simpler API, you should try awesome-phonenumber. It is based on the same concepts of this package but changes the API in order to make it more user friendly. You run the risk of bumping into other bugs and you'll have to learn new API types, but that's the necessary trade-off that the author made for achieving a generally better looking API.

libphonenumber-js is a much more radical approach to Google's libphonenumber. It is a rewrite of the original library based on its source phone metadata but implemented without depending on the Google Closure library. It also offers a tool to reduce the metadata to a set of countries which might be useful for frontend projects. It has several caveats, many of which make a lot of sense depending on the project, but you will have to ascertain those yourself.


There have been some users reporting successful but also unsuccessful usage with Webpack. While I don't personally use it, I'm 100% supportive of pull requests adding modifications that allow this package to better interact with it.

Chrome Extensions

Google Closure Compiler API, a serviced provided by Google to compile code online via its Closure library, may not always return fully compliant UTF-8-encoded output.

Loading extensions using this library on Google Chrome and other Chromium-based browsers may result in the following error when compiled with webpack:

Could not load file 'file.js' for content script. It isn't UTF-8 encoded.

While the local Java-based version supports a parameter which would let us workaround this issue at the source using --charset=US-ASCII, the online API version, which is a lot more convenient to use, does not offer support for an equivalent parameter (e.g. output_charset=US-ASCII).

In order to workaround this issue when using webpack, make sure to output US-ASCII characters only when defining TerserPlugin options, as demonstrated below:

optimization: {
  minimize: process.env.NODE_ENV !== 'development',
  minimizer: [
    new TerserPlugin({
      terserOptions: {
        output: {
          ascii_only: true


A small subset of tests guarantees that the main library functions are working as expected and are correctly exported. The actual heavy lifting is done by libphonenumber's extensive test suite.

npm test


npm version [<newversion> | major | minor | patch] -m "Release %s"


The exceptional work on libphonenumber was made possible by these committers and contributors.


This package is licensed under MIT. The bundled libphonenumber library is licensed under Apache 2.0.

*Note that all licence references and agreements mentioned in the google-libphonenumber README section above are relevant to that project's source code only.