Free developer tool
Unix Timestamp Converter
Convert Unix timestamps in seconds or milliseconds to dates in any time zone, and dates back to timestamps.
Current Unix time (s)
…
Milliseconds
…
UTC
…
Timestamp or date → every format
| ISO 8601 (UTC) | 2026-01-01T00:00:00.000Z |
|---|---|
| UTC | 2026-01-01 00:00:00 (UTC+00:00) |
| RFC 2822 | Thu, 01 Jan 2026 00:00:00 GMT |
| Unix seconds | 1767225600 |
| Unix milliseconds | 1767225600000 |
| Relative | — |
Date and time → Unix timestamp
| Unix seconds | 1767258000 |
|---|---|
| Unix milliseconds | 1767258000000 |
| ISO 8601 (UTC) | 2026-01-01T09:00:00.000Z |
| UTC offset | UTC+00:00 |
Unix time, explained
A Unix timestamp counts the seconds since 1 January 1970, 00:00 UTC. It's how most databases, APIs and log files store time, because it's the same everywhere in the world. Many systems, including JavaScript, use milliseconds instead.
Paste a timestamp in seconds, milliseconds, microseconds or nanoseconds (the unit is detected from the number of digits) or a date string, and see it in ISO 8601, any time zone, RFC 2822 and relative time. The second section converts a date and time in a chosen time zone back into a timestamp, with daylight saving time handled by your browser's time zone database.
Frequently asked questions
- How do I know if a timestamp is in seconds or milliseconds?
- Count the digits. Current timestamps in seconds have 10 digits, and in milliseconds they have 13. Auto-detect uses this rule, and you can pick the unit yourself.
- What is the year 2038 problem?
- Systems that store Unix time as a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. Modern systems use 64-bit values, which last for billions of years.
- Does Unix time include leap seconds?
- No. Unix time treats every day as exactly 86,400 seconds, so leap seconds aren't counted.