DD/MM/YYYY vs MM/DD/YYYY Who Uses Which?

Last reviewed on 2 October 2026.

Ambiguity checker: what does this date mean?

Type a numeric date in any common style, such as 01/05/2013, 1.5.13 or 05-13-2013, to see how it reads day-first and month-first.

Date format by country

The table shows the typical all-numeric format for everyday use, using 2 October 2026 as the example. Many countries also write dates with the month as a word, and official documents can differ from everyday habit. Where more than one numeric style is common, the notes say so. For locale data used by software, see Intl date formatting.

Filter countries or formats

Calendar notes refer to systems covered in Calendar Systems.

Why does the US write the month first?

The usual explanation is that MM/DD/YYYY copies the way Americans say a date: "October 2, 2026". Month-first spoken and written dates were also common in British English in earlier centuries. Over time British usage settled on day first ("2 October 2026") and the numeric form followed, while American usage kept the month first in both.

The US is not uniform even today. The US military writes day first (2 Oct 2026), and ISO 8601 dates are standard in US software, science and data exchange. The month-first numeric form is mostly a feature of everyday writing, paper forms and consumer software set to US English.

Little-endian, big-endian and middle-endian dates

Borrowing a term from computing, date orders are sometimes described by which end comes first:

• Little-endian, DD/MM/YYYY: the smallest unit (day) first, growing to the largest (year). Most of the world uses this order.
• Big-endian, YYYY-MM-DD: the largest unit first. Used in East Asia, Sweden, Hungary and Lithuania, and by ISO 8601.
• Middle-endian, MM/DD/YYYY: starts with the middle-sized unit. This is the US order.

Little-endian and big-endian orders are each consistent: the units always get bigger or always get smaller. Middle-endian is the odd one out, which is part of why it surprises people outside the US.

Why ISO 8601 avoids the problem

ISO 8601 writes dates as YYYY-MM-DD, so 2 October 2026 is 2026-10-02. Nobody uses a year-day-month order in practice, so a four-digit year at the start effectively settles the question. It has other advantages too:

• It sorts correctly as plain text, which makes it ideal for file names, spreadsheets and logs.
• It is the format behind HTML date inputs, JSON APIs and most database date literals (see dates in databases).
• It extends cleanly to times and time zones, e.g. 2026-10-02T14:30:00Z.

Practical advice: forms, spreadsheets and emails

Emails, letters and messages

If the reader might be in another country, write the month as a word: 2 October 2026 or October 2, 2026. Both are unambiguous, and abbreviations like 2 Oct 2026 work too. Avoid all-numeric dates in contracts, travel bookings and meeting invitations.

Web and paper forms

• Show the expected format next to the field, e.g. "DD/MM/YYYY", and give an example.
• Better still, use separate day, month and year fields with the month as a named dropdown, or a native date picker. HTML <input type="date"> shows the date in the user's own locale but always submits YYYY-MM-DD.
• Echo the date back in long form ("Friday, 2 October 2026") so people can spot a swap before submitting.

Spreadsheets and data files

• Store and exchange dates as YYYY-MM-DD; format them for display only at the end.
• When importing a CSV, choose the date order or locale explicitly rather than relying on the default.
• Spot-check imported data: if every "day" is 12 or less, the order may have been swapped silently.

When a form says "(dd/mm/yyyy)" or "use mm/dd/yyyy format"

Follow the hint literally, even if it is not the order you are used to. The system is going to read the digits in that order, whatever you meant.

• "(dd/mm/yyyy)" or "DD/MM/YYYY": day, then month, then a four-digit year. 2 October 2026 is 02/10/2026.
• "mm/dd/yyyy" or "This system uses US date format (MM/DD/YYYY)": month, then day. 2 October 2026 is 10/02/2026.
• "yyyy-mm-dd": 2026-10-02.

Keep leading zeros (02, not 2) when the hint shows two letters, and use the separator shown. If the confirmation page shows the date in words, check that it is the date you meant. On paper forms that are processed abroad, adding the month as a word ("02/OCT/2026") can prevent mistakes if the form allows it.

How Excel and browsers interpret ambiguous dates

Excel and other spreadsheets

Excel reads typed dates according to the operating system's regional settings. On a computer set to US English, typing 01/05/2013 gives 5 January 2013; on one set to UK English, the same keystrokes give 1 May 2013. Values that do not fit the expected order, like 25/12/2026 on a US-configured machine, are usually kept as text rather than converted, so a single column can end up as a mix of real dates and text. Opening a CSV by double-clicking applies the same regional settings; the import tools (such as From Text/CSV or Text to Columns) let you specify the locale or the DMY/MDY order. Google Sheets uses the spreadsheet's locale setting in the same way.

Browsers and JavaScript

Browsers display dates according to the user's language and region settings, which is why the same page can show 02/10/2026 to one visitor and 10/02/2026 to another. When code parses a date string, the only format JavaScript guarantees is the ISO 8601 form. Strings such as "01/05/2013" fall back to engine-specific behaviour; in practice the major engines read slashed dates month-first regardless of the user's locale, so new Date("01/05/2013") is 5 January. Do not rely on that: parse with an explicit format, as described in date parsing pitfalls, and format for display with Intl.DateTimeFormat. You can find the format tokens for each language in date format codes, or convert a date with the date converter.

Frequently asked questions