Unix Timestamp Converter
Paste a Unix timestamp to see the date in UTC, your local time and ISO 8601, or paste a date to get its epoch value. Seconds, milliseconds and microseconds are detected automatically.
Accepts Unix time in seconds, milliseconds, microseconds or nanoseconds, and dates like 2024-02-29, 2024-02-29 12:00, ISO 8601 or RFC 2822. Dates without a time zone are read as your local time.
- ISO 8601 (UTC)
- Unix (seconds)
- Unix (milliseconds)
- UTC
- Your time
- Relative
- Day
- Input
How it works
- Paste a valueA Unix timestamp such as 1700000000, a JavaScript millisecond value, or a date string.
- Unit detectionTen-digit numbers are read as seconds, thirteen digits as milliseconds, sixteen as microseconds; override it with the Unit menu.
- See every formatISO 8601, epoch seconds and milliseconds, UTC, your local time with time zone, relative time and the ISO week.
- Go the other wayPick a date and time, or click "Use now", to get the timestamp.
What Unix time is
Unix time counts the seconds since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. It is a single number with no time zone, which makes it the standard way to store and compare moments in databases, logs, APIs and file systems. For example, 1700000000 is 22:13:20 UTC on 14 November 2023. Unix time ignores leap seconds, so every day is exactly 86,400 seconds long.
Different systems use different units. Unix tools, Python's time.time() (rounded) and most APIs use seconds; JavaScript's Date.now() and Java's System.currentTimeMillis() use milliseconds; some databases and tracing systems use microseconds or nanoseconds. Mixing them up is a classic bug that produces dates in 1970 or in the year 55,000, which is why this tool shows how it read your input.
Time zones and ISO 8601
ISO 8601 strings such as 2024-02-29T12:00:00Z are unambiguous: the Z means UTC, and an offset like +05:30 gives the local offset. A date without a zone, such as 2024-02-29 12:00, means different moments in different places; this tool reads it in your browser's time zone unless you tick "as UTC" in the date picker. When exchanging times between systems, store Unix time or ISO 8601 with an offset.
The year 2038 problem
Systems that store Unix time in a signed 32-bit integer run out at 2147483647, which is 03:14:07 UTC on 19 January 2038. After that the value wraps to a negative number, a date in 1901. Modern operating systems and languages use 64-bit time, but embedded devices and old databases may still be affected. Paste 2147483647 above to see the moment.
Frequently asked questions
How do I get the current Unix time?
It is shown live in the options bar; click "Use now" to convert it. In code: Math.floor(Date.now() / 1000) in JavaScript, int(time.time()) in Python, or date +%s in a shell.
Why is my timestamp showing 1970?
It was probably in seconds but read as milliseconds, or the value was 0. Set the Unit menu explicitly.
Can it handle dates before 1970?
Yes. Earlier dates are negative Unix times.
Does it send my data anywhere?
No. Conversion uses your browser’s date functions.