Seconds to a readable date
1767225600
2026-01-01T00:00:00Z
Unix Timestamp Converter
Convert between Unix time and human dates in any timezone.
Result
Nothing to show yet. Enter something above to get started.
Was this tool useful?
About this tool
Unix time counts the seconds since 1 January 1970 UTC. It is what databases, log files and APIs store, because a single integer has no timezone ambiguity and sorts correctly without any parsing.
The trade-off is that it means nothing to a human. This converter goes both ways and shows the result in your timezone, in UTC and as ISO 8601 at the same time — which is usually what you need when you are comparing a log line against a report.
How to use it
- Enter a timestamp to convert it to a date, or pick a date to get the timestamp.
- Leave the unit on automatic unless the value is ambiguous: ten-digit values are read as seconds, thirteen-digit ones as milliseconds.
- Change the timezone to see the same instant somewhere else. Your browser's zone is selected by default.
- Copy whichever representation you need — local time, UTC, ISO 8601, seconds or milliseconds.
Examples
Milliseconds from a JavaScript log
Date.now() returns milliseconds, which is why the value has thirteen digits.
1767225600000
2026-01-01T00:00:00Z
Common problems
- The date is off by about 55 years.
- A milliseconds value was read as seconds, or the other way round. Set the unit explicitly instead of relying on detection.
- The result is an hour out.
- Daylight saving. The offset depends on the date, not just the zone — this converter applies the rules that were in force at that instant.
- A very large value is rejected.
- It falls outside the range a date can represent (roughly ±273,000 years around 1970). Check whether the value is actually microseconds or nanoseconds.