Date Formats Around the World: DD/MM, MM/DD and YYYY-MM-DD

Three orders, many separators

Every numeric date puts three fields in some order. Day first runs from the smallest unit to the largest: 4/3/2026. Month first starts in the middle: 3/4/2026. Year first runs from the largest to the smallest: 2026-03-04. On top of the order, locales differ in separators (slash, dot, hyphen, a dot plus a space), in zero padding (03 or 3) and in whether the year has two or four digits.

Operating systems and browsers do not each invent these rules. The Unicode Common Locale Data Repository, CLDR, supplies the patterns, and its project page says CLDR is incorporated into all modern operating systems and browsers. When your phone shows a date, it is usually formatting it with a CLDR pattern for your language and region.

Short date patterns by locale

The table lists the CLDR 49 short date pattern, the shortest numeric format a locale defines, and what March 4, 2026 looks like in it.

Counted across these 21 locales:

• D-M-Y: 11 locales
• Y-M-D: 9 locales
• M-D-Y: 1 locale

Two details stand out. English in Canada uses year first, y-MM-dd, the same order as ISO 8601, while its medium pattern, MMM d, y, spells the month: Mar 4, 2026. And Hungarian and Korean end the date with a dot, which is part of the pattern and not a typo.

How to read a pattern

CLDR patterns follow the date field symbols in Unicode Technical Standard #35. The letters that matter for numeric dates:

The standard defines four lengths for each locale: full (usually with the weekday name), long (with the full month name), medium and short (usually with a numeric month). Only the short format is purely numeric in most locales, and it is the one that causes confusion.

Why 03/04/26 is a problem

Write 03/04/26 and three readers can see three different dates:

The day-first versus month-first clash is not rare. It happens whenever both the day and the month are 12 or less and they are different numbers. That is 12 × 12 = 144 combinations, minus the 12 where day and month are equal (5/5 reads the same either way), so 132 days a year, or 36.2 percent of a 365-day year. On every one of those days, a numeric date in an email to another country can be off by weeks or months.

A two-digit year adds the third reading in the table: a reader used to year-first dates sees 03 as the year. In 03/04/05 every one of the three numbers could be the year, the month or the day. Four-digit years fix that part immediately, because 2026 cannot be anything but a year.

Spelled-out dates differ too

Writing the month as a word removes the ambiguity, but the order still changes from place to place. The CLDR 49 long patterns for a few locales show it:

• English, United States: MMMM d, y, so March 4, 2026, with a comma before the year.
• English, United Kingdom: d MMMM y, so 4 March 2026, with no comma.
• German: d. MMMM y, so 4. März 2026, with a dot after the day.
• Spanish: the day, then de, the month, de and the year: 4 de marzo de 2026.
• Hungarian: y. MMMM d., year first even when spelled out.

None of these can be misread, which is why a spelled-out month is the safe choice in letters, contracts and emails across borders. The order is a matter of style; the meaning stays fixed. In the long form the year always has four digits, so the two-digit problem disappears as well.

ISO 8601: year, month, day

The W3C internationalization page sums up the standard in one line: ISO 8601 specifies a format of YYYY-MM-DD. March 4, 2026 is 2026-03-04. The page calls this format unambiguous and computer friendly, and also notes that it is not how most people write dates by hand.

Year first with fixed widths has one more advantage: dates sort as text in chronological order. File names like 2026-03-04-invoice.pdf line up by date in any folder, while 03-04-2026-invoice.pdf sorts all the March files of every year together. The guide to the ISO 8601 date format covers times, the T separator, time zones and the RFC 3339 profile.

Practical rules

• For people in other countries, write the month as a word and the year with four digits: 4 March 2026 or March 4, 2026. The W3C page suggests both measures.
• For files, spreadsheets and data, use 2026-03-04. It survives every locale and sorts correctly.
• For forms, show the expected pattern next to the field, for example DD/MM/YYYY, or use separate fields or a month dropdown.
• For code, store a timestamp or an ISO 8601 string and format it with the user's locale only when you display it. The Unix timestamp converter turns a stored timestamp into a readable date and back.
• For deadlines across borders, count with the date in an unambiguous form. The days between dates calculator takes the date from a picker, so the order never comes into play.

If you receive a numeric date and cannot tell the order, look for a day above 12 elsewhere in the same document: 25/03/2026 settles that the writer puts the day first. When nothing settles it, ask. Time zones cause the same kind of confusion one level down; the guide to UTC and time zones explains offsets.

Frequently asked questions

Sources

• Unicode CLDR project home (what CLDR is; incorporated into all modern operating systems and browsers; CLDR 49 released 2026-10-22)
• Unicode CLDR JSON data, cldr-dates-full, ca-gregorian.json per locale (the short date patterns in the table, version 49.0.0)
• Unicode Technical Standard #35, Part 4: Dates (the date field symbols y, yy, M, MM, MMM, MMMM, d, dd; the full, long, medium and short format lengths)
• W3C Internationalization: Date formats (ISO 8601 specifies YYYY-MM-DD; unambiguous and computer friendly; month names and four-digit years as a way to avoid confusion)

Written by Tobias. Updated October 30, 2026.