CONVERT TOOL
Date Format Converter
Convert any readable date into every common format at once: ISO 8601, US month-first, European day-first, compact, long form, and weekday variants. Ambiguous numeric dates are flagged instead of guessed — you choose whether 04/05/2026 means 4 May or 5 April.
Ambiguous numeric dates are resolved with the selected day/month order.
Dates are written differently almost everywhere. The same day can be 2026-04-05, 04/05/2026, 05/04/2026, or "April 5, 2026", and the slash formats disagree about which number is the month. That disagreement is not cosmetic: reading a date the wrong way can move a deadline by weeks or swap two people's event dates.
Type or paste a date in almost any common layout — ISO, slash-separated, dotted, a written month name, or the compact eight-digit form — then pick the day/month order when the numbers alone cannot settle it. The converter returns the resolved date with its weekday and every standard representation of it, ready to copy into a form, an import, or a document.
How to Use the Date Format Converter
- Enter the date in any layout you have — for example 2026-04-05, 05/04/2026, or May 5 2026.
- If the numbers are ambiguous (both parts 12 or smaller), choose the correct order: day first for European dates, month first for US dates.
- Select "Convert date".
- Copy the format you need from the results table — ISO 8601 is the safe default for systems and files.
Why Numeric Dates Are Ambiguous
In 03/04/2026, is the month March and the day 4th, or is the day the 3rd of April? Both readings are valid somewhere in the world. The US writes month first; most of Europe and much of Asia, Africa, and Latin America write day first; ISO 8601 puts the year first and removes the question entirely.
Note: The converter never guesses when both readings are possible. Auto-detect resolves dates it can prove — like 13/04/2026, which can only be day-first — and asks you to pick an order for the rest.
ISO 8601 and Why Systems Prefer It
ISO 8601 writes dates as YYYY-MM-DD: 2026-04-05. Sorting strings in ISO order matches sorting them chronologically, the year comes first so decades are never confused, and there is no day/month ambiguity. Databases, APIs, configuration files, and filenames all benefit from it.
The compact variant (20260405) follows the same year-month-day order and is common in file naming and batch identifiers.
US vs European Order at a Glance
| Format | Pattern | Example (5 April 2026) | Example (4 May 2026) |
|---|---|---|---|
| US (month first) | MM/DD/YYYY | 04/05/2026 | 05/04/2026 |
| European (day first) | DD/MM/YYYY | 05/04/2026 | 04/05/2026 |
| ISO 8601 | YYYY-MM-DD | 2026-04-05 | 2026-05-04 |
| Long form | D Month YYYY | 5 April 2026 | 4 May 2026 |
Notice that the two slash formats swap each other's strings — which is exactly why a date exported from one region and imported into another can silently shift by weeks.
How the Converter Works
- The input is matched against known layouts: ISO and compact first, then numeric with separators, then written month names.
- ISO and unambiguous inputs are accepted immediately, whatever order is selected.
- For numeric dates where both parts are 12 or smaller, the calculator checks your chosen order — day first, month first, auto-detect, or ISO only.
- The resolved date is validated against the real calendar, so 31 February is rejected rather than rolled into March.
- Every supported representation of the resolved date is produced from that single validated date.
Choosing a Format for Your Audience
Use ISO 8601 in systems, filenames, logs, and anywhere dates are sorted or parsed. Use the local convention of your audience for prose and forms — and if a document crosses borders, write the month name instead of the number. The Date and Time Formats guide explains the trade-offs in more depth.
Converted dates are often inputs to another calculation. Feed the resolved date into the Date Calculator or Days Between Dates once you know what it means.
Dates and Times Together: ISO 8601 and RFC 3339
When a date carries a time, ISO 8601 joins the two with a capital T: 2026-11-04T09:30:00. A zone marker then fixes the instant — Z for UTC, or an offset such as +01:00 for local time — so 2026-11-04T09:30:00Z and 2026-11-04T10:30:00+01:00 describe the same moment in two different local readings.
RFC 3339, the Internet Engineering Task Force profile of ISO 8601, is the form you meet in APIs, logs, and JSON payloads. It narrows ISO 8601 to one complete, unambiguous layout — four-digit year, full date, 24-hour clock, and a mandatory zone — so two programs can never disagree about what a timestamp means. Calendar files follow the same philosophy: RFC 5545 stores an all-day date in the basic ISO form without separators, for example 20261104 for 4 November 2026.
This converter works on the date portion of any of those layouts. To move a full timestamp between zones, use the Time Zone Converter — it applies the offset arithmetic that a date-only tool deliberately skips.
Format Comparison: Which Layout to Use Where
Written-month forms — 4 November 2026 or November 4, 2026 — are the safest for human readers, because there is no pair of numbers to misread. The numeric forms are compact, which is exactly what makes them risky across borders.
| Format | Pattern | Example (4 November 2026) | Best used for | Risk |
|---|---|---|---|---|
| ISO 8601 extended | YYYY-MM-DD | 2026-11-04 | Databases, APIs, filenames, sorting | Low — year first, no ambiguity |
| ISO 8601 basic | YYYYMMDD | 20261104 | File names, batch IDs, calendar files | Low — harder for humans to scan |
| US month first | MM/DD/YYYY | 11/04/2026 | US forms and correspondence | High outside the US |
| European day first | DD/MM/YYYY | 04/11/2026 | UK, EU and most other forms | High outside those regions |
| Written month | D Month YYYY | 4 November 2026 | Contracts, cross-border documents | Low — unambiguous in that language |
Sorting is the quiet advantage of ISO: the year comes first and every field is fixed width, so plain text sorting of ISO dates is already chronological. Lexicographic sorting of 11/04/2026 and 04/11/2026 mixes them up completely, which is why exports and filenames are safer in YYYY-MM-DD.
Common Date Data-Entry and Import Mistakes
- Reading a slashed date in the wrong order. 03/04/2026 is 4 March to a US reader and 3 April to most others — a 30-day error that no validation catches.
- Letting a spreadsheet guess the layout. Importing 04.05.2026 into a workbook set to a US locale stores 4 May; format the column as text, or export ISO, before importing.
- Two-digit years. 01/02/03 can be read as 2001, 2002, or 2003 depending on the system's pivot year. Four-digit years remove the question entirely.
- Accepting rolled-over dates. Some tools silently turn 2026-02-30 into 2 March; this converter rejects the input instead, so a typo surfaces immediately.
- Assuming a filename sorts chronologically. report-4-5-2026.txt does not order by date; report-2026-05-04.txt does.
Related Tools
Check the weekday of the resolved date with the Day of the Week Calculator, move it by a duration with Add Days to Date, and see which ordinal day of the year it is with the Day of Year Calculator.
Method, checked examples, and limits
The input is parsed as ISO, compact, numeric, or named-month date. Numeric dates that could be day-first or month-first are flagged as ambiguous unless the day/month order is chosen. The resolved date is then rendered in nine common formats.
Assumptions
- Years are four digits; two-digit years are not guessed.
- A numeric date is ambiguous when both day and month are 12 or less and no order is selected.
- The output is a calendar date, not a time zone conversion.
Examples you can reproduce
| Input | Result | Why it matters |
|---|---|---|
| 03/04/2026, day-first | 3 April 2026 (Friday) · ISO 2026-04-03 · US 04/03/2026 · EU 03/04/2026 | — |
| 03/04/2026, month-first | 4 March 2026 (Wednesday) · ISO 2026-03-04 · US 03/04/2026 · EU 04/03/2026 | — |
| 2026-10-03 | 3 October 2026 (Saturday) | — |
| 03/04/2026, auto | Ambiguous; choose day-first or month-first. | — |
These examples were produced with the same calculation functions the tool uses. Enter the inputs above to reproduce them.
Known limitations
- Does not expand two-digit years.
- Does not convert times or time zones.
- Ambiguous dates are intentionally not guessed.
Rules and definitions: ISO — ISO 8601 date and time format, RFC 3339 — Date and Time on the Internet: Timestamps, RFC 5545 — Internet Calendaring and Scheduling Core Object Specification (iCalendar)
Read the full testing methodology, the editorial standards, or report a problem.
Related Calculators
Related Guides
Frequently Asked Questions
Which date format should I use in a spreadsheet or database?
ISO 8601 (YYYY-MM-DD). It sorts correctly as text, removes day/month ambiguity, and is understood by virtually every system.
How do I know if 04/05/2026 is April 5th or May 4th?
You cannot tell from the numbers alone. Select day-first or month-first to match how the date was written, or ask the source. The converter flags the ambiguity instead of guessing.
Can the converter read dates like "3 Oct 2026" or "October 3, 2026"?
Yes. Written month names are unambiguous, so they are accepted directly in either day-first or month-first phrasing.
Does it accept times too?
No. This tool converts date layouts only. For date and time values across zones, use the Time Zone Converter.
Why does my imported date keep shifting by months?
The file was probably written day-first and read month-first, or the reverse. Re-export in ISO 8601 and the shifts stop.
Why do databases and filenames prefer YYYY-MM-DD?
Because it is the only common layout where text order matches chronological order: the year leads and every component is fixed width, so sorting strings sorts dates. It is also the ISO 8601 standard form, so any system that parses it knows exactly what it received — no day/month guessing, no locale settings.
What is the difference between ISO 8601 and RFC 3339?
ISO 8601 is the international standard covering dates, times, and intervals in many representations. RFC 3339 is the IETF profile that selects one of them for Internet protocols: a complete date, a capital T, a 24-hour time, and a mandatory Z or numeric offset. If you store API timestamps, RFC 3339 is the form to write.