Unix Timestamp Converter

Worked example

Epoch second zero converts to 1970-01-01T00:00:00 in the UTC zone by definition, since that instant is the epoch's own reference point. Converting the same epoch value into America/New_York instead lands on 1969-12-31T19:00:00, five hours earlier on the clock, because New York sits five hours behind UTC in the winter standard-time offset that applied at that historical instant. The real, underlying instant on the universal timeline never changes between these two results. Only its local wall clock reading does, which is exactly the point of separating an epoch value from a zoned date and time in the first place.

Common mistakes

• Confusing epoch seconds with epoch milliseconds. A JavaScript timestamp from Date.now() is in milliseconds, a thousand times larger than the equivalent Unix second count, and mixing the two units silently produces a date centuries off.
• Assuming an epoch value converts to the same wall clock date everywhere. It does not. The same instant can fall on different calendar dates depending on the zone, a point covered in the UTC versus local time resource linked below.

Limitations

Conversion depends on your browser's own IANA time zone data staying current, which is maintained through normal browser and operating system updates rather than anything this page controls. A future daylight saving rule change in a given zone is reflected automatically once your browser's data is updated, not before.