Unix Time Converter

Unix time represents an instant as the number of elapsed seconds since 00:00:00 Coordinated Universal Time on January 1, 1970. That starting instant is called the Unix epoch. The format is compact, sortable, and independent of a display language, which makes it common in operating systems, databases, APIs, log files, authentication tokens, and software protocols. A timestamp of zero identifies the epoch itself, while 946684800 identifies the beginning of January 1, 2000 in UTC. This converter works in both directions. In timestamp-to-date mode, it multiplies the supplied epoch seconds by 1,000 because JavaScript dates store milliseconds, then formats the instant as an ISO 8601 UTC value. In date-to-timestamp mode, it parses an ISO 8601 date, obtains milliseconds since the epoch, divides by 1,000, and rounds down to a complete second. Including the trailing Z in an input explicitly identifies UTC and avoids accidental interpretation in the computer's local time zone. Unix timestamps do not contain a time-zone label. They identify one absolute instant, which can be displayed as different wall-clock times in different regions. Time zones and daylight-saving rules matter only when formatting or interpreting a local date. This tool displays UTC so results remain stable across devices and locations. When converting a date, include Z for UTC or an explicit numeric offset such as plus 02:00 when the source time is not UTC. Most current systems use signed 64-bit values and can represent dates far beyond the older limits associated with 32-bit Unix time. Some legacy software stores timestamps in signed 32-bit fields and encounters the year 2038 problem when the value exceeds its maximum. Another frequent mistake is confusing seconds with milliseconds: modern browser timestamps often contain 13 digits, whereas present-day Unix seconds generally contain 10 digits. Divide milliseconds by 1,000 before entering them here. Use the converter to inspect API responses, debug database rows, verify scheduled events, translate log entries, and create test data. Date parsing follows the ISO 8601 conventions supported by the browser. For unambiguous results, provide a complete year-month-day value, a time, and either Z or an offset. Leap seconds are not represented as separate Unix seconds, so timestamp calculations follow the conventional continuous count used by mainstream computer systems.