Unix Timestamp Converter

Converts a Unix timestamp (epoch time) into a readable date and time, and a date back into a timestamp. Use it to find out when a number in a log, a database or an API response refers to.

How to use

1. The "Current Unix timestamp (seconds)" at the top updates live; press "Copy seconds" or "Copy milliseconds" to take it.
2. Enter a number under "Timestamp to date" to see the date in the chosen time zone, UTC, ISO 8601, RFC 2822 and the "Relative" time. Leave "Unit" on "Detect from length" in most cases.
3. Under "Date to timestamp", choose the "Date and time" and the "Time zone" to get the value in seconds and milliseconds.
4. Paste many values into "Convert many at once", or compare two moments under "Difference between two timestamps".

How it works

• Detection uses the number of digits in the whole part: up to 11 digits means seconds, up to 14 milliseconds, up to 17 microseconds and anything longer nanoseconds.
• When a local time is skipped or repeated because of daylight saving time, a note says how it was read.
• Only the chosen time zone and unit are remembered in this browser; the numbers you enter are not saved.

Questions and answers

What is a Unix timestamp?

It is the number of seconds since 1970-01-01 00:00:00 UTC. Leap seconds are not counted, so every day has exactly 86,400 seconds.

What is a 13-digit timestamp?

It is in milliseconds. Ten digits means seconds and 13 digits means milliseconds; JavaScript's Date.now() returns milliseconds. Divide by 1000 to get seconds.

Does a Unix timestamp depend on the time zone?

No. The same moment has the same number everywhere; only the local date shown changes. Timestamp 0 is 1970-01-01 00:00 in UTC and 1969-12-31 19:00 in New York.

What is the year 2038 problem?

A signed 32-bit integer can hold at most 2147483647 seconds, which is 2038-01-19 03:14:07 UTC; after that the value overflows. Systems that store the time in 64 bits do not have this problem.