Unix Timestamp Converter (Epoch ↔ Date)

Paste an epoch time to see it as a date in any time zone, or pick a date to get its Unix timestamp. Seconds, milliseconds, microseconds and nanoseconds are detected automatically.

Runs in your browserNo sign-upNothing uploaded

0seconds
0milliseconds

Timestamp → Date

Date → Timestamp

How to use the Unix Timestamp Converter

  1. The current Unix time ticks at the top; copy it in seconds or milliseconds.
  2. Paste a timestamp (or an ISO date such as 2026-10-12T10:00:00Z) into Timestamp → Date. The unit is detected from the number of digits.
  3. Choose a time zone to see the same instant as local wall-clock time, plus UTC, ISO 8601, RFC 2822, relative time and week number.
  4. To go the other way, pick a date and time in Date → Timestamp. It is read as wall-clock time in the selected zone, daylight saving included.
  5. Use the Copy buttons next to each value.

What is a Unix timestamp?

A Unix timestamp (epoch time, POSIX time) is the number of seconds elapsed since 1970-01-01 00:00:00 UTC, not counting leap seconds. It describes one instant regardless of time zone, which is why databases, logs, JWT exp claims and APIs use it. Time zones only matter when you turn that instant into a calendar date and clock time for a person.

Seconds, milliseconds, microseconds or nanoseconds?

Different platforms count in different units, and mixing them up is a classic bug (dates in 1970 or in the year 55,000). The converter looks at the number of digits:

Digits (today)UnitTypical source
10secondsUnix date +%s, PHP time(), JWT claims, Python int(time.time())
13millisecondsJavaScript Date.now(), Java System.currentTimeMillis()
16microsecondsPostgreSQL internals, some tracing systems
19nanosecondsGo time.UnixNano(), Python time.time_ns()

Getting the current timestamp in code

// JavaScript
Math.floor(Date.now() / 1000)
# Python
import time; int(time.time())
# Bash
date +%s
-- PostgreSQL
SELECT extract(epoch FROM now());

Time zones and daylight saving

When you convert a date to a timestamp, the wall-clock time is interpreted in the selected IANA zone (for example Europe/Istanbul or America/New_York) using your browser's time zone database. During a spring-forward jump some local times do not exist; during a fall-back the same local time occurs twice and the earlier instant is used. The tool tells you when this happens.

The year 2038 problem

Systems that store seconds in a signed 32-bit integer overflow at 2147483647, which is 2038-01-19 03:14:07 UTC. Modern platforms use 64-bit values, but older embedded systems and database columns may still be affected.

Frequently asked questions

How do I know if my timestamp is in seconds or milliseconds?
Count the digits. Current dates are 10 digits in seconds and 13 digits in milliseconds. The converter detects this automatically and tells you which unit it used.
Is a Unix timestamp always UTC?
Yes. The timestamp itself has no time zone; it counts seconds since midnight UTC on 1 January 1970. A time zone is applied only when you display it as a local date.
Can I convert negative timestamps?
Yes. Negative values are instants before 1970, e.g. -86400 is 1969-12-31 00:00:00 UTC.
Does Unix time include leap seconds?
No. Every Unix day is exactly 86,400 seconds, so leap seconds are not counted. This keeps date arithmetic simple.
Can I paste an ISO 8601 date instead of a number?
Yes. Strings such as 2026-10-12T10:00:00Z or 2026-10-12T10:00:00+03:00 are parsed and shown in every format, including their Unix timestamp.

Related tools