Unix timestamp converter
Paste an epoch time to read it as a date, or pick a date to get its timestamp. Seconds, milliseconds and microseconds are detected automatically.
Runs entirely in your browser. Nothing you enter is sent to a server.
What is a Unix timestamp?
A Unix timestamp counts the seconds since 00:00:00 UTC on 1 January 1970 (the “epoch”), ignoring leap seconds. It’s the same everywhere on Earth at a given instant, which is why databases, APIs and log files use it.
Seconds or milliseconds?
- 10 digits (e.g. 1767225600) — seconds. Used by Unix, PHP, Python’s
time.time()and most APIs. - 13 digits — milliseconds. Used by JavaScript’s
Date.now()and Java. - 16 digits — microseconds, common in databases and tracing tools.
Get the current timestamp in code
| JavaScript | Math.floor(Date.now() / 1000) |
| Python | int(time.time()) |
| PHP | time() |
| Go | time.Now().Unix() |
| Java | Instant.now().getEpochSecond() |
| Bash | date +%s |
| SQL (PostgreSQL) | extract(epoch from now()) |
The year 2038 problem
Systems that store timestamps as signed 32-bit integers overflow at 03:14:07 UTC on 19 January 2038 (2147483647). Modern systems use 64-bit values, which last for billions of years.
Inspecting an API response? Pretty-print it with the JSON formatter, or read a token’s exp claim with the JWT decoder.
Frequently asked questions
What timestamp is 0?
0 is 1 January 1970, 00:00:00 UTC — the Unix epoch.
Do Unix timestamps depend on time zone?
No. A timestamp is the same worldwide; only its display as a local date changes.
Can timestamps be negative?
Yes. Negative values are dates before 1970; −86400 is 31 December 1969.
Does Unix time include leap seconds?
No. Every Unix day is treated as exactly 86,400 seconds.