Unix Timestamp

Convert between Unix timestamps and human-readable dates instantly. A developer-friendly Epoch time converter for programming, debugging, and data analysis. Free online tool.

Current Unix Timestamp: ...
Conversion Direction

Enter a Unix timestamp in seconds

How to Use

  1. Choose the conversion direction

    Select whether to convert a timestamp to a date, or a date to a timestamp.

  2. Enter the value

    Input a Unix timestamp number or select a date and time.

  3. View the result

    Click Convert to see the result displayed in multiple formats.

What is a Unix timestamp?

A Unix timestamp (Unix time, POSIX time, Epoch time) represents the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC (the Unix Epoch) as a single integer. Because it points to the same instant everywhere on Earth regardless of time zone, daylight saving, or calendar notation, it has become the de facto standard for database storage, logging, API communication, and time comparison.

Why express time as a number?

  • Simple comparison — deciding which of two moments came first is just an integer comparison.
  • Easy arithmetic — adding or subtracting immediately yields the elapsed time in seconds.
  • No ambiguity — as an absolute UTC time, there is no confusion over whether a value is local time or UTC.

10-digit (seconds) and 13-digit (milliseconds) forms are common; JavaScript and Java work in milliseconds by default, while Unix system calls use seconds.

Conversion Formula

Timestamps and dates convert in both directions using 1000 (the millisecond factor) as the bridge.

  • Timestamp → date: date = new Date(timestamp x 1000)
  • Date → timestamp: timestamp = floor(UTC milliseconds / 1000)

Example: converting 1711324800 seconds gives 1711324800 x 1000 = 1,711,324,800,000 milliseconds → 2024-03-25 00:00:00 UTC. Conversely, 1970-01-01 01:00 converts to a timestamp of 3600, since 1 hour = 3600 seconds. Here timestamp is the seconds elapsed since the Epoch, x1000 is the millisecond conversion factor, and floor truncates the fractional part.

Frequently Asked Questions

What is a Unix timestamp?
A Unix timestamp (Unix time, POSIX time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. It is the most fundamental way computer systems represent dates and times, expressing the same instant as a single number regardless of time zone. For example, timestamp 0 is midnight (UTC) on January 1, 1970.
What is the Epoch?
The Epoch is the reference point for measuring time. On Unix/POSIX systems the Epoch is January 1, 1970, 00:00:00 UTC, also called the 'Unix Epoch'. Every Unix timestamp counts the seconds elapsed since this moment, and negative timestamps represent times before 1970.
What is the Y2K38 (Year 2038) problem?
Y2K38 is an overflow problem that arises when timestamps are stored in a 32-bit signed integer. The 32-bit maximum value 2,147,483,647 corresponds to January 19, 2038, 03:14:07 UTC; immediately after, the value wraps to negative and the time is wrongly shown as 1901. Most modern systems solved this by using 64-bit integers.
How do second and millisecond timestamps differ?
Second-precision timestamps usually have 10 digits (e.g. 1711324800), while millisecond timestamps have 13 digits (e.g. 1711324800000). The relationship is 'milliseconds = seconds x 1000'. JavaScript's Date.now() and Java return milliseconds, whereas the Unix date command and PHP time() return seconds. This converter shows the result in both seconds and milliseconds.
Why are UTC time and local time shown differently?
The timestamp itself is an absolute UTC time, but people find their own local time more convenient to read. So the same timestamp is shown two ways: in UTC and in your browser's local time zone. For example, Korea (KST) is UTC+9, so for the same timestamp the local time appears 9 hours ahead of UTC.
How do I get the current Unix timestamp?
When you open this page, the current Unix timestamp is shown live, and the 'Use current timestamp' button fills it straight into the input field. On the command line you can also get the current second-precision timestamp with 'date +%s' (Unix/Mac).
What is the ISO 8601 format and why show it alongside?
ISO 8601 is an international standard for writing dates and times, such as '2024-03-25T00:00:00.000Z', where the trailing Z means UTC. Timestamps are hard for people to read while UTC strings are highly portable across systems, so they are often used together in APIs, logs, and JSON; that is why we include it with the conversion result.
Can a timestamp be zero or negative?
Yes. Timestamp 0 is the Epoch reference point, January 1, 1970, 00:00:00 UTC, and earlier moments (e.g. 1969) are expressed as negative numbers. For reference, Y2K (2000-01-01) is 946684800 and the Y2K38 limit is 2147483647, so specific moments have fixed integer values.
2026 calendar data

Related Calculators