How precision is detected
The tool counts digits: up to 11 digits is read as seconds, 12-14 as milliseconds (JavaScript Date.now(), Java), 15-17 as microseconds (Python time.time_ns()//1000, PostgreSQL) and anything longer as nanoseconds (Go UnixNano). Negative values are dates before 1970.
Good to know
- Unix time ignores leap seconds, so every day is exactly 86,400 seconds.
- Signed 32-bit timestamps overflow at
2147483647, which is 2038-01-19 03:14:07 UTC (the "Year 2038 problem"). - Date strings without a time zone, like
2026-10-12 09:00, are read as your local time. AddZor an offset such as+03:00to be explicit.
FAQ
What time zone is a Unix timestamp in?
None. It counts seconds since 1970-01-01 00:00:00 UTC, so the same number is the same instant everywhere. Only the display changes per time zone.
Does this use my clock?
Yes. "Now" and relative times use your device clock.