A date format converter chart compares one selected date across ISO 8601, US, European, long, weekday, ordinal, date-to-words, and Unix forms.

The practical task is to find the exact notation a filename, form, spreadsheet, database, contract, or script expects without confusing month-first dates with day-first dates. A chart is useful because it shows the alternatives together: the US and European numeric lines may look similar even though their component order is different, while the ISO line removes that ambiguity.

The Date Format Converter performs that comparison for one date at a time. Choose a date and it displays every supported form immediately, each on its own line with a Copy control. This gives you a ready-to-use choice for technical systems, formal prose, and scripts instead of making you reconstruct each format by hand.

date format converter chart
Date Format Converter Chart: US, ISO, EU Compared

The Date Format Comparison Chart

The sample column below uses July 6, 2026 throughout so the difference in ordering is visible. Read the pattern column as the general rule, then use the example to recognize what the selected date will look like.

Format Pattern or rule Example or output rule Best fit
ISO 8601 YYYY-MM-DD 2026-07-06 Filenames, databases, and spreadsheets
US numeric MM/DD/YYYY 07/06/2026 Systems explicitly using month-first dates
European numeric DD/MM/YYYY 06/07/2026 Systems explicitly using day-first dates
US long Month D, YYYY July 6, 2026 Readable US-style prose
European long D Month YYYY 6 July 2026 Readable day-first prose
Full weekday Weekday, Month D, YYYY Monday, July 6, 2026 Headings and event references
Ordinal day Day with an English suffix 6th Numbered headings and day references
Date to words, British or formal Written day, month, and year the sixth of July, twenty twenty-six Formal documents and cheques
Date to words, American Written month, day, and year July sixth, two thousand twenty-six Contracts and invitations
Unix timestamp Epoch seconds at UTC midnight Calculated for the selected date Code, logs, and APIs

The chart contains several kinds of output. ISO, US, and European lines are numeric; long and date-to-words lines spell out components; the ordinal line isolates the day with its suffix; and Unix encodes the selected date as seconds since the epoch. Because the converter labels every line, check the label rather than guessing from the digits alone.

Convert a Date in Three Steps

  1. Pick a date in the date field. The field defaults to today, so verify that default when you need a different date.
  2. Read every format shown below the field. The outputs include ISO, US, European, long, weekday, ordinal, words, and Unix. Check each label before choosing a numeric line.
  3. Click Copy on the line you need. The exact displayed format is placed on your clipboard, ready to paste into the destination without retyping it.

The supported workflow handles a single selected date rather than a range or batch of dates. Its input is a date, not a date-and-time value, so it does not preserve or add a time of day. For each additional date, select it again, review the updated lines, and copy the required format. This distinction matters when a destination expects a timestamp: use the Unix line for epoch seconds rather than treating the numeric date as a time.

Numeric Order and ISO Clarity

Begin by identifying the numeric convention required by the destination. In the chart’s sample, the US line reads 07/06/2026 because the month comes first, so it means July 6. The European line reads 06/07/2026 because the day comes first, and it means the same date. Both forms are valid in their respective contexts, but swapping their order changes the meaning.

ISO 8601 removes that uncertainty by using year-month-day, displayed as 2026-07-06 for the sample. The order is unambiguous, and it sorts correctly as plain text. That makes ISO the safest choice for filenames, database columns, and spreadsheet cells, especially when dates may be reviewed or sorted by people working in different regions.

ISO does not replace a local convention when a system explicitly requires one particular order. If a form requests MM/DD/YYYY, choose the US line; if it requests DD/MM/YYYY, choose the European line. Use ISO for technical workflows that value a consistent, sortable representation, and use the requested local format when the destination rules are already fixed.

Long, Word, and Ordinal Formats

The long outputs provide three readable styles. The US form is written as July 6, 2026, the European form places the day first as 6 July 2026, and the full weekday form adds the weekday as Monday, July 6, 2026. These are useful when a date needs to read naturally rather than behave like a database field.

Date to words offers two accepted conventions. The British or formal style writes the day as an ordinal followed by “of,” producing the sixth of July, twenty twenty-six. The American style puts the month first, producing July sixth, two thousand twenty-six. Both spell out the day and year fully, making them suitable for cheques, contracts, invitations, and other prose where a compact numeric value could be misread.

The ordinal line applies the standard English suffix rule. Most numbers take -th, while numbers ending in 1, 2, or 3 normally take -st, -nd, or -rd. The important exceptions are 11th, 12th, and 13th, which retain -th because they are pronounced eleventh, twelfth, and thirteenth. For the chart’s selected day, the result is 6th.

Reading the Unix Timestamp

The Unix output counts the seconds from January 1, 1970 UTC to the UTC midnight of the selected date. It represents the date at midnight rather than an arbitrary local clock time. This makes it suitable for scripts, logs, and APIs that expect seconds since the Unix epoch.

Using UTC midnight also keeps the result stable across time zones. The timestamp will not drift to the previous or next day because the user’s local time zone differs from UTC. Copy the generated line directly instead of calculating epoch seconds from a local midnight, which could place the date boundary on the wrong day.

Match the Format to Its Destination

Once the alternatives are visible together, choose the format according to how the destination will use the date:

Destination Recommended output Reason
Filenames, database columns, or spreadsheet cells ISO 8601 It is unambiguous and sorts correctly as plain text.
A system explicitly using MM/DD/YYYY US numeric It follows the required month-first order.
A system explicitly using DD/MM/YYYY European numeric It follows the required day-first order.
Contracts, cheques, or invitations Date to words It writes the day and year fully in an accepted prose convention.
Readable headings or event references Long or full weekday It adds month names and, in the weekday form, the named day.
Scripts, logs, or APIs expecting epoch seconds Unix timestamp It uses UTC midnight and remains stable across time zones.

For cross-border communication, do not rely on an unlabeled numeric value when the recipient may assume the opposite order. ISO is the clearest machine-readable option, while a long or written form is easier for a person to interpret in a document. The right choice depends on whether the destination is primarily a system or a reader.

Final Checks Before Copying

  • Confirm the date: Make sure the date field shows the intended date before copying any output.
  • Check the order: Use US for MM/DD/YYYY and European for DD/MM/YYYY.
  • Match the destination: Use ISO for sorting and structured records, long or words for readable prose, and Unix for epoch-based systems.
  • Keep the scope in view: The converter handles one date at a time and does not add a time of day.
  • Copy one exact line: Use its Copy control instead of typing the value and risking a changed order.

All processing happens in your browser: the selected date never leaves your device, and nothing is uploaded. The converter requires no signup and has no limit on the number of conversions, so you can repeat the same select, compare, and copy workflow for each date you need.

For a deeper look, see Cube Calculator Chart: Read x³ Values and Labels.