Epoch Timestamp Converter
Convert between Unix timestamps (seconds or milliseconds) and human-readable dates in both UTC and your local time.
Converted locally — UTC and your local time side by sideHow to use
Enter a Unix timestamp in seconds or milliseconds, or type a normal date and time, then click Convert to see both directions at once. The tool auto-detects whether your number is seconds or milliseconds by its magnitude and shows the equivalent in the other unit, so you never have to guess which one you are holding. Both Coordinated Universal Time (UTC) and your browser's local time are displayed side by side, along with the ISO 8601 string and the individual year, month, day, hour, minute and second components for easy copying.
Example
Unix(s): 1752739200 UTC: 2026-07-17T00:00:00.000Z
FAQ
How do I know seconds vs milliseconds?
Values above about 1e11 are milliseconds; the tool auto-detects and shows both.
What timezone is shown?
Both UTC and your browser's local time are displayed.
Why are there seconds and milliseconds?
Older systems and many APIs count seconds since 1970-01-01, while JavaScript Date.now() and some databases count milliseconds. Mixing them up shifts a date by a thousand times, so the converter always shows both.
What is the epoch start date?
The Unix epoch begins at 00:00:00 UTC on 1 January 1970. Timestamps before that moment are negative.
Does it handle leap seconds?
No mainstream operating system tracks leap seconds in the Unix clock. The converter follows the standard POSIX model where every day is exactly 86400 seconds, which matches how your own code will behave.
How do I convert a date to epoch?
Type or paste a date and time into the input and click Convert; the tool reads it and shows the matching Unix timestamp in both seconds and milliseconds. If your input omits a timezone, it is treated as your local time.
What date formats can I type?
Most ISO 8601 and common date strings are accepted, including "2026-07-17T00:00:00Z" and "July 17, 2026". Ambiguous formats are interpreted by your browser the same way your own code would interpret them.
Why does my timestamp show the wrong year?
A wrong year almost always means seconds and milliseconds were swapped: a value meant as milliseconds but read as seconds lands roughly a thousand times further in the future. The converter shows both units, so the mix-up is obvious at a glance.