Skip to content
codevory

Timestamp Converter

Read a date in ISO 8601, RFC 2822 or Unix form and see it in every common format and in other time zones.

Timestamp Converter: the tool

Enter an ISO 8601 date, an RFC 2822 date or a Unix timestamp. A date with no offset is read on the clock of the selected time zone.

How to use Timestamp Converter

  1. Enter a date in one of the supported forms: ISO 8601 (2024-05-02T13:45:00Z or 2024-05-02 13:45), RFC 2822 (Thu, 02 May 2024 13:45:00 +0000) or a Unix timestamp.
  2. If the date has no offset, it is read on the clock of the selected time zone, and the line under the box says so.
  3. The Formats card shows the same moment as ISO 8601, RFC 2822, a readable text, Unix seconds and milliseconds, the day of the year and the ISO week.
  4. The right card lists the same moment on the clocks of other time zones, with their UTC offsets at that date.

Example

A date without an offset, read in UTC, and the same moment in other formats.

Input
2024-05-02 13:45:30
Result
ISO 8601 UTC    2024-05-02T13:45:30.000Z
ISO 8601 Paris  2024-05-02T15:45:30.000+02:00
RFC 2822        Thu, 02 May 2024 13:45:30 +0000
Readable        Thursday, May 2, 2024 at 1:45:30 PM UTC
Unix seconds    1714657530
Day of year     123
ISO week date   2024-W18-4

About this tool

The same moment has many written forms. ISO 8601 and its profile RFC 3339 are used by APIs and JSON. RFC 2822 is the format of email headers and HTTP-style dates. Unix timestamps are used by databases and logs. This tool reads each of them and shows the others, so you can check a value in a log against an API response or an email header.

Only unambiguous formats are accepted. A date such as 03/04/2024 means the 4th of March in the United States and the 3rd of April in most of the world, so it is refused rather than guessed. Impossible dates, such as 30 February or hour 24, are reported with the reason, and an RFC 2822 date whose weekday does not match its date is rejected.

Daylight saving time is applied from your browser's time zone database. When clocks go back, a wall-clock time happens twice and the first occurrence is used. When clocks go forward, a time in the gap does not exist and is moved forward by the length of the gap. Offsets that are not whole hours, such as +05:30 or +05:45, are supported.

Date formats compared

FormatLooks likeUsed in
ISO 8601 / RFC 33392024-05-02T13:45:30ZAPIs, JSON, databases, logs
RFC 2822Thu, 02 May 2024 13:45:30 +0000Email headers, feeds, HTTP-style dates
Unix timestamp1714657530Databases, logs, JWT claims
ISO week date2024-W18-4Planning, payroll, reporting by week

Frequently asked questions

Which formats can I enter?

ISO 8601 and RFC 3339 dates with or without time, seconds, fractions and offset (Z, +02:00, -0500), RFC 2822 dates, and Unix timestamps in seconds, milliseconds, microseconds or nanoseconds. Other spellings are refused because they cannot be read reliably.

Why is 03/04/2024 not accepted?

It is ambiguous: it is 3 April in much of the world and 4 March in the United States. Guessing would silently give a wrong date, so the tool asks for ISO 8601 (2024-04-03) instead.

What happens with a time that does not exist because of daylight saving?

In a spring-forward gap, such as 02:30 in New York on the second Sunday of March, the time is moved forward by the length of the gap. In a fall-back overlap, the first occurrence is used.

Is the time zone data up to date?

It comes from your browser, which ships the IANA time zone database. Recent rule changes appear once your browser is updated.

What is an ISO week date?

A way to write a date as year, week and weekday: 2024-W18-4 is the Thursday of week 18. Weeks start on Monday and week 1 is the one that contains the first Thursday of the year, so the first days of January can belong to the previous year's last week.

More developer tools