Timestamp & date converter
Convert timestamps and common date formats.
Enable JavaScript to use this interactive tool. Paste input, choose options, then copy or download the result, or save it to your notebook.
Example and common questions
Read a timestamp from an API response or log without confusing seconds and milliseconds. The millisecond value 1704067200000 and the second value 1704067200 represent the same instant. An explicit unit makes that interpretation clear.
How to read a Unix timestamp in UTC
- Paste a Unix timestamp or date; common formats update automatically.
- Review the detected formats and confidence scores. The highest-confidence match is applied automatically; select another candidate when needed.
- Review the labelled formats and copy the value required by your log, query, or document.
Read Unix milliseconds as a UTC date
- Dates without a timezone
- UTC
- Numeric date order
- Auto-detect
- Unix input unit
- milliseconds
17040672000002024-01-01T00:00:00.000ZHow are units interpreted?
Common Unix units are ranked using the number format and digit count. Confidence scores are estimates; choose another detected format to use a different unit. An explicit unit suffix such as ms gives one 100% match. Unix output retains available nanosecond precision, while calendar displays use milliseconds.
Which timezone applies?
Dates without a timezone use your selected browser-local or UTC setting. An explicit timezone offset in the input is respected.
How are ambiguous numeric dates handled?
Dates such as 03/04/2026 show day-first and month-first candidates at 50% each. Day first is applied by default when the scores tie; select the other candidate to switch. Dates without a timezone use the setting in Timezone options.
Common errors and limitations
Check invalid calendar dates, unsupported precision and dates outside the supported range. For ambiguous values, review the candidate previews and choose the intended format. Use Timezone options for dates without an offset.