Epoch Time to Date Converter — Unix Timestamp to Date Online

How to use the Epoch Time to Date Converter

The tool works in both directions. To read a timestamp, type it into “Enter Epoch Time (seconds or milliseconds)” and click “Convert to Date”. The date appears below, shown in your browser’s local time. To go the other way, pick a date in “Select a Date” and click “Convert to Epoch Time” — the result is the epoch time in seconds.

You do not need to say whether your number is in seconds or milliseconds. The tool decides by length: a number with more than 10 digits is treated as milliseconds, anything shorter as seconds. That covers the two formats you will meet in practice, since current epoch seconds are 10 digits and milliseconds are 13.

Worked example: what is 1700000000?

Type 1700000000 into the converter and click “Convert to Date”. The instant it names is 14 November 2023 at 22:13:20 UTC. What you see on screen may show a different clock time, because the tool displays the date in your own time zone — for example, in Rome that same instant reads 14 November 2023 at 23:13, one hour ahead of UTC.

Two more values are worth knowing. Epoch 0 is the starting point itself: 1 January 1970 at 00:00:00 UTC. And the millisecond form of the first example, 1700000000000 (13 digits), names the exact same instant as 1700000000 — the tool recognises the extra three digits and divides accordingly. Going backwards, picking 1 January 2025 gives 1735689600, the number of seconds from 1970 to the start of that year in UTC.

Where it helps

API responses, database rows, log files and cookies all store times as epoch numbers. A developer debugging an API can paste a timestamp here instead of doing the division by hand. A support agent reading a log can turn an expiry value into a date a customer understands. Students learning programming meet epoch time in their first date-handling lesson, and seeing a familiar date come out of a ten-digit number makes the concept concrete. Anyone checking whether a token or a session really expired at the claimed time can verify it in seconds.

Honest limitations

The result is shown in your browser’s local time, not in UTC. That is convenient when you want “when did this happen for me”, but it means the same number shows a different clock time for a colleague in another time zone — so when you share a converted time, say which zone you mean. The seconds-or-milliseconds guess is based on digit length, so it only works for realistic modern values; it is not a substitute for knowing your source’s format. Dates before 1970 (negative epoch values) can behave oddly, because the length rule was not built with them in mind. And the reverse direction converts the date you pick at the precision the picker offers — it cannot recover a time of day that was never entered. For the reverse phrasing of this same problem, the date to epoch time converter covers it as its own query.

Epoch Time to Date Converter — frequently asked questions

Seconds or milliseconds — how do I tell which one I have?

Count the digits. Current epoch seconds have 10 digits (like 1700000000); milliseconds have 13 (like 1700000000000). This tool also decides for you: more than 10 digits is read as milliseconds.

Why does the same timestamp show a different time for my friend?

Because the tool displays the result in each browser’s local time zone. The instant is identical — only the clock reading differs. Convert with UTC in mind when you compare across zones.

What is epoch 0?

Epoch 0 is 1 January 1970 at 00:00:00 UTC, the starting point from which all Unix time is counted.

Can I convert a date back to epoch time here?

Yes. Pick a date in “Select a Date” and click “Convert to Epoch Time” to get the epoch value in seconds.