JSON Data from the Unicode CLDR Project



JSON distribution of CLDR locale data for internationalization

It should be noted that XML (not JSON) is the "official" format for all CLDR data. The JSON data contained in the packages described below is provided as a convenience for the development community, and is programatically generated from the corresponding XML, using the JSON conversion utility that is provided as part of the CLDR tooling (written in Java).

The data in these packages is intended to serve as a common reference point for most JavaScript packages. As such, this JSON data is generated using only data that has achieved draft="contributed" or draft="approved" status in the CLDR. This is the same threshhold as is used by the ICU (International Components for Unicode).

If you require JSON data containing provisional or unconfirmed data, or data that is customized in any way, you can generate it using the Ldml2JSON conversion utility in CLDR's tools distribution (org.unicode.cldr.json).


Latest official release is version 30.0.3, published on 2016-12-13


Each repository is tagged with the release it pertains to, for example 30.0.3.


This project is distributed by the Unicode Consortium Terms of Use


This project requires the following other projects to run:

  • none

Package Organization

Because the CLDR is so large and contains so many different types of information, the JSON data here is grouped into packages by functionality. For each type of functionality, there are two available packages: The "modern" packages, which contain the set of locales listed as modern coverage targets by the CLDR subcomittee, and the "full" packages, which contain the complete set of locales, including those in the corresponding modern packages. The functional groups are:


Installation using NPM:

$ npm install <package-name> , where <package-name> is one of the package names mentioned above, for example:

$ npm install cldr-dates-full

Installation using bower:

$ bower install <package-name> , where <package-name> is one of the package names mentioned above, for example:

$ bower install cldr-dates-full

Bug reports

CLDR does NOT use Github's issue tracking system to track bugs. If you find an error in the data contained here, please file a new ticket at http://unicode.org/cldr/trac/newticket