Unix Timestamp Converter
Live current Unix timestamp, timestamp-to-date and date-to-timestamp conversion — seconds, milliseconds, micro- and nanoseconds.
A Unix timestamp is the number of seconds since January 1, 1970, 00:00 UTC. 10 digits = seconds, 13 digits = milliseconds. Paste a value below — the tool auto-detects the unit.
Timestamp → date
Date → timestamp
Formats by digit count
| Unit | Digits (today) | Example | Used by |
|---|---|---|---|
| Seconds | 10 | 1755000000 | Unix `date +%s`, PHP time(), Python time.time() |
| Milliseconds | 13 | 1755000000000 | JavaScript Date.now(), Java System.currentTimeMillis() |
| Microseconds | 16 | 1755000000000000 | PostgreSQL, Python datetime |
| Nanoseconds | 19 | 1755000000000000000 | Go time.UnixNano(), Rust |
Notable timestamps
| Timestamp | UTC | Note |
|---|---|---|
| 0 | 1970-01-01 00:00:00 | The Unix epoch |
| 1000000000 | 2001-09-09 01:46:40 | 1 billion seconds |
| 1234567890 | 2009-02-13 23:31:30 | A favourite round moment |
| 1500000000 | 2017-07-14 02:40:00 | 1.5 billion seconds |
| 2000000000 | 2033-05-18 03:33:20 | 2 billion seconds |
| 2147483647 | 2038-01-19 03:14:07 | The Y2038 problem (32-bit limit) |
Frequently asked questions
What is a Unix timestamp?
A Unix timestamp (epoch time) is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC — the "Unix epoch". It is the standard machine representation of a moment in time: one integer, independent of time zones and calendar formats.
Seconds or milliseconds — how do I tell them apart?
By digit count: a timestamp in seconds currently has 10 digits (e.g. 1755000000), in milliseconds 13 (JavaScript Date.now()), in microseconds 16, and in nanoseconds 19. The tool auto-detects the unit.
Does Unix time depend on the time zone?
No. The timestamp is identical worldwide — it counts seconds in UTC. Time zones only matter when you render the number as a human-readable date: the same timestamp shows as different local times in Sofia and New York.
What is the Y2038 problem?
On January 19, 2038 at 03:14:07 UTC, 32-bit signed integers reach their maximum (2147483647). Systems still storing Unix time in 32 bits will overflow — like Y2K, but for Unix time. Modern 64-bit systems are unaffected.
Can a timestamp be negative?
Yes — negative values represent moments before January 1, 1970. For example, -86400 is December 31, 1969, 00:00 UTC. Most systems support them, though some APIs reject negative values.
Does Unix time count leap seconds?
No. Unix time assumes every day has exactly 86,400 seconds — leap seconds are "absorbed". That makes it convenient for arithmetic but not a precise physical timescale (TAI serves that purpose).