UnitPlanet

Unix Timestamp Converter

A Unix timestamp is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC — a moment known as the Unix epoch. It is the most widely used machine-readable representation of time in programming, databases, APIs, and log files. The converter above accepts a timestamp and shows the equivalent UTC and local-timezone datetime, or converts a human-readable datetime back to a timestamp.

The formula

unix_timestamp = (UTC datetime − 1970-01-01T00:00:00Z) in whole seconds

human datetime = 1970-01-01T00:00:00Z + timestamp seconds

Millisecond timestamps (used by JavaScript's Date.now()) are 1,000× larger than second timestamps. Divide by 1,000 before entering here.

Practical examples

Example 1 — Epoch origin

Timestamp: 01970-01-01 00:00:00 UTC

Negative timestamps represent dates before 1970, e.g. −86400 = 1969-12-31 00:00:00 UTC.

Example 2 — Recent date

Timestamp: 1748390400May 28, 2026, 00:00:00 UTC

Example 3 — Millisecond timestamp from JavaScript

Date.now() returns 1748390400000 (milliseconds). Divide by 1000: 1748390400 → use in this converter.

Common mistakes

Confusing seconds and milliseconds. Many modern APIs (JavaScript, Android, Python's time.time_ns()) return milliseconds or nanoseconds. A 13-digit timestamp is milliseconds; a 10-digit timestamp is seconds. If the converted date shows 1973 instead of 2024, you likely need to divide by 1000.

Assuming timestamps include timezone information. Unix timestamps are always UTC by definition. Converting to local time is a display operation performed by the viewer's system — the underlying number is timezone-agnostic.

The 2038 problem. Signed 32-bit integers overflow at 2,147,483,647 — January 19, 2038, 03:14:07 UTC. Systems using 32-bit timestamps may malfunction at this point. 64-bit systems (standard on modern hardware) extend the range by billions of years.

International and regional variations

Platform / languageUnitExample (now)
Unix / POSIX / CSeconds1748390400
JavaScript / JavaMilliseconds1748390400000
Python time.time()Float seconds1748390400.123
Go time.Now().UnixNano()Nanoseconds1748390400000000000
PostgreSQL EXTRACT(EPOCH)Float seconds1748390400.0

Quick reference — notable Unix timestamps

TimestampUTC dateSignificance
01970-01-01Unix epoch origin
1,000,000,0002001-09-09First billion-second milestone
1,234,567,8902009-02-13Popular cultural milestone
2,000,000,0002033-05-18Second billion-second milestone
2,147,483,6472038-01-1932-bit integer overflow (Year 2038 problem)
UTC
Local time

Frequently Asked Questions

What is a Unix timestamp?
A Unix timestamp is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC (called the Unix epoch). It is used in virtually all programming languages and databases to represent a moment in time.
What does timestamp 0 represent?
Timestamp 0 is 1970-01-01 00:00:00 UTC — the Unix epoch origin. Negative timestamps represent dates before 1970.
How do I convert a Unix timestamp in milliseconds?
Divide by 1000 to get seconds, then use this converter. Many JavaScript APIs return milliseconds (e.g. Date.now()), while Unix timestamps are conventionally in seconds.
What is the maximum Unix timestamp?
On 32-bit systems the maximum is 2,147,483,647, which corresponds to January 19, 2038 — the so-called 'Year 2038 problem'. 64-bit systems extend this billions of years into the future.
How does this differ from an ISO 8601 date string?
An ISO 8601 string (e.g. 2024-11-15T12:00:00Z) is human-readable but longer. A Unix timestamp is a compact integer used in databases, APIs, and log files where storage and sorting efficiency matter.

Related Tools