Advertisement

Free Online Date Format Converter

Convert dates between ISO, US, European, and custom formats.

Accepts ISO dates, MM/DD/YYYY, DD/MM/YYYY, date-times, 10-digit Unix seconds, or 13-digit Unix milliseconds.
Tokens: YYYY YY MMMM MMM MM M DD D dddd ddd HH H hh h mm m ss s A a Z X x. Wrap literal words in square brackets, for example [on] dddd.
Parsed input will appear here.

Converted formats

ISO 8601 (local time) —
UTC —
US format —
European format —
Written long date —
Unix seconds —
Unix milliseconds —
RFC 2822 —
Custom pattern —

ISO and UTC values are unambiguous and safe for databases and APIs. US and European numeric formats are shown for convenience; when sharing a date with someone in another region, prefer ISO 8601. Unix timestamps are always based on UTC and do not depend on the browser timezone.

Advertisement

About the Date Format Converter

A single moment in time can be written in dozens of valid ways. Databases prefer ISO 8601, APIs often exchange Unix timestamps, invoices use local numeric formats, and human readers respond best to a written long date. Copying a date from one system to another without changing its representation is a common source of errors, especially when the day and month are both small numbers. This converter parses a date, date-time, or timestamp and displays the same instant in several standard formats at once, with a copy button beside each value.

Accepted inputs

The input field accepts an ISO date such as 2026-11-07, an ISO date-time such as 2026-11-07T14:30:00, a space-separated date-time, US-style 11/07/2026, European-style 07/11/2026, a ten-digit Unix timestamp in seconds, or a thirteen-digit Unix timestamp in milliseconds. A trailing Z or numeric offset is recognised for ISO date-times. When a numeric date is ambiguous, the tool follows the US convention of month first and adds a note in the parsed summary so you can switch to an ISO input if you meant the other order.

Standard outputs

ISO 8601 is shown with the local timezone offset, which keeps the value unambiguous while matching the clock on your device. UTC is the same instant expressed in Coordinated Universal Time. The US and European rows show month-first and day-first numeric formats with the time appended. The long written form spells out the weekday, month, day, year, and time. Unix seconds and milliseconds are integers since 1 January 1970 UTC, and the RFC 2822 row provides the format used by email headers.

Custom patterns

The custom pattern field supports common date tokens. YYYY and YY produce the year, MMMM, MMM, MM, and M produce the month in different widths, and DD, D, dddd, and ddd produce the day and weekday. HH, H, hh, and h give twenty-four or twelve-hour clocks, while mm, ss, A, and a add minutes, seconds, and the AM/PM marker. Z adds the numeric timezone offset, and X or x add Unix seconds or milliseconds. Literal text should be wrapped in square brackets, so a pattern like dddd [at] h:mm A prints the weekday followed by the word "at" and the time.

Frequently asked questions

Does the converter change the moment in time?

No. Every output describes the same instant. Only the representation and, for local formats, the timezone offset change.

Why is the UTC value different from my local time?

UTC is a fixed reference timezone. Your local clock may be ahead of or behind it depending on where you are and whether daylight saving is active.

Can I copy all formats at once?

Each row has its own copy button. Copy the specific format you need so the value matches the destination system.

Sponsored
Find a bug? Report now