Task path / input to outcome
How to convert timestamps across time zones
- 01
Pick the input type
Auto detection is a heuristic: absolute numeric values of 100000000000 or more use milliseconds; smaller values use seconds. Select an explicit unit when needed.
- 02
Enter or paste the value
Use Unix decimals, YYYY-MM-DDTHH:mm[:ss[.SSS]] for wall time, or an ISO date-time with Z/±HH:mm. RFC dates require an English month, four-digit year, seconds and GMT/UTC or ±HHmm. Limit: 512 UTF-8 bytes. Invalid days, leap seconds, 24:00 and unknown -00:00 offsets are rejected. Time-zone rules come from this browser and may differ across devices.
- 03
Set the source and output zones
Choose explicit zones in Source time zone and Output time zone instead of relying on guesses. The pickers offer UTC, the browser local zone, and eight named IANA zones from America/New_York to Australia/Sydney. The source zone only matters for wall times — a Unix timestamp is already an absolute instant — and the current browser local time stays visible as a reference point.
- 04
Review the result and resolve DST cases
The Equivalent instant pane shows every representation of the same moment: Unix seconds and milliseconds, ISO 8601, the UTC string, and formatted lines in the browser local zone and the chosen output zone. If the wall time falls in a DST overlap, pick the Earlier or Later occurrence explicitly; if it falls in a gap, the conversion fails with a clear message instead of being shifted silently. Unix and ISO output preserve milliseconds. Discord uses whole seconds rounded down, including before 1970.
- 05
Copy the result or the Discord codes
The result also carries three Discord timestamp codes built from the same instant — full, relative, and short date-time, such as <t:1700000000:F> and <t:1700000000:R> — which every reader's client renders in that reader's own zone. Use Copy result for the whole summary or Download .txt to keep it with the incident notes.