Unix Timestamp Converter
Convert Unix timestamps (seconds or milliseconds) to UTC, local and ISO 8601 dates and back, in any time zone. Runs in your browser: nothing is uploaded.
Current Unix time (seconds)
—
Processed locally in your browser. Your data never leaves your device.
About this Unix timestamp converter
Convert a Unix timestamp to a readable date, or a date to a Unix timestamp, in either direction. Results show ISO 8601 in UTC, the UTC string, the wall-clock time in the time zone you choose (with its offset), how long ago or from now it is, and the value in both seconds and milliseconds. A live clock shows the current Unix time.
How to use it
- Pick a time zone (your local zone by default).
- Enter a Unix timestamp on the left, or a date such as
2023-11-14 17:13:20on the right, or use the current time. - Copy any result. Leave Unit on Auto-detect, or force seconds or milliseconds.
Example
The timestamp 1700000000 is 2023-11-14T22:13:20Z in UTC, which is 17:13:20 in New York (UTC-05:00) and 07:13:20 the next day in Tokyo (UTC+09:00). As milliseconds it is 1700000000000.
Accepted date formats
- ISO 8601:
2023-11-14T22:13:20Z,2023-11-14T17:13:20-05:00,2023-11-14T22:13:20.123Z. - With a space:
2023-11-14 17:13:20,2023-11-14 17:13, or just2023-11-14. - Text with an offset (
Z,+01:00) is exact. Text without one is read as clock time in the selected time zone.
Common pitfalls
- Seconds versus milliseconds. A 13-digit value is milliseconds and a 10-digit value is seconds. Reading milliseconds as seconds gives a date in the year 55,000.
- Time zones. The timestamp itself has no time zone. The zone only affects how it is displayed, and how a clock time without an offset is read.
- Microseconds and nanoseconds. 16 and 19 digit values come from systems such as Python, Go and databases. Divide by 1,000 or 1,000,000 to get milliseconds.
- Leap seconds are ignored by Unix time, so every day has exactly 86,400 seconds.
Frequently asked questions
- What is a Unix timestamp?
- It is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970 (the Unix epoch), ignoring leap seconds. It is one number for one instant in time, the same everywhere in the world, which is why systems use it to store and compare times.
- How does this tool decide between seconds and milliseconds?
- Numbers below 100,000,000,000 are read as seconds (that reaches the year 5138) and larger numbers as milliseconds (100,000,000,000 ms is March 1973). JavaScript and Java use milliseconds; most Unix tools, databases and APIs use seconds. The tool tells you which it chose, and you can force either.
- What is the Year 2038 problem?
- A signed 32-bit integer overflows at 2147483647, which is 03:14:07 UTC on 19 January 2038. Software that stores timestamps in 32 bits will wrap to 1901 after that. Enter 2147483648 to see the next second. 64-bit timestamps do not have this limit.
- How are daylight saving gaps and overlaps handled?
- When a clock time is skipped (spring forward) or occurs twice (fall back) in the chosen time zone, the tool says so. For a skipped time it uses the offset from before the change; for a repeated time it uses the earlier of the two. To avoid ambiguity, include an offset such as +01:00 or Z.
- Does the tool send my data anywhere?
- No. All conversions run in your browser using its built-in date and time zone support. Nothing you type is uploaded.