Timestamp to date
Date to timestamp
How to use the timestamp converter
- Paste a Unix timestamp into Timestamp to date. The tool reads its unit from the number of digits and tells you what it assumed; if that is wrong, choose the unit yourself.
- Read the date in UTC, in your own time zone, as ISO 8601 and relative to now. Each value has its own Copy button.
- To go the other way, pick a date and time under Date to timestamp and say whether it is your local time or UTC.
What a Unix timestamp is
A Unix timestamp counts the seconds since 1 January 1970 at 00:00:00 UTC (the “Unix epoch”), not counting leap seconds. The same moment has the same timestamp everywhere in the world, which is why servers and databases store time this way and only convert to a time zone for display. Times before 1970 are negative.
Seconds, milliseconds, microseconds, nanoseconds
Systems disagree on the unit. Unix tools, PHP’s time() and most APIs use seconds (10 digits for today’s dates). JavaScript’s Date.now() and Java use milliseconds (13 digits). Python’s time.time_ns() and Go’s UnixNano() use nanoseconds (19 digits), and some databases store microseconds (16 digits). Mixing them up gives dates in 1970 or tens of thousands of years from now, so this tool always shows which unit it used. Very long values are converted with exact whole-number arithmetic rather than rounded first.
Time zones and daylight saving
“Your time” uses the time zone your browser reports. Around daylight-saving changes, some local times do not exist (the clocks jump forward) and others happen twice (they fall back); the tool warns you in both cases. When precision matters, enter the time in UTC.
Dates from about 271,821 BC to AD 275,760 work. Signed 32-bit timestamps stop at 03:14:07 UTC on 19 January 2038 (the “Year 2038 problem”), and the tool notes when a date is past it.
Everything is calculated in your browser; nothing you enter is sent to this site.