Unix Timestamp Converter

This Unix timestamp converter turns epoch seconds or milliseconds into readable dates and times, and dates back into timestamps. A Unix timestamp counts the seconds since 00:00:00 UTC on January 1, 1970 (the Unix epoch), and you will find them in databases, APIs, server logs and the exp and iat fields that a JWT decoder shows. Results appear in UTC, your browser's local time or one of 13 named time zones.

How to use the Unix timestamp converter

1. For Unix timestamp to date conversion, paste the number into the Unix Timestamp box. The result appears as you type, or press Convert to Date. Now, Start of Day and Start of Year fill the box for you; the last two use midnight UTC.
2. Leave Unit on Auto-detect, or force Seconds or Milliseconds.
3. Choose UTC, Local (Browser) or a named zone such as Asia/Kolkata from the Timezone menu. The result updates when you switch.
4. Read the rows: ISO 8601, a full date, a short date, the time alone, a line labelled RFC 2822 and a relative time such as "2 years ago". Each has a Copy button.
5. To go the other way, set the Date and Time (to the second) under Date to Timestamp, pick its time zone and press Convert to Timestamp. You get both seconds and milliseconds.
6. The live clock at the top shows the current timestamp, with Copy Seconds and Copy Milliseconds buttons.

Example: 1700000000 in three time zones

The timestamp 1700000000 is one moment everywhere. Here is how the converter shows it in three zones:

Typing 1700000000000 gives the same rows, because Auto-detect reads 13 or more digits as milliseconds. In the other direction, January 1, 2026 at 00:00:00 UTC converts to 1767225600 seconds and 1767225600000 milliseconds.

Seconds or milliseconds

Like any epoch converter, this Unix timestamp converter has to guess the unit when you don't set it. Ten-digit values are seconds and cover every date from September 9, 2001 to November 20, 2286. Thirteen-digit values are milliseconds, which is what JavaScript's Date.now() and Java's System.currentTimeMillis() return.

A wrong unit is easy to spot. A seconds value read as milliseconds lands in January 1970: 1700000000 as milliseconds is 1970-01-20T16:13:20Z. A milliseconds value read as seconds lands in the year 55840. If you see either, set Unit by hand. Decimals also work: 1700000000.5 is read as seconds and keeps the half second.

Unix time in Excel, SQL, Python and Discord

The same conversion in other tools, all giving UTC unless noted:

• Excel and Google Sheets: =A2/86400+DATE(1970,1,1), then format the cell as a date and time. Divide by 86400000 instead for milliseconds.
• MySQL: FROM_UNIXTIME(1700000000) returns the date in the session time zone.
• PostgreSQL: to_timestamp(1700000000) returns a timestamp with time zone, and EXTRACT(EPOCH FROM now()) gives the current value.
• Python: datetime.fromtimestamp(1700000000, tz=timezone.utc) gives 2023-11-14 22:13:20+00:00.
• Discord: a message containing <t:1700000000:F> shows the full date in each reader's own time zone, and <t:1700000000:R> shows it as relative time.

So this page works as a Unix time converter for checking any of those results by hand.

Things to know about the output

• For a named zone, the ISO 8601 row shows that zone's clock time without an offset. With Local (Browser), the ISO row keeps the UTC clock time and adds your offset, so it is off by that offset; read the full or short row for local time, or use UTC for a correct ISO string.
• The RFC 2822 row is a readable date with a zone name. It is not the strict layout email headers use, which looks like Tue, 14 Nov 2023 22:13:20 +0000.
• Relative time counts a month as 30.44 days and a year as 365.25 days, so treat it as a rough guide.

For scheduled jobs, the cron generator builds the expression and the guide to running cron every 5 minutes explains its fields. More converters are in the developer tools.