Timestamp converter
Convert Unix timestamps and dates in either direction, by time zone. Everything is calculated inside this browser.
Current time
- Unix seconds
-- Unix milliseconds
-- ISO 8601 (UTC)
-- Local time zone
-
This device clock is read at the start of every second. Copying takes the value shown on screen.
Timestamp to date
Could not convert.
How to fix
Results appear here once you enter a timestamp.
Date and time to timestamp
A time that does not exist because of daylight saving is moved forward by the skipped amount, and a time that occurs twice uses the earlier one. You are told below when this applies.
Could not convert.
How to fix
Results appear here once you enter a date and time.
Values convert as you type. Use the copy buttons to take a result.
How to use the timestamp converter
Use it to turn a Unix timestamp from a log or API response into a readable date, or to turn a date and time in a given time zone into a timestamp.
- Copy the current seconds or milliseconds timestamp from the current time panel at the top.
- On the left, enter a timestamp and choose a time zone to get UTC, local, the chosen zone and ISO 8601.
- On the right, enter a date and time and its time zone to get Unix seconds and milliseconds.
Example: 1700000000 2023-11-14T22:13:20.000Z
Rules and limits
- The supported range is ±8,640,000,000,000,000 milliseconds (about ±275,760 years); values outside it are reported as errors.
- Auto-detect reads up to 11 integer digits as seconds and 12 or more as milliseconds. Pick the unit yourself if unsure.
- Unix time does not count leap seconds. A day is always 86,400 seconds, and a leap-second time (23:59:60) cannot be entered.
- Seconds are rounded down below the millisecond, and negative timestamps before 1970 follow the same rule.
- Time zones follow the IANA data built into your browser, so old historical daylight saving records may differ between browsers.
- Entered values and the chosen time zone are not saved or sent anywhere and disappear on reload.
Frequently asked questions
Is my input sent to a server?
No. Every conversion runs inside this browser, and input and results are neither saved nor sent.
How are daylight saving transitions handled?
When the clock skips ahead in spring and a time does not exist (for example New York 2024-03-10 02:30), it is moved forward by the skipped amount and calculated as 03:30. When a time occurs twice in autumn (for example New York 2024-11-03 01:30), the earlier daylight-saving one is used and the later value is shown too.
Is there a year 2038 problem?
This tool uses JavaScript numbers rather than 32-bit integers, so dates after 2038 convert correctly within the supported range.
Where does the local time zone come from?
It is the time zone this device reports through the browser. UTC is used when it cannot be determined.