Time Zone Converter
Compare the time in UTC and cities around the world side by side, with a 24-hour timeline and daylight saving info.
Convert Unix epoch timestamps to human-readable dates and dates back to timestamps, in UTC or any time zone. Free, private, and 100% in your browser.
··········
Dates without an offset (like 2024-05-11 10:30) are read in the selected time zone.
Logs, databases, APIs, and JWTs store time as Unix timestamps because they are compact and unambiguous. Reading them is another story. Paste a timestamp to see exactly which date and time it represents, in your time zone and in UTC.
JavaScript Math.floor(Date.now() / 1000)
Python int(time.time())
Go time.Now().Unix()
Java Instant.now().getEpochSecond()
PHP time()
Bash date +%s
PostgreSQL SELECT EXTRACT(EPOCH FROM now());
MySQL SELECT UNIX_TIMESTAMP();10 digits are seconds, 13 milliseconds, 16 microseconds, and 19 nanoseconds. You can also pick the unit yourself.
Paste a timestamp to get the date, or paste a date (ISO 8601, RFC 2822, or 2024-05-11 10:30) to get the timestamp.
Show results in your local zone, UTC, or any IANA zone such as America/New_York, with the correct daylight saving offset.
ISO 8601 with offset, RFC 2822 / HTTP date, seconds, milliseconds, microseconds, nanoseconds, ISO week, day of year, and Excel serial date.
Convert up to 500 timestamps from logs at once and copy the results as tab-separated text.
Large values are handled with BigInt, so 19-digit nanosecond timestamps keep every digit.
A Unix timestamp (epoch time, POSIX time) is the number of seconds since January 1, 1970 at 00:00:00 UTC, not counting leap seconds. It is the same everywhere in the world, which makes it ideal for storing and comparing times.
Count the digits. Current timestamps in seconds have 10 digits (for example 1715423000), in milliseconds 13 digits (1715423000000), in microseconds 16, and in nanoseconds 19. JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds; most Unix tools and Python's time.time() use seconds.
None: a timestamp always refers to a moment in UTC. Only its display depends on a time zone. That is why the same timestamp shows different clock times in different zones.
Systems that store Unix time as a signed 32-bit integer overflow at 2147483647, which is January 19, 2038 at 03:14:07 UTC. After that, the value wraps to a negative number (1901). Use 64-bit integers to avoid it.
A date such as 2024-05-11 10:30:00 is read as a wall-clock time in the time zone you select. Dates with Z or an offset like +02:00 are exact instants and ignore the selection.
Compare the time in UTC and cities around the world side by side, with a 24-hour timeline and daylight saving info.
Convert numbers between binary, octal, decimal, and hexadecimal instantly, with two's complement and a bit editor.
Beautify, minify, and validate JSON instantly with exact line and column error reporting.
Compare two JSON documents side by side and see every added, removed, and changed value.