Coffe2CodeSeconds, milliseconds and beyond
| Unit | Digits today | Example | Used by |
|---|---|---|---|
| Seconds | 10 | 1762128000 | Unix, PHP time(), Python time.time(), JWTs, most databases |
| Milliseconds | 13 | 1762128000000 | JavaScript Date.now(), Java System.currentTimeMillis() |
| Microseconds | 16 | 1762128000000000 | PostgreSQL internals, Python datetime precision |
| Nanoseconds | 19 | 1762128000000000000 | Go time.UnixNano() |
1762128000 is 3 November 2025, 00:00:00 UTC. More detail in Unix time explained.
Get the current timestamp
Math.floor(Date.now() / 1000) // JavaScript, seconds
int(time.time()) # Python
date +%s # Shell
SELECT EXTRACT(EPOCH FROM now()); -- PostgreSQL
new Date(1762128000 * 1000).toISOString() // '2025-11-03T00:00:00.000Z'Frequently asked questions
Is my timestamp in seconds or milliseconds?
Count the digits. A current Unix time in seconds has 10 digits (for example 1762128000), and in milliseconds it has 13 (1762128000000). JavaScript’s Date.now() returns milliseconds; most databases, Unix tools and JWTs use seconds. This converter detects which one you pasted.
Does a Unix timestamp have a time zone?
No. A Unix timestamp counts seconds since 00:00:00 UTC on 1 January 1970, so the same number means the same instant everywhere. Time zones only matter when you display it as a date.
What is the year 2038 problem?
Systems that store Unix time as a signed 32-bit integer can only count up to 2,147,483,647 seconds, which is reached at 03:14:07 UTC on 19 January 2038. After that the value overflows. Modern systems use 64-bit integers, which last for billions of years.