What is a Unix timestamp?
A Unix timestamp is the number of seconds elapsed since 1 January 1970 at 00:00:00 UTC. Millisecond timestamps use the same starting point but count milliseconds instead.
Tools
Convert Unix seconds or milliseconds to local and UTC dates, or convert a local date back to both units.
Current offset: UTC+00:00
Convert Unix seconds or milliseconds into readable dates.
Interpret a date and time in the selected timezone.
Selected timezone: UTC (UTC+00:00)
A Unix timestamp counts the seconds elapsed since 1 January 1970 at 00:00:00 UTC. The same timestamp represents one instant worldwide; only its displayed date and time change by timezone. This converter accepts Unix seconds or milliseconds and converts a date in the selected timezone back to both units.
The number of digits usually identifies the unit used by current application data.
| Digits | Unit | Example | Typical use |
|---|---|---|---|
| 10 | Seconds | 1704067200 | APIs, server logs and database records |
| 13 | Milliseconds | 1704067200000 | JavaScript and systems that need sub-second precision |
This page handles seconds and milliseconds. It does not currently parse 16-digit microseconds or 19-digit nanoseconds.
A Unix timestamp does not contain a timezone. It identifies a single point in time relative to the Unix epoch in UTC.
When converting a timestamp, this page shows the time in your selected timezone and an ISO 8601 UTC value. A date entered in the date field is interpreted in the selected timezone, so check the timezone and UTC offset before copying the result.
The tool keeps the machine value and the readable date together so you can check API, log and database values.
A Unix timestamp is the number of seconds elapsed since 1 January 1970 at 00:00:00 UTC. Millisecond timestamps use the same starting point but count milliseconds instead.
Current Unix timestamps normally have 10 digits when measured in seconds and 13 digits when measured in milliseconds. This converter accepts both.
No. A Unix timestamp represents one point in time and does not store a timezone. Timezones only affect how that point is displayed as a date and time.
The devices or tools may use different selected timezones. The underlying timestamp is unchanged, while the readable date and time reflect the chosen timezone.
The date field is interpreted in the timezone selected above the converter. Choose the browser timezone, UTC, Hong Kong or Shanghai, then verify the displayed UTC offset before copying.
No. The conversion runs in your browser. The timestamp and date entered in this tool are not sent for server-side conversion.
Continue checking the API payload, token, schedule or encoded value associated with your timestamp.