This converter translates between Unix timestamps and calendar dates in both directions. It accepts seconds or milliseconds, shows ISO, UTC and local time, and keeps a live view of the current timestamp.
Your data is processed locally in your browser and is not uploaded to our server.
Current Unix timestamp—
Timestamp to date
Enter a valid Unix timestamp.
ISO 8601
2023-11-14T22:13:20.000Z
UTC
Tue, 14 Nov 2023 22:13:20 GMT
Local time
Wednesday, November 15, 2023 at 6:13:20 AM
Date to timestamp
Choose a valid local date and time.
Seconds
1704067200
Milliseconds
1704067200000
ISO 8601
2024-01-01T00:00:00.000Z
Timestamps are absolute; local time depends on your device time zone. Dates before 1970 use negative values.
How to use this tool
1 Copy the current Unix timestamp from the live counter at the top.
2 To convert a timestamp, paste it and choose seconds or milliseconds; the date appears immediately.
3 To convert a date, pick a local date and time; the seconds and milliseconds timestamps update as you type.
4 Use the copy buttons for the current timestamp, the ISO date or the numeric timestamp.
Formula and calculation logic
Timestamp to date
Date = 1 January 1970 UTC + timestamp × 1000 ms
A Unix timestamp counts seconds since 1970-01-01T00:00:00Z, ignoring leap seconds. Multiplying by 1000 gives the milliseconds used by JavaScript dates.
Date to timestamp
Seconds = floor(milliseconds ÷ 1000)
The date is converted to milliseconds since the epoch, then divided by 1000 for the seconds form. The milliseconds form keeps the full precision.
Worked example
1700000000 in UTC
A log entry stores a timestamp in seconds.
1700000000 × 1000 = 1700000000000 ms
ISO: 2023-11-14T22:13:20.000Z
Local time depends on your time zone
The same instant is 14 November 2023 at 22:13:20 UTC. Your local clock may show a different hour.
Midnight on 1 January 2024
A local date needs a timestamp for an API request.
Choose 2024-01-01 00:00 local time
Read the seconds value
Use the millisecond value if the API expects milliseconds
The exact numbers depend on your time zone, because the input is interpreted as local time.
Edge cases and accuracy
Seconds versus milliseconds
A seconds timestamp is about 1.7 billion today; the same instant in milliseconds is about 1.7 trillion. Choosing the wrong unit moves the date by decades, so check the unit before pasting.
Local time versus UTC
The timestamp itself is absolute. The local display depends on your device time zone, while ISO and UTC are the same everywhere.
Dates before 1970
Negative timestamps represent dates before the Unix epoch. They are valid and are handled by the converter.
Frequently asked questions
What is a Unix timestamp?+−
The number of seconds since 1 January 1970 at 00:00:00 UTC, not counting leap seconds. It is a timezone-independent instant.
Is the timestamp in seconds or milliseconds?+−
Both are supported. JavaScript uses milliseconds, while many APIs and databases use seconds. Choose the matching unit before converting.
Why does my local date differ from UTC?+−
A timestamp is an absolute instant; local time adds your timezone offset. The ISO and UTC rows show the same instant without that offset.
Does it handle daylight saving time?+−
The timestamp is unaffected by daylight saving. Local displays follow your device’s current timezone rules for that date.
Is the current timestamp updated live?+−
Yes. The counter at the top refreshes every second while the page is open.
Related developer tools
Hash, format or encode the data that carries these timestamps.