Every common date format, explained — MM/DD/YYYY, DD/MM/YYYY, YYYY-MM-DD, and 15 more — with country-by-country usage, Excel pitfalls, and one tool to convert between them all.
If you landed here from a search like "what is the date today mm/dd/yyyy" or "dd/mm/yyyy vs mm/dd/yyyy", here's the short answer: the date format you see depends entirely on where the form, document, or system was built. The United States writes today as MM/DD/YYYY. Most of the rest of the world — the UK, India, Australia, the EU — writes it as DD/MM/YYYY. Computers and any sane API write it as YYYY-MM-DD. The number is the same; only the order changes.
This cheat sheet covers every format you'll ever encounter, why the world hasn't agreed on one, and the common pitfalls (especially in Excel and DOB fields) that quietly corrupt data every day. When you need to actually convert one to another, use the Date Format Converter — it shows any date you pick in 20+ formats simultaneously, in your browser, with one-click copy.
Take any single date — say 28 May 2026 — and here's how the same day looks across the formats real systems use:
MM/DD/YYYY → 05/28/2026 (United States)
DD/MM/YYYY → 28/05/2026 (UK, India, Australia, most of Europe)
YYYY-MM-DD → 2026-05-28 (ISO 8601 — APIs, databases, file names)
DD.MM.YYYY → 28.05.2026 (Germany, Russia, much of Eastern Europe)
YYYY/MM/DD → 2026/05/28 (Japan, Korea, China)
D MMM YYYY → 28 May 2026 (UK long form, journalism)
MMMM D, YYYY → May 28, 2026 (US long form)
DD-MMM-YY → 28-MAY-26 (Oracle databases, banking)
DDMMYYYY → 28052026 (compact, common on Indian government forms)
MMDDYY → 052826 (US compact, credit-card expiry style)
Unix timestamp → 1748390400 (seconds since 1970-01-01 UTC)
Drop any date into the Date Format Converter and all of these update at once — useful when you're copying a date from one system into another and want zero ambiguity.
Three big cultural conventions evolved in parallel and never reconciled:
The US writes dates the same way it speaks them: "May 28, 2026". That spoken order — month first — carried into the numeric form. It's used almost nowhere else and routinely confuses every visitor and every API integration.
Most of the world writes dates from smallest unit (day) to largest (year) — the way you'd file paper records or sort by recency. The UK, India, Australia, New Zealand, South Africa, and most of continental Europe use this. Spoken: "28 May 2026".
The ISO 8601 international standard puts the largest unit first — year, then month, then day. This sorts correctly as plain text (a file called 2026-05-28-invoice.pdf naturally comes after 2026-04-15-invoice.pdf in any file browser), is unambiguous internationally, and is the only format you should use inside code, databases, APIs, JSON payloads, and file names. If you're a developer, this is the only format that matters.
The single most common date-format mistake happens in date-of-birth (DOB) fields. A US-built form asks for "DOB (MM/DD/YYYY)" and an Indian user types 05/28/2026 meaning "28th May" — but the form parses it as "May 28th". For dates where day ≤ 12, the bug is invisible — 05/08/2026 could be 8 May or 5 August and the system happily accepts either, silently storing the wrong birthday.
If you build forms, always:
Show an explicit example next to the field: e.g. 28/05/2026 for 28th May 2026.
Use a date picker rather than a free-text field whenever possible.
Internally store everything as ISO 8601 (2026-05-28) regardless of what the user sees.
For age calculations from DOB, use the Age Calculator — it handles leap years, varying month lengths, and birthday boundaries correctly.
Excel is the single biggest source of date corruption in business data. The problems:
Auto-conversion of CSV imports. Open a CSV in Excel and any column that looks like a date gets "helpfully" reformatted to Excel's locale — usually MM/DD/YYYY on US installs, DD/MM/YYYY on UK installs. The original string is gone. The fix: import via Data > From Text rather than double-click, and force the column type to Text.
Two-digit years. Excel guesses the century. 05/28/26 becomes 2026 (probably), but 05/28/49 might become 1949 or 2049 depending on the version. Always use 4-digit years.
Locale-dependent re-export. The same workbook opened on a US laptop versus a UK laptop will display the same underlying date differently. If you email a CSV between offices, dates can silently swap meaning.
The 1900-02-29 bug. Excel believes 1900 was a leap year. It wasn't. This is preserved for Lotus 1-2-3 compatibility and quietly throws off date arithmetic across that boundary.
For any data exchange that involves dates, agree on ISO 8601 (YYYY-MM-DD) at the schema level and convert at the display boundary only. The Date Format Converter can turn ISO dates back into the locale-friendly form for end-user display.
If you're building forms, sending invoices, or designing UI for an international audience, this is the format the user expects in plain text:
United States, Canada (English): MM/DD/YYYY (05/28/2026)
United Kingdom, Ireland: DD/MM/YYYY (28/05/2026)
India, Pakistan, Bangladesh, Sri Lanka: DD/MM/YYYY (28/05/2026)
Australia, New Zealand: DD/MM/YYYY (28/05/2026)
Germany, Austria, Switzerland: DD.MM.YYYY (28.05.2026)
France, Spain, Italy, Portugal: DD/MM/YYYY (28/05/2026)
Netherlands, Belgium: DD-MM-YYYY (28-05-2026)
Russia, Ukraine: DD.MM.YYYY (28.05.2026)
Japan, Korea, China: YYYY/MM/DD (2026/05/28) or with native ideographs
Iran, most Arab countries: DD/MM/YYYY (often with Arabic/Persian numerals)
Mexico, most of Latin America: DD/MM/YYYY (28/05/2026)
Brazil: DD/MM/YYYY (28/05/2026)
Heuristic when you can't tell: if the day is > 12 (e.g. 28), the format is unambiguously DD/MM/YYYY. If you see 14/05/2026, no US system would have produced it — safe to read as 14 May.
Format conversion answers "how do I write this date for that audience?" — but most date questions are actually arithmetic:
How old is someone? → Age Calculator takes a DOB and returns years, months, days, hours, even seconds.
How many days between two dates? → Days Between Two Dates Calculator handles project deadlines, contract durations, and trip planning.
What's the date 90 days from today? → same tool, with add/subtract.
These three calculators (format converter + age + days-between) cover roughly 95% of everyday date questions. None require signup; everything runs in your browser.
Today's date written in MM/DD/YYYY format is the current US-style date — for example, May 28th 2026 is written 05/28/2026. Use the Date Format Converter to see today's date (or any date you pick) instantly in MM/DD/YYYY, DD/MM/YYYY, YYYY-MM-DD, and 20+ other formats simultaneously.
The UK and most of the Commonwealth (plus continental Europe) write dates smallest unit first: day, then month, then year. The US is one of the few countries that puts month first. Neither is more "correct" — they're just different historical conventions.
For computers, yes — unambiguously. YYYY-MM-DD (ISO 8601) sorts correctly as plain text, is internationally unambiguous, and is the standard in JSON, SQL, and most APIs. For human-facing UI, use whatever your audience expects locally.
ISO 8601 specifies YYYY-MM-DD for dates and YYYY-MM-DDTHH:mm:ssZ for date-times in UTC. Always use this format inside code, databases, and data exchange — convert to a local format only at the moment of display.
Don't double-click the CSV. Open Excel first, then use Data > From Text/CSV, and explicitly mark date columns as Text in the import wizard. This preserves the original string and prevents Excel's locale from silently swapping day and month.
Pair a date-picker UI (so the user picks visually) with an explicit example label like "DD/MM/YYYY (e.g. 28/05/2026)". Internally, store as ISO 8601. Never rely on free-text date input across international audiences — ambiguity will silently corrupt your data.
Date formats are messy because the world is messy — cultures don't agree, software makes assumptions, and form designers forget to label their fields. The defensive playbook:
Inside code and data, always use ISO 8601 (YYYY-MM-DD).
At display, use the format your audience expects (US: MM/DD/YYYY, most of the world: DD/MM/YYYY).
Convert between them with a tool, not by hand — bookmark the Date Format Converter for the next time a date crosses a system boundary.
Compute, don't count — use the Age Calculator and Days Between Dates tool for any arithmetic. Mental month-math is where bugs come from.
Creating helpful tools and sharing productivity insights to make your work easier.
Convert dates between DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD, and 20+ other date formats. Free online date format converter with custom format support and one-click copy.
Send a WhatsApp message to any number without saving it to your contacts. Free, instant, no signup — perfect for businesses and one-off chats.
Generate custom QR codes for URLs, vCards, Wi-Fi, text, and more — high-resolution PNG and SVG download, free.
Convert between gold karats, purity percentage, touch, tunch, and 916/750/585/375 hallmark markings. Free online gold karat calculator and purity converter.
Convert byte arrays to strings online. Decode space- or comma-separated bytes (decimal, hex, or binary) to UTF-8 text. Free browser-based byte-to-string converter.