Developer tools
Unix Timestamp Converter — Convert Seconds, Milliseconds & Dates
A Unix timestamp (also called epoch time or POSIX time) counts the seconds that have passed since 00:00:00 UTC on 1 January 1970. Because it is one number with no time zone attached, developers, database administrators, DevOps and security engineers, and data analysts use it to store times, compare events and read logs. Paste a timestamp below to see the date, or pick a date to get its timestamp. Everything runs in your browser and nothing is sent anywhere.
Current Unix time
Updates every second- Seconds
- —
- Milliseconds
- —
Timestamp to date
Enter a Unix timestamp in seconds or milliseconds. Negative values are dates before 1970.
The suggested unit appears here as you type.
- Local time
- —
- UTC
- —
- ISO 8601
- —
- Unix seconds
- —
- Unix milliseconds
- —
Date to timestamp
Pick a date and time, then choose whether it is in your local time zone or UTC. Nothing is guessed.
- Unix seconds
- —
- Unix milliseconds
- —
- ISO 8601 (UTC)
- —
How to use this converter
- To read a timestamp, paste it into Unix timestamp and press Enter or Convert. The unit is suggested from the digit count: up to 11 digits is treated as seconds, 12 or more as milliseconds. Change Unit to override.
- To get a timestamp, choose a date and time, pick Local or UTC, then convert.
- Use the Copy button next to any value. Use current time fills in the present moment.
Frequently asked questions
What is the difference between seconds and milliseconds?
Unix time is traditionally in seconds (10 digits today, such as 1700000000). JavaScript, Java and many APIs use milliseconds (13 digits today), which is the seconds value multiplied by 1000.
Does a Unix timestamp depend on time zone?
No. A timestamp identifies one exact moment worldwide. Time zones only matter when you display it as a calendar date, which is why this tool shows both local time and UTC.
Can a timestamp be negative?
Yes. Negative values are moments before 1 January 1970 UTC. For example, -86400 is 31 December 1969.
What is the Year 2038 problem?
Systems that store seconds in a signed 32-bit integer overflow after 03:14:07 UTC on 19 January 2038. Modern 64-bit systems and JavaScript are not affected.
Why do I get an out-of-range error?
Browsers support dates up to 8,640,000,000,000,000 milliseconds either side of 1970, roughly 271,821 years. Values beyond that cannot be shown as a valid date.