Epoch to date and date to epoch, in any time zone, with a live clock.
A Unix timestamp counts the time since 1 January 1970, 00:00:00 UTC, the "epoch". It is how databases, logs, APIs and programming languages store a moment as a single number. This tool turns that number into a date you can read, and a date back into a number. It shows the same moment in the time zone you pick, as ISO 8601, as an RFC 2822 date, as a readable sentence in your language, and as a relative time such as "3 days ago". Everything is calculated in your browser.
Type or paste a value into the one box. If it is a number, it is read as a timestamp; if it looks like a date, it is read as a date. With an empty box the tool shows the current time and updates it every second; switch "Live clock" off to freeze it. Press Now to fill the box with the current timestamp. Every row has its own Copy button.
1700000000 is Tuesday 14 November 2023, 22:13:20 UTC.2023-11-14 22:13:20 in UTC is 1700000000. A date without an offset is read in the time zone chosen above it; one with Z or an offset such as +07:00 carries its own.The same moment is written with a different number of digits depending on where it comes from. 1700000000 (10 digits) is seconds, as used by Unix, PHP, MySQL and JWT. 1700000000123 (13 digits) is milliseconds, as used by JavaScript's Date.now() and Java. 16 digits are microseconds and 19 digits are nanoseconds, as in Python's time functions and Go's UnixNano. The tool counts the digits and picks the unit for you, and you can override it when you know better. Reading milliseconds as seconds is the classic mistake: it gives a date tens of thousands of years from now.
A timestamp has no time zone; the zone only decides how it is written. The same 1700000000 is 05:13:20 on 15 November in Ho Chi Minh City (UTC+07:00) and 17:13:20 on 14 November in New York (UTC-05:00). The tool uses your browser's copy of the IANA time zone database, so daylight saving is handled by data, not by guesswork.
Dates typed without an offset can fall on the awkward hours of a clock change, and the tool tells you when they do. In New York, 02:30 on 10 March 2024 never happened, because the clocks jumped from 02:00 to 03:00; the tool moves it forward to 03:30. And 01:30 on 3 November 2024 happened twice; the tool uses the earlier one, 05:30 UTC, and says so. The latest moment this page can show is 31 December 9999.
2147483647, which is 19 January 2038, 03:14:07 UTC. Systems that still use 32 bits must move to 64.-86400 is 31 December 1969.=A2/86400+25569, formatted as a date (25569 is the number of days between Excel's 1900 starting point and 1970); divide by 86,400,000 for milliseconds.Timestamps usually arrive inside API responses and exports: the JSON formatter makes those readable, and the CSV and JSON converter turns an export into a table.
Count the digits. A current timestamp has 10 digits in seconds and 13 in milliseconds. The tool does this automatically and shows how it read your number; you can pick the unit yourself.
No. It is always counted from the epoch in UTC. The time zone only affects how the moment is displayed as a date and time.
Because of daylight saving. When clocks go forward an hour of wall-clock time is skipped, and when they go back an hour is repeated. The tool picks a sensible moment and tells you.
The years 1 to 9999. That covers all realistic values, including timestamps past 2038 and before 1970.
No. The conversion uses your browser's own date and time zone data, and nothing you type leaves the page.
Updated October 13, 2026 · More in Developer