Unix Timestamp Converter

A Unix timestamp counts time since 00:00:00 UTC on 1 January 1970. Logs, databases, JWTs and APIs store dates this way, but in different units — seconds in most APIs, milliseconds in JavaScript, microseconds in Python and PostgreSQL, nanoseconds in Go and many log systems. This converter reads the unit from the number’s length, shows the moment as a readable date in your time zone with how long ago it was, and lists it as seconds, milliseconds, microseconds, nanoseconds, ISO 8601 and the HTTP date format. It also converts the other way, from a date to a timestamp, and shows the same instant in any time zone with daylight saving applied.

1. To read a timestamp, paste it in “Timestamp → date”. The unit is detected automatically; choose one if yours is unusual.
2. To make a timestamp, type a date in “Date → timestamp”, such as 2026-09-13T14:30:00+05:30.
3. Read the result: the local date, a relative time, and every format with a copy button.
4. Pick another time zone to see the same moment there — useful for scheduling across offices.
5. Press “Use it” to load the current Unix time.

• Unix time ignores leap seconds, as nearly every system does, so it can differ from atomic time by a few seconds.
• Dates are limited to about 270,000 years either side of 1970 — the range JavaScript can represent.
• Automatic unit detection assumes dates near the present. A seconds timestamp for the year 5000 has 12 digits and would be read as milliseconds; choose the unit when that matters.
• A date-time without a zone is read in your device’s time zone, and a date on its own (2026-09-13) as midnight UTC — both as the ECMAScript standard specifies.
• Time-zone rules come from your browser and can lag behind very recent government changes.
• All conversion uses your browser’s date and time-zone data. Nothing is sent, and nothing you enter is saved.

Count the digits. A current date is 10 digits in seconds and 13 in milliseconds; 16 is microseconds and 19 nanoseconds. The converter shows which unit it used.

Systems that store Unix seconds in a signed 32-bit integer overflow at 03:14:07 UTC on 19 January 2038 (2147483647). Modern systems use 64 bits, which lasts far beyond any practical date.

No. It’s the same number everywhere at the same instant. Time zones only matter when you display it as a date, which is why this tool can show one timestamp in several zones.

India Standard Time is defined as 82.5° east of Greenwich, five and a half hours ahead of UTC, and India doesn’t use daylight saving time, so the offset never changes.