Date Format Converter

Formula

How this is calculated

The single input accepts a date written in any of several common ways. The parser first checks for an unambiguous YYYY-MM-DD pattern, then for an MM/DD/YYYY slash pattern (US convention), and finally falls back to the browser's native Date parser for everything else such as "June 27, 2026". The resulting calendar date is read as year, month and day in your local time zone.

Each output is then rebuilt from those components. ISO 8601 zero-pads month and day to two digits; the US and European variants only differ in field order; long form and the weekday name are produced with your locale so month names appear in your language. The ordinal adds the English suffix (st, nd, rd, th). RFC 2822 assembles the abbreviated weekday and month with a numeric UTC offset, and the Unix epoch is the whole number of seconds elapsed since 1970-01-01 00:00:00 UTC.

Date-only inputs are treated as midnight local time, so the Unix timestamp reflects that local midnight rather than UTC midnight. If the text cannot be understood as a date, no formats are shown. Slash dates are always read in US month-first order, so write 2026-06-27 when you need unambiguous results.