A Unix timestamp is the number of seconds since 1970-01-01 00:00:00 UTC. JavaScript and Java use milliseconds, some databases and tracing tools use microseconds. The converter picks the unit by the number of digits: 10 digits are seconds, 13 are milliseconds, 16 are microseconds. If the guess is wrong, set the unit by hand.
The result is shown in UTC, in your local time zone, as ISO 8601 and RFC 2822, plus how long ago it was.
How to use
- Paste a timestamp into the field. It starts with the current time.
- Check the detected unit. Switch to s, ms or µs if the number means something else.
- Copy the format you need: ISO 8601 for APIs, RFC 2822 for email headers.
- For the reverse, pick a date and time below, choose local time or UTC and copy the seconds or milliseconds.
Examples
1700000000 → 2023-11-14T22:13:20Z (Tue, 14 Nov 2023 22:13:20 +0000)
1700000000123 → 2023-11-14T22:13:20.123Z
0 → 1970-01-01T00:00:00Z
Frequently asked questions
How do I tell seconds from milliseconds?
Count the digits. Timestamps for current dates have 10 digits in seconds and 13 in milliseconds. In JavaScript Date.now() returns milliseconds; in Python time.time() and in PHP time() return seconds.
Does a Unix timestamp depend on the time zone?
No. It counts seconds from a fixed moment in UTC, so the same instant has the same number everywhere. The time zone only matters when you turn it into a calendar date.
What is the year 2038 problem?
Signed 32-bit integers can hold timestamps up to 2147483647, which is 2038-01-19T03:14:07Z. Systems that still store time in 32 bits will overflow after that. 64-bit timestamps do not have this limit.
Are leap seconds counted?
No. Unix time treats every day as exactly 86400 seconds, so leap seconds are not part of the count.