Home › Unix Timestamp Converter
Unix Timestamp Converter
Enter a Unix timestamp or a date and read it in ISO 8601, in the time zone offset you choose, with the weekday and day of the year.
Results
- Unix time (seconds)
- 1,700,000,000
- Milliseconds
- 1,700,000,000,000
- ISO 8601 (UTC)
- 2023-11-14T22:13:20.000Z
- Date and time in the chosen offset
- 2023-11-15 01:13:20 (UTC+03:00)
- Weekday
- Wednesday
- Day of the year
- 319
- Input read as
- seconds
How it works
A Unix timestamp counts the seconds since 1 January 1970 at 00:00 UTC. A number with 11 or more digits is read as milliseconds, anything shorter as seconds. A date such as 2025-03-14 09:30:00 is read in the UTC offset you set, unless it ends with Z or its own offset. Results are shown in UTC and in your chosen offset.
Rules and details
seconds = floor(milliseconds ÷ 1000)Auto-detect: |value| ≥ 100,000,000,000 → milliseconds, otherwise secondsLocal time = UTC + offset hours (fractions allowed, for example 5.5)Accepted dates: YYYY-MM-DD, YYYY-MM-DD HH:MM[:SS], ISO 8601 with Z or ±HH:MM
Worked example
The timestamp 1700000000 is 2023-11-15 01:13:20 in the offset UTC+3, which is 2023-11-14T22:13:20.000Z in UTC. That day is a Wednesday. As a check, 1 January 2025 at 00:00 UTC is 1,735,689,600 seconds, and the first input is 1,700,000,000,000 milliseconds.
Frequently asked questions
How do I know whether a timestamp is in seconds or milliseconds?
Current dates are around 1.7 billion in seconds (10 digits) and 1.7 trillion in milliseconds (13 digits). This tool reads 11 digits or more as milliseconds.
Does the tool handle daylight saving time?
It uses a fixed offset that you enter, so it never guesses. If your region changes its offset during the year, enter the offset valid on that date.
What is the year 2038 problem?
Systems that store seconds in a signed 32-bit integer overflow on 19 January 2038. JavaScript uses 64-bit numbers, so this tool is not affected.
Tips
- Leave the field empty to see the current timestamp, which updates when you edit any field.
- Use ISO 8601 with a trailing Z in logs and APIs to avoid time zone confusion.
- Negative timestamps are dates before 1970.