Unix timestamp converter
Turn epoch timestamps into dates and dates into epoch values. The unit is detected automatically.
tool 08 of 12 []
all shortcuts ?
How to use it
- Paste an epoch value on the left. Values under 100 billion are read as seconds, under 100 trillion as milliseconds, then microseconds and nanoseconds. You can also force a unit.
- The result shows ISO 8601 in UTC, the same instant in your local time zone, an RFC 2822 string and a relative description such as "2 years ago".
- On the right, enter a date (2024-03-15, 2024-03-15 14:30:00 or a full ISO string with Z or an offset) to get epoch seconds and milliseconds.
- Dates with no offset are read as UTC unless you choose local time.
Examples
Select an example to load it into the tool.
- Seconds
1700000000 - Milliseconds
1700000000123 - Y2038 limit
2147483647 - ISO date with offset
2024-03-15T14:30:00+02:00
Frequently asked questions
What is a Unix timestamp?
The number of seconds since 1970-01-01 00:00:00 UTC, ignoring leap seconds. JavaScript, Java and many APIs use milliseconds instead, which is why the unit matters.
How does auto-detection work?
It looks at the size. A 10-digit number (like 1700000000) is seconds, 13 digits is milliseconds, 16 digits is microseconds and 19 digits is nanoseconds. Dates before 1973 expressed in milliseconds look like seconds, so choose the unit manually for those.
What is the year 2038 problem?
Systems that store seconds in a signed 32-bit integer overflow after 2147483647, which is 2038-01-19 03:14:07 UTC. Modern 64-bit systems are unaffected. Try it from the examples.
Why does my local time differ from the server log?
Epoch values are always UTC. Logs formatted in local time use the server's zone, which may differ from yours. Compare in UTC to avoid mistakes.
Does it handle negative timestamps and leap seconds?
Negative values give dates before 1970. Unix time ignores leap seconds, so a leap second shares its timestamp with the next second.