Timestamp

How to use it

1. Paste a Unix timestamp (seconds, milliseconds, microseconds or nanoseconds) or an ISO 8601 date and time — the values appear as you type, with no button to press.
2. If the unit is guessed wrong, pick Seconds or Milliseconds. The line above the values always says how the input was read: by digit count, by the unit you chose, or by the offset inside the date.
3. Choose a zone to see that zone instead of your own; the UTC and ISO 8601 rows never change. Copy the row you need, or start from the current time with “Use now”.

Example

1767225600

Read 10 digits as Seconds
Zone: 01/01/2026, 08:00:00 AM GMT+8
UTC: 01/01/2026, 12:00:00 AM UTC
ISO 8601: 2026-01-01T00:00:00.000Z
Unix seconds: 1767225600
Unix ms: 1767225600000

Ten digits is read as seconds. The first row follows the zone dropdown and the UTC/ISO rows do not, because they describe the same instant for everyone. The relative row is left out of the example: it depends on when you read this, not on the value.

Rules, limits and known issues

• Zones offered: your own, UTC and 12 common IANA zones. For any other zone, write the offset into the date (2026-01-01T08:00:00+09:00) or change your system zone.
• Dates must be unambiguous ISO 8601: 2026-01-01 or 2026/01/01, optionally followed by T or a space and HH:mm[:ss[.SSS]], optionally Z or ±HH:mm. 03/04/2026 and “Jan 5, 2026” are rejected rather than guessed — they read differently in different countries.
• A date without an offset is read in your own zone, and the line above the values says which zone that was. A date with Z or ±HH:mm is read in that offset.
• Digit count decides the unit: up to 10 digits = seconds, 11–13 = milliseconds, 14–16 = microseconds, 17–19 = nanoseconds. Leading zeros count, so 0001767225600 is read as milliseconds — pick “Seconds” to force it.
• Milliseconds is as precise as it gets: microsecond and nanosecond input is truncated toward zero, and the note above the values says so. Leap seconds (:60) are rejected instead of being rounded.
• Local times that do not exist are errors, not adjustments: 2026-03-08 02:30 is skipped in New York and the tool will not quietly move it to 03:30. A time that happens twice, when the clocks go back, is read as the earlier one.
• Unix seconds use floor: -1500 ms reads as -2 s. Times before 1970 work, and the range ends at the browser Date limit (about 271,821 BC and 275,760 AD).
• Digits may be typed as ASCII, Arabic-Indic, Persian or full-width, and bidi marks from copied Arabic text are ignored. The ISO 8601 and Unix rows always come out in plain ASCII.
• Not included: interval maths, batch conversion, week numbers, day-of-year, Julian day, RFC 2822 output, time-zone history beyond what your browser ships, and links that carry the value. The input never leaves the page and never enters the URL.

Related tools

What people usually need next, once the instant is clear.