Timestamp Converter
Turn Unix timestamps into human dates and dates back into timestamps — seconds, milliseconds or microseconds, in UTC and your local time zone.
Unix time in one minute
A Unix timestamp counts the seconds elapsed since 1 January 1970 00:00:00 UTC (the epoch), ignoring leap seconds. It is time-zone independent, which is why it is the format of choice for logs, JWT claims, database columns and APIs — the same instant always has the same value everywhere. This converter reads a 10-digit timestamp as seconds, a 13-digit one as milliseconds and a 16-digit one as microseconds; pick a unit manually if your value does not fit that pattern.
Date input is equally forgiving: ISO 8601 (2026-10-02T08:00:00Z),
the common 2026-10-02 16:00:00 form, RFC-style strings such as
Oct 2, 2026 — or just pick a moment with the date-time field. Values written
without a time zone are interpreted in your local zone, values with Z or an
offset in UTC, matching how browsers and Node read them.
FAQ
Is the current timestamp exact?
It is your device clock, refreshed every second, and shown in both seconds and milliseconds. BasaltKit has no server, so nothing is fetched over the network.
Why does the same timestamp show 8 hours less in UTC?
Because UTC carries no offset. A timestamp produced at 16:00 in GMT+8 is 08:00 UTC — the same instant written in two zones. Neither is "wrong"; only the local wall-clock reading differs.
How do I get milliseconds instead of seconds?
Multiply the seconds value by 1000, or read the millisecond line this tool prints. JavaScript's Date.now() returns milliseconds, while most APIs (and JWT exp) use seconds.
Does it handle negative or far-future timestamps?
Yes — negative values are dates before 1970 (try -1) and any value JavaScript's Date supports is converted, so years far outside the expected range show up clearly instead of silently rounding.