DN

Unix Timestamp Converter

Convert Unix timestamps to dates and dates to timestamps.

About the Timestamp Converter

Convert Unix (epoch) timestamps to readable dates and back. Paste a timestamp in seconds, milliseconds or microseconds — the unit is detected automatically — and see it in UTC, your local time zone, ISO 8601 and relative time.

The current Unix time is shown live at the top, and every value has a one-click copy button. All conversions use your browser's clock and time zone settings.

How to use the Timestamp Converter

  1. 1

    See the current time

    The live panel shows the current Unix timestamp in seconds and milliseconds.

  2. 2

    Convert a timestamp

    Paste a timestamp under Timestamp → Date; the unit is detected from its length, or choose it yourself.

  3. 3

    Convert a date

    Pick a date and time under Date → Timestamp and choose whether it's in local time or UTC.

  4. 4

    Copy what you need

    Copy any format — Unix seconds, milliseconds, ISO 8601, UTC or local — with one click.

Frequently asked questions

What is a Unix timestamp?

A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have passed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is a simple, time-zone-independent way for computers to store a moment in time.

How do I know if a timestamp is in seconds or milliseconds?

Look at the number of digits. Current timestamps in seconds have 10 digits, in milliseconds 13 digits and in microseconds 16 digits. The converter detects this automatically, and you can override it.

Does a Unix timestamp depend on the time zone?

No. A Unix timestamp always refers to the same instant everywhere in the world. Only the way it is displayed as a date and time depends on the time zone, which is why the converter shows both UTC and your local time.

What is ISO 8601?

ISO 8601 is an international standard format for dates and times, such as 2026-09-26T14:30:00.000Z. The trailing Z means the time is in UTC. It is widely used in APIs and JSON because it sorts correctly and is unambiguous.

What is the year 2038 problem?

Systems that store Unix time as a signed 32-bit integer can only count up to 2,147,483,647 seconds, which is reached on 19 January 2038. After that the value overflows. Modern systems use 64-bit timestamps, which avoid the problem.