Omvandla Unix-tidsstämplar till läsbara datum och datum till tidsstämplar, i sekunder eller millisekunder, i UTC och din tidszon.
| Timestamp | Date (UTC) |
|---|---|
0 | January 1, 1970, 00:00:00 (the Unix epoch) |
1000000000 | September 9, 2001, 01:46:40 |
1700000000 | November 14, 2023, 22:13:20 |
2000000000 | May 18, 2033, 03:33:20 |
2147483647 | January 19, 2038, 03:14:07 (32-bit limit) |
Decoding a JWT's exp claim? The JWT decoder converts its timestamps automatically.
It's the number of seconds since 00:00:00 UTC on January 1, 1970 (the Unix epoch), not counting leap seconds. It's the same everywhere in the world, which makes it a convenient way for computers to store moments in time.
Unix systems, databases and most APIs use seconds (10 digits today). JavaScript, Java and many web APIs use milliseconds (13 digits). The converter detects which one you entered from its length.
Systems that store timestamps as signed 32-bit integers can only count to 2,147,483,647, which is reached on January 19, 2038 at 03:14:07 UTC. After that they overflow. Modern systems use 64-bit timestamps, which last for billions of years.
JavaScript: Math.floor(Date.now() / 1000). Python: int(time.time()). C#: DateTimeOffset.UtcNow.ToUnixTimeSeconds(). Bash: date +%s. SQL (PostgreSQL): extract(epoch from now()).
