Practical guide
Convert a Nine-Digit Unix Timestamp Without Guessing the Unit
Read a historical log timestamp as seconds, verify its UTC instant and millisecond form, and distinguish the instant from its local display.
Prepared by DoItAl · Worked examples checked . How examples are checked and corrected
The job: interpret an older log value
A copied event log contains 946684800 with no unit label. It has nine digits because it dates from 2000. Its length alone does not prove whether the sender meant seconds or milliseconds. Check the source system's field definition first; this example assumes it explicitly says Unix seconds.
DoItAl's Auto setting deliberately refuses this nine-digit value as ambiguous. That refusal prevents a plausible-looking but wrong date from being copied into an incident report.
946684800Convert with an explicit unit
Choose Timestamp → date/time, paste 946684800 into Unix timestamp, set Timestamp unit to Seconds, and choose UTC as the display zone. Press Convert epoch. The result is the first instant of 2000 in UTC, and the tool supplies both exact unit spellings and an ISO 8601 UTC value.
Copy the ISO result when a report needs an unambiguous date and time. Copy milliseconds only if the receiving API documents milliseconds; adding three zeros is correct for this whole-second example but is not a universal rule for fractional input.
| Output | Value |
|---|---|
| Unix seconds | 946684800 |
| Unix milliseconds | 946684800000 |
| ISO 8601 UTC | 2000-01-01T00:00:00.000Z |
Display zone changes the clock, not the instant
Switch the display zone to America/New_York and convert again. The selected-zone clock reads 1999-12-31 19:00:00, while the ISO result and both Unix values stay the same. The previous calendar date is expected because New York was five hours behind UTC at that instant.
For a scheduled meeting expressed as a local wall-clock time, start with the Date/time → timestamp job or the Time Zone Converter. A timestamp already identifies one instant; a local date/time needs a zone and, around daylight-saving transitions, may need an explicit occurrence choice.
Limits and next checks
Seconds may contain up to three decimal places; milliseconds must be integers. Auto only assumes ten-digit seconds or thirteen-digit milliseconds, plus zero and fractional seconds. Historical or future values of other lengths need a manual unit choice. Exponents, microseconds, nanoseconds, leap seconds, and batch import are outside this tool's current scope.
If this value came from JSON, validate the JSON structure separately before copying a field. JSON syntax validation cannot tell you whether its timestamp unit is seconds or milliseconds. The conversion runs in the browser; confirm the original field definition and keep the source record for your audit.
Material update: