Timestamp Converter | How to use and interpret results
Convert Unix seconds or milliseconds to a local date/time and back. UTC ISO and local displays let you compare a numeric log timestamp with its represented instant.
- Runs in your browser
- Nothing is uploaded
- No signup; device limits apply
Loading the tool. If it does not appear, reload this page.
How to use this tool
Select seconds or milliseconds before entering the number, or choose a local date/time. The numeric units differ by 1000, and local input follows the browser's time zone.
Results and examples
Zero seconds is UTC 1970-01-01T00:00:00.000Z. A device set to Korea displays the same instant at 9 am, so different clock labels do not indicate an error.
Worked example
Zero seconds is UTC 1970-01-01T00:00:00.000Z. A device set to Korea displays the same instant at 9 am, so different clock labels do not indicate an error.
Limitations
- Operating-system clock and time-zone accuracy are not verified.
- Leap seconds and server-specific log conventions are not separately modelled.
Fields
| Field | Guidance and constraints |
|---|---|
| Unix timestamp | Check the unit and format displayed beside this field. |
| Seconds (s) | Check the unit and format displayed beside this field. |
| Milliseconds (ms) | Check the unit and format displayed beside this field. |
| Local date/time | Check the unit and format displayed beside this field. |
Data handling
Processing stays in the current browser tab; the site does not upload tool input for the calculation itself.
Sources
Frequently asked questions
Why can zero display as 9 am locally?
Zero seconds is UTC 1970-01-01T00:00:00.000Z. A device set to Korea displays the same instant at 9 am, so different clock labels do not indicate an error.
Are seconds and milliseconds detected automatically?
Operating-system clock and time-zone accuracy are not verified. Leap seconds and server-specific log conventions are not separately modelled.
