DEVELOPER TOOL

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

About Unix Timestamp Converter

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.

How to use Unix Timestamp Converter

  1. Click into the input box and type a date and time such as 2026-10-15T09:30:00Z, or paste a Unix timestamp with 10 or 13 digits.
  2. Or press Use current time to fill the box with the current moment.
  3. Read the result lines: Unix seconds, Unix milliseconds, ISO (UTC) and Local time.
  4. Add a Z or an offset such as +02:00 to a typed date if you want a result that does not depend on your device's time zone.
  5. Press Copy result to place all four lines on your clipboard, then paste the value you need.

When this tool helps

Reading a log or API value

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.

Setting an expiry

Type the date you want a token, cookie or cache entry to expire and copy the seconds value into your code or configuration.

Comparing seconds and milliseconds

JavaScript uses milliseconds while many back-end systems use seconds. The tool shows both so you can spot a factor-of-1000 mistake.

Debugging time zones

See the UTC time and local time side by side to confirm whether a scheduled job or report uses the zone you expect.

Tips for better results

  • Without a Z or offset, a typed date is read in your device's local time zone, so the same text can give different timestamps on different computers.
  • If a number looks like the year 1970, it is probably in seconds when milliseconds were expected, or the reverse for a date far in the future.
  • Use ISO 8601 text for typed dates. Other formats depend on the browser's parser and may be read differently.
  • Negative timestamps are allowed and represent dates before 1970.

Good to know

  • Values are classified by digit count. Timestamps with 15 or more digits, such as microseconds, are not recognized.
  • There is no time zone picker. The local line uses your device's zone, and the ISO line is always UTC.
  • Only one value can be converted at a time, and there is no batch mode.

Privacy and your data

Conversion happens in your browser. The text you enter is not sent to a server and is not stored.

Unix Timestamp Converter FAQ

What is a Unix timestamp?

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.

How do I convert a timestamp to a readable date?

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.

What is the difference between seconds and milliseconds?

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.

Why does my typed date give a different timestamp than a colleague's?

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.

Does a Unix timestamp include leap seconds or time zones?

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.

Browse all ELDOSA tools →