Unix timestamp converter
Developer tools
Paste a timestamp or pick a date. Seconds, milliseconds, microseconds and nanoseconds are all recognised.
Runs in your browser
Nothing is uploaded. The work happens on your own device, so your file or text never reaches us.
About this tool
Seconds or milliseconds?
A timestamp is just a number and carries no unit, so it has to be guessed from magnitude.
10 digits is seconds, for any date between 2001 and 2286. 13 digits is milliseconds. 16 is microseconds and 19 is nanoseconds.
Unix itself and most of the shell world use seconds; JavaScript, Java and most JSON APIs use milliseconds. Interpreting one as the other puts you in 1970 or in the year 50,000, which at least makes the error obvious. The tool says which unit it read.
The 2038 problem
A signed 32-bit integer overflows at 2,147,483,647, which is 03:14:07 UTC on 19 January 2038. Systems still storing time that way will wrap to 1901.
It is not hypothetical: it is already reachable by any system handling a 15-year date — a mortgage, a bond, a passport expiry. The tool flags a timestamp past that point.
Leap seconds
Unix time deliberately ignores them. It assumes every day has exactly 86,400 seconds, so a leap second is absorbed by repeating a value rather than adding one.
That makes Unix time not quite a true count of elapsed seconds since 1970, which matters in precision timing and nowhere else. Leap seconds are being discontinued by 2035 in any case.