About the Unix Timestamp
A Unix timestamp counts the seconds since the Unix epoch, 1970-01-01T00:00:00Z, ignoring leap seconds. It is time-zone independent: the same instant has the same timestamp everywhere, and only its display changes. Many systems use a finer unit — JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds, Python's time.time_ns() and Go's UnixNano() return nanoseconds, and some databases store microseconds.
This converter guesses the unit from the number of digits: up to 11 digits is read as seconds, 12–14 as milliseconds, 15–17 as microseconds and longer values as nanoseconds. A current timestamp has 10 digits in seconds and 13 in milliseconds, so the guess is right for any date between 1973 and 5138. The result is shown in your local time, UTC, ISO 8601, RFC 2822 (the format used in email and HTTP headers) and as a relative time.
For the reverse direction, pick a date, a time and any IANA time zone; the tool resolves daylight-saving rules with the browser's Intl data. You can also paste a free-form string such as 2026-09-29T10:00:00+07:00. Signed 32-bit timestamps overflow at 2147483647 (19 January 2038, 03:14:07 UTC) — the Year 2038 problem listed in the reference table. Everything runs locally in your browser.
How to use it
- Read or copy the live current timestamp in seconds, milliseconds or ISO 8601 at the top.
- Paste a timestamp into “Timestamp → date”; the detected unit is shown next to the heading.
- To go the other way, pick a date, time and time zone, or type any date string.
- Click Copy next to the value you need.