Date Format Converter
ProductivityConvert a date into US (MM/DD/YYYY), international (DD/MM/YYYY), ISO 8601, and other common formats, or decode an ambiguous numeric date like 03/04/2026 to see what it actually means.
Convert a date
United States (MM/DD/YYYY)
08/10/2026
UK, EU, Brazil, Vietnam (DD/MM/YYYY)
10/08/2026
ISO 8601 — unambiguous everywhere (YYYY-MM-DD)
2026-08-10
China, Japan, Korea (YYYY/MM/DD)
2026/08/10
Long form
August 10, 2026
Decode an ambiguous date
Paste a numeric date someone sent you and see how it reads under each convention.
If US format (MM/DD/YYYY)
March 4, 2026
If UK/EU/Brazil/Vietnam format (DD/MM/YYYY)
April 3, 2026
Both readings are valid calendar dates — genuinely ambiguous without knowing which convention the sender used. If only one side above shows a date, that's the correct reading (the other one isn't a real date).
Why date formats differ by country
The United States writes dates month-first (MM/DD/YYYY), while the United Kingdom, most of Europe, Brazil, and Vietnam write them day-first (DD/MM/YYYY). China, Japan, and South Korea typically write them year-first (YYYY/MM/DD) — largest unit to smallest, the same logic behind the ISO 8601 standard. None of these conventions is more 'correct' than another; they're just different, long-established norms, which is exactly why a date written as a short numeric string doesn't reliably travel across countries without confusion.
The ambiguity problem
A date like 01/02/2026 means January 2nd to an American reader and February 1st to a British, Brazilian, or Vietnamese one — and both readings are perfectly valid calendar dates, so there's no way to tell which one is meant just by looking at it. The confusion only becomes obvious when one of the numbers is greater than 12, since only one reading can be a real date in that case (03/25/2026 can only be March 25th — no country writes a 25th month). Below 13, though, the ambiguity is completely silent, and it's a genuine source of missed flights, wrong deadlines, and misfiled paperwork when a date crosses between date-format conventions without anyone noticing.
Common use cases
People use a date format converter to safely rewrite a date before sending it to someone in a different country, to double-check a form field that expects a specific format, to convert a date for a spreadsheet or CSV import that requires ISO 8601, and to decode a confusing date they've received in an email, invoice, or document from abroad. Developers reach for it when preparing example data or documentation meant for an international audience, where a silently misread date can cause a hard-to-spot bug.
How to avoid the ambiguity going forward
The most reliable fix is to default to ISO 8601 (YYYY-MM-DD) whenever the audience or system isn't guaranteed to share your date convention — it's the international standard specifically because the year-first, zero-padded structure can't be confused with any other common format, and it's what most databases, APIs, and spreadsheet imports expect by default. When writing a date for a general audience rather than a system, spelling out the month by name ("3 April 2026" or "April 3, 2026") removes the ambiguity just as effectively, since a name can't be misread as a different number the way a digit can.
How to use Date Format Converter
- 1Pick a date to see it instantly written out in US, international, ISO 8601, and other common formats.
- 2Or paste a confusing numeric date you've received into the decoder.
- 3Read both possible readings — if only one is a valid calendar date, that's the correct one.
Frequently asked questions
What does 03/04/2026 mean?
It depends on the convention: April 3, 2026 if read as US format (MM/DD/YYYY), or March 4, 2026 if read as international format (DD/MM/YYYY). Both are valid dates, so it's genuinely ambiguous without knowing which convention the writer used — paste it into the decoder above to see both readings side by side.
How can I tell which format a date is in?
If either number is greater than 12, it can only be a day, which resolves the ambiguity immediately. If both numbers are 12 or under, there's no way to tell for certain from the date alone — you'd need to know the convention the source normally uses.
Which format should I use to avoid this problem entirely?
ISO 8601 (YYYY-MM-DD) — it's the international standard precisely because its year-first, zero-padded structure isn't mistakable for any other common date format.
Is my date information sent anywhere?
No — every conversion and every decode happens locally in your browser using JavaScript's built-in date handling.
Does this handle two-digit years, like 03/04/26?
Yes — two-digit years are expanded using the standard convention (00–69 becomes 2000–2069, 70–99 becomes 1970–1999), though writing out the full four-digit year is always safer when it matters.