Current Unix Timestamp
—
Milliseconds: —
Timestamp → Human-readable Date
Local time
—
UTC
—
ISO 8601
—
Relative
—
Date → Timestamp
Seconds (Unix)
—
Milliseconds (JS)
—
What This Tool Does
Converts Unix timestamps (in seconds or milliseconds) to local time, UTC, ISO 8601, and relative time. Also converts any date/time back to a Unix timestamp. The current timestamp is displayed live, ticking every second. Auto-detects whether your input is seconds or milliseconds.
Frequently Asked Questions
What is a Unix timestamp?
A Unix timestamp (also called Unix time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970 (the Unix epoch). It is a simple, timezone-independent way to represent a moment in time, widely used in programming, databases, and APIs.
Does Unix timestamp account for timezones?
Unix timestamps are always in UTC — they represent an absolute moment in time with no timezone information. When displaying a timestamp as a human-readable date, the timezone is applied at that point. This is why the same timestamp looks like different clock times in different parts of the world.
What is the "Year 2038 problem"?
Traditional 32-bit systems store Unix timestamps as a signed 32-bit integer, which overflows on 19 January 2038 at 03:14:07 UTC. Modern 64-bit systems use 64-bit integers and won't face this problem for billions of years.
Is milliseconds vs seconds important?
JavaScript uses milliseconds (1000× larger) internally, while most Unix tools and APIs use seconds. This tool handles both — paste either format and it detects which you mean based on the number of digits.