Unix Timestamp Converter
Convert dates to Unix timestamps and Unix timestamps back to dates.
Enter a date or a Unix timestamp, or press Use current time
Convert dates to Unix timestamps and Unix timestamps back to dates.
Enter a date or a Unix timestamp, or press Use current time
A Unix timestamp counts the seconds since midnight UTC on 1 January 1970. This converter works in both directions. Type a date such as 2026-10-15T09:30:00Z and it shows the Unix seconds and milliseconds. Paste a number such as 1792056600 and it shows the matching date. Press Use current time to fill in the present moment and see what an epoch value for right now looks like.
The result has four lines: Unix seconds, Unix milliseconds, the ISO 8601 time in UTC, and the local time in your device's time zone. Numbers with 9 to 11 digits are read as seconds and numbers with 12 to 14 digits as milliseconds, which covers the values you meet in logs, APIs and databases. Anything else is passed to the browser's date parser, so ISO formats work best, and a message explains when a value cannot be read.
Paste the epoch number from a log line, token claim or database column and see at once when the event happened in UTC and in your own time zone.
Type the date you want a token, cookie or cache entry to expire and copy the seconds value into your code or configuration.
JavaScript uses milliseconds while many back-end systems use seconds. The tool shows both so you can spot a factor-of-1000 mistake.
See the UTC time and local time side by side to confirm whether a scheduled job or report uses the zone you expect.
Conversion happens in your browser. The text you enter is not sent to a server and is not stored.
It is the number of seconds that have passed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. Systems use it because a single number is easy to store, compare and sort, and it does not depend on a time zone.
Paste the number into the box. With 10 digits it is treated as seconds and with 13 digits as milliseconds. The result shows the date in UTC and in your local time zone, so you can read it either way.
Milliseconds are a thousand times larger numbers for the same moment. 1792056600 seconds and 1792056600000 milliseconds are the same instant. JavaScript and Java often use milliseconds, while many databases and Unix tools use seconds.
A date typed without a Z or offset is read in the local time zone of each device. Add Z for UTC or an offset like +02:00, and everyone gets the same timestamp.
No. Unix time ignores leap seconds, treating every day as exactly 86,400 seconds, and it has no time zone of its own because it counts from a fixed UTC moment. Time zones matter only when you display the value as a local date.