Using the converter
Paste a timestamp and the date appears, one per line if you paste several. The converter works out whether it's in seconds, milliseconds, microseconds or nanoseconds from how many digits it has, since that's the usual reason a converted date comes out wrong. Time zone shows the date in UTC, your own zone or another city's.
Swap to go from a date to a timestamp. Dates like 2026-10-01 12:00 are read in the chosen time zone; a date with its own zone, like 2026-10-01T12:00:00Z, uses that. Type now for the current timestamp.
What Unix time counts
Unix time is the number of seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. JSON Web Tokens use exactly the same count for their dates. The moment is called the epoch, which is why converters are often called epoch converters.
Some systems count in milliseconds instead, which gives a 13-digit number for dates in this century rather than 10. Microseconds give 16 digits and nanoseconds 19.
The year 2038
A signed 32-bit integer can hold numbers up to 2,147,483,647. As a Unix time, that's 03:14:07 UTC on 19 January 2038. One second later, a system that stores time in 32 bits wraps round to a negative number, a date in December 1901. The steps point it out when a timestamp is past that limit.
Questions
Why is my date in 1970?
The timestamp was probably read in the wrong unit. A millisecond timestamp read as seconds lands tens of thousands of years in the future, and the other way round lands near 1970. This converter guesses the unit from the number of digits to avoid that.
Does Unix time include leap seconds?
No. Every day counts as exactly 86,400 seconds, so a leap second doesn't get a number of its own.
Can a Unix timestamp be negative?
Yes. Negative numbers are dates before 1970: -86400 is the last day of 1969.