Paste Unix time or an ISO date. Seconds, milliseconds and a readable clock show up here.
Paste a number or a date. Now fills the current millisecond.
Unix time counts seconds from 1970-01-01T00:00:00Z. It does not count leap seconds: a POSIX day is 86,400 seconds. Milliseconds are that count times 1,000, which is what JavaScript’s Date uses.
ISO 8601 writes a calendar date, and a time of day with an offset. This page accepts a date-only form or a time with Z or a numeric offset. The ISO line it prints is always UTC, from Date.prototype.toISOString.
0
1970-01-01T00:00:00.000Z
1700000000 1700000000000
2023-11-14T22:13:20.000Z 2023-11-14T22:13:20.000Z
170000000000 read as seconds
170000000000 with Milliseconds
A date-only value such as 2026-10-16 is midnight UTC, which is the ECMA-262 rule for a date without a time. A time without Z or an offset is read in the local time zone. 10/16/2026 is rejected: only the ISO shape is accepted.
Years before 1 and after 9999 are rejected. An unreadable value keeps the previous result on screen.
The clock here has millisecond precision, because that is what Date stores. A fraction of a second in the input is kept when it lands on a whole millisecond.
The share link stores the text and the unit switch. The four lines are computed again when the link is opened. Now is not stored by itself: it writes the current millisecond into the field, and that text is what the link keeps.
The Unix epoch is 1970-01-01T00:00:00Z. POSIX defines time_t as seconds since that instant, not counting leap seconds, so every day has 86,400 seconds.
A signed 32-bit time_t overflows at 2038-01-19T03:14:07Z. Values past that instant need a wider integer. This page uses JavaScript numbers, which cover the years 1 through 9999.
ISO 8601 was first published in 1988. The date-time strings this page accepts are the ECMA-262 date time string format: a calendar date, an optional time, and Z or an offset such as +02:00.