Figuro.net

Unix Timestamp Converter

Convert epoch time to a human-readable date and back, in any time zone. The tool detects seconds, milliseconds, microseconds and nanoseconds automatically and shows the current Unix time live.

Current Unix time

Seconds
…
Milliseconds
…

Timestamp → date

Enter a timestamp.

Date → timestamp

Pick a date.

What is a Unix timestamp?

A Unix timestamp, also called epoch time, counts the time elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. Because it is a single number that is the same everywhere on Earth, it is widely used in databases, log files, APIs, JWT tokens and file systems. A timestamp has no time zone of its own: the zone only matters when you display it as a calendar date.

Seconds, milliseconds and beyond

Digits (today)UnitTypical source
10SecondsUnix tools, PHP time(), Python time.time()
13MillisecondsJavaScript Date.now(), Java
16MicrosecondsDatabases and tracing tools
19NanosecondsGo, high-resolution logging

Working with time zones

Pick a time zone above and the converter shows the local date and offset for that zone, including daylight saving time rules from your browser's time zone database. When you convert a date back to a timestamp, the date you enter is interpreted in the selected zone, which avoids the classic mistake of treating a local time as if it were UTC.

One practical note: signed 32-bit timestamps run out on 19 January 2038, while the 64-bit values used by modern systems last for hundreds of billions of years.

Frequently asked questions

How do I know if a timestamp is in seconds or milliseconds? Count the digits. Current timestamps have 10 digits in seconds and 13 digits in milliseconds. The Auto-detect option applies this rule for you.

Does a Unix timestamp depend on the time zone? No. It always counts from the epoch in UTC. The time zone only affects how the moment is written as a calendar date and clock time.

What is the Year 2038 problem? Systems that store the timestamp in a signed 32-bit integer overflow on 19 January 2038. Systems using 64-bit integers are not affected.

Are leap seconds included in Unix time? No. Unix time ignores leap seconds, so each day is treated as exactly 86,400 seconds.

Can I enter negative timestamps? Yes. Negative values represent moments before 1 January 1970.

← Browse all calculators