Convert an epoch value safely
Paste a signed whole number, check the detected unit, and choose the time zone used for the human-readable result. Values such as 1700000000, 1700000000000, 1700000000000000, and 1700000000000000000 represent the same instant in four different units.
Outputs explained
UTC is the universal reference. Local time uses the selected IANA zone and its daylight-saving rules. ISO 8601 is a stable machine-readable representation. Milliseconds are included so you can compare the converted value with JavaScript and many API payloads.
Common mistakes
- Treating a 13-digit millisecond value as seconds produces a date far outside the normal range.
- Appending
Zto a local date changes its meaning by declaring it UTC. - A timestamp represents an instant; it does not remember the place where it was created.
How to use this tool
Paste the original integer without adding separators. Select the documented unit or inspect the automatic suggestion, choose the display zone, and press Convert. Changing the input, unit or zone clears the previous result so it cannot be copied accidentally.
Worked input and output
| Input or setting | Expected result |
|---|---|
0 · s | 1970-01-01T00:00:00.000Z |
1700000000000 · ms | 2023-11-14T22:13:20.000Z |
-1 · ns | 1969-12-31T23:59:59.999Z |
Checks before using the result
UTC and ISO show the same instant in different formats. Microsecond and nanosecond rows preserve the exact integer; calendar dates use millisecond resolution. If a precision notice appears, keep the finer integer for a lossless export. An invalid integer and an out-of-range date have different errors. Check unit differences before correcting the source value.