Your Search Results



    The toLocaleDateString() method returns a string with a language sensitive representation of the date portion of this date. The new locales and options arguments let applications specify the language whose formatting conventions should be used and allow to customize the behavior of the function. In older implementations, which ignore the locales and options arguments, the locale used and the form of the string returned are entirely implementation dependent.


    dateObj.toLocaleDateString([locales [, options]])


    Check the Browser compatibility section to see which browsers support the locales and options arguments, and the Example: Checking for support for locales and options arguments for feature detection.


    Optional. A string with a BCP 47 language tag, or an array of such strings. For the general form and interpretation of the locales argument, see the Intl page. The following Unicode extension keys are allowed:

    Numbering system. Possible values include: "arab", "arabext", "bali", "beng", "deva", "fullwide", "gujr", "guru", "hanidec", "khmr", "knda", "laoo", "latn", "limb", "mlym", "mong", "mymr", "orya", "tamldec", "telu", "thai", "tibt".
    Calendar. Possible values include: "buddhist", "chinese", "coptic", "ethioaa", "ethiopic", "gregory", "hebrew", "indian", "islamic", "islamicc", "iso8601", "japanese", "persian", "roc".

    Optional. An object with some or all of the following properties:

    The locale matching algorithm to use. Possible values are "lookup" and "best fit"; the default is "best fit". For information about this option, see the Intl page.
    The time zone to use. The only value implementations must recognize is "UTC"; the default is the runtime's default time zone. Implementations may also recognize the time zone names of the IANA time zone database, such as "Asia/Shanghai", "Asia/Kolkata", "America/New_York".
    Whether to use 12-hour time (as opposed to 24-hour time). Possible values are true and false; the default is locale dependent.
    The format matching algorithm to use. Possible values are "basic" and "best fit"; the default is "best fit". See the following paragraphs for information about the use of this property.

    The following properties describe the date-time components to use in formatted output, and their desired representations. Implementations are required to support at least the following subsets:

    • weekday, year, month, day, hour, minute, second
    • weekday, year, month, day
    • year, month, day
    • year, month
    • month, day
    • hour, minute, second
    • hour, minute

    Implementations may support other subsets, and requests will be negotiated against all available subset-representation combinations to find the best match. Two algorithms are available for this negotiation and selected by the formatMatcher property: A fully specified "basic" algorithm and an implementation dependent "best fit" algorithm.

    The representation of the weekday. Possible values are "narrow", "short", "long".
    The representation of the era. Possible values are "narrow", "short", "long".
    The representation of the year. Possible values are "numeric", "2-digit".
    The representation of the month. Possible values are "numeric", "2-digit", "narrow", "short", "long".
    The representation of the day. Possible values are "numeric", "2-digit".
    The representation of the hour. Possible values are "numeric", "2-digit".
    The representation of the minute. Possible values are "numeric", "2-digit".
    The representation of the second. Possible values are "numeric", "2-digit".
    The representation of the time zone name. Possible values are "short", "long".

    The default value for each date-time component property is undefined, but if the weekday, year, month, day properties are all undefined, then year, month, and day are assumed to be "numeric".


    Example: Using toLocaleDateString()

    In basic use without specifying a locale, a formatted string in the default locale and with default options is returned.

    var date = new Date(Date.UTC(2012, 11, 12, 3, 0, 0));
    // toLocaleDateString() without arguments depends on the implementation,
    // the default locale, and the default time zone
    // → "12/11/2012" if run in en-US locale with time zone America/Los_Angeles

    Example: Checking for support for locales and options arguments

    The locales and options arguments are not supported in all browsers yet. To check whether an implementation supports them already, you can use the requirement that illegal language tags are rejected with a RangeError exception:

    function toLocaleDateStringSupportsLocales() {
      try {
        new Date().toLocaleDateString('i');
      } catch (e) {
        return e​.name === 'RangeError';
      return false;

    Example: Using locales

    This example shows some of the variations in localized date formats. In order to get the format of the language used in the user interface of your application, make sure to specify that language (and possibly some fallback languages) using the locales argument:

    var date = new Date(Date.UTC(2012, 11, 20, 3, 0, 0));
    // formats below assume the local time zone of the locale;
    // America/Los_Angeles for the US
    // US English uses month-day-year order
    // → "12/19/2012"
    // British English uses day-month-year order
    // → "20/12/2012"
    // Korean uses year-month-day order
    // → "2012. 12. 20."
    // Arabic in most Arabic speaking countries uses real Arabic digits
    // → "٢٠‏/١٢‏/٢٠١٢"
    // for Japanese, applications may want to use the Japanese calendar,
    // where 2012 was the year 24 of the Heisei era
    // → "24/12/20"
    // when requesting a language that may not be supported, such as
    // Balinese, include a fallback language, in this case Indonesian
    console.log(date.toLocaleDateString(['ban', 'id']));
    // → "20/12/2012"

    Example: Using options

    The results provided by toLocaleDateString() can be customized using the options argument:

    var date = new Date(Date.UTC(2012, 11, 20, 3, 0, 0));
    // request a weekday along with a long date
    var options = { weekday: 'long', year: 'numeric', month: 'long', day: 'numeric' };
    console.log(date.toLocaleDateString('de-DE', options));
    // → "Donnerstag, 20. Dezember 2012"
    // an application may want to use UTC and make that visible
    options.timeZone = 'UTC';
    options.timeZoneName = 'short';
    console.log(date.toLocaleDateString('en-US', options));
    // → "Thursday, December 20, 2012, GMT"


    When formatting large numbers of dates, it is better to create an Intl.DateTimeFormat object and use the function provided by its format property.


    Specification Status Comment
    ECMAScript 3rd Edition. Standard Initial definition. Implemented in JavaScript 1.0.
    ECMAScript 5.1 (ECMA-262)
    The definition of 'Date.prototype.toLocaleDateString' in that specification.
    ECMAScript 6 (ECMA-262)
    The definition of 'Date.prototype.toLocaleDateString' in that specification.
    Release Candidate  
    ECMAScript Internationalization API 1.0 (ECMA-402)
    The definition of 'Date.prototype.toLocaleDateString' in that specification.
    Standard Defines locales and options arguments.

    Browser compatibility

    Feature Chrome Firefox (Gecko) Internet Explorer Opera Safari
    Basic support (Yes) (Yes) (Yes) (Yes) (Yes)
    locales and options arguments 24 + Support for passing timeZones other than UTC 29 (29) 11 15 Not supported
    Feature Android Chrome for Android Firefox Mobile (Gecko) IE Mobile Opera Mobile Safari Mobile
    Basic support (Yes) (Yes) (Yes) (Yes) (Yes) (Yes)
    locales and options arguments Not supported 26 Not supported
    bug 864843
    Not supported Not supported Not supported

    See also

    Document Tags and Contributors

    Last updated by: Sheppy,
    Hide Sidebar