Unix Timestamp

A Unix timestamp (epoch time) is the number of seconds — or in some APIs, milliseconds — elapsed since 00:00:00 UTC on January 1, 1970, not counting leap seconds.

Updated: 2026-08-11

Lookup

Unix Timestamp
Definition
Epoch origin1970-01-01T00:00:00Z.
Seconds precisionWhole seconds since the epoch — used by Unix time(), most POSIX APIs, and many JWT claims (exp, iat, nbf).
Milliseconds precisionUsed by JavaScript's Date.now(), Java's System.currentTimeMillis(), and many JSON web APIs. See the seconds vs milliseconds guide.
Year 2038 problemA signed 32-bit seconds counter overflows at 2038-01-19T03:14:07Z.
Negative timestampsValid — they represent instants before 1970-01-01.

Examples

Epoch zero

text
0 -> 1970-01-01T00:00:00Z

A recent timestamp

text
1700000000 -> 2023-11-14T22:13:20Z

Common Mistakes

!
Passing seconds where milliseconds are expected
new Date(1700000000) in JavaScript treats the value as milliseconds and produces 1970-01-20, not the intended 2023 date.
!
Ignoring timezone at display time
The timestamp itself is a timezone-agnostic UTC instant; timezone only enters when formatting it for display.
!
Assuming strict monotonic increase
System clock adjustments (NTP sync, manual changes) can move wall-clock time backward; don't rely on timestamps alone for ordering guarantees.

Related Concepts

Unix Timestamp

Related Tools

Related Guides