Paste a Unix timestamp to get the date, or type a date to get epoch time. Seconds and milliseconds are detected for you, you see the moment in ten time zones, and Batch mode converts every timestamp in a log. It runs in your browser.
Free Unix timestamp converter. Paste a timestamp to get ISO 8601, RFC 2822, local and relative time plus ten time zones, or type a date to get Unix seconds and milliseconds. Batch mode converts every 10-digit and 13-digit timestamp in pasted logs. Runs in the browser.
Seconds, milliseconds, microseconds and nanoseconds are told apart by length. Dates can be ISO 8601 like 2026-09-26T14:30:00Z, an offset like +02:00, or RFC 2822.
The date shows up here
Type a timestamp or a date, or .
Was this tool helpful?
Each snippet gets the current time in seconds, then turns 1790000000 back into a UTC date.
Math.floor(Date.now() / 1000) new Date(1790000000 * 1000).toISOString()
JavaScript. Date.now() is in milliseconds, so divide by 1000.
import time, datetime int(time.time()) datetime.datetime.fromtimestamp(1790000000, datetime.timezone.utc)
Python. time.time() returns a float in seconds.
time.Now().Unix() time.Unix(1790000000, 0).UTC()
Go. UnixMilli() and UnixNano() give the other units.
SELECT extract(epoch FROM now())::bigint; SELECT to_timestamp(1790000000); SELECT UNIX_TIMESTAMP(); SELECT FROM_UNIXTIME(1790000000);
SQL. PostgreSQL first, then MySQL.
date +%s date -u -d @1790000000 date -u -r 1790000000
Bash. -d @ on Linux (GNU date), -r on macOS.
A current timestamp with 10 digits is in seconds and one with 13 is in milliseconds. Here is the same instant in all four units, and where each one turns up.
| Digits | Same instant | Where you see it | |
|---|---|---|---|
| Seconds | 10 | 1790000000 | JWT exp and iat, date +%s, Go Unix() |
| Milliseconds | 13 | 1790000000000 | JavaScript Date.now(), Java currentTimeMillis() |
| Microseconds | 16 | 1790000000000000 | Go UnixMicro(), BigQuery UNIX_MICROS |
| Nanoseconds | 19 | 1790000000000000000 | Python time.time_ns(), Go UnixNano() |
10, 13, 16 or 19 digits are read as seconds, milliseconds, microseconds or nanoseconds. Dates can be ISO 8601 or RFC 2822.
ISO 8601, RFC 2822, your local time, how long ago it was, and the clock time in ten cities.
Paste log lines or drop a .log file. Every timestamp gets its date in brackets, ready to copy or download.
A Unix timestamp is the number of seconds since 00:00:00 UTC on January 1, 1970, a moment called the Unix epoch. 1790000000 is September 21, 2026 at 14:13:20 UTC. APIs, databases, JWT tokens and log files use it because it's one number with no time zone, so it sorts and compares cleanly.
Paste the timestamp into the converter. You get the date in ISO 8601, RFC 2822, your own time zone and ten cities around the world, plus how long ago it was. Every line has a copy button. The unit is detected from the length of the number, and everything runs in your browser.
Count the digits. A current timestamp in seconds has 10 digits, in milliseconds 13, in microseconds 16 and in nanoseconds 19. The converter reads the length and picks the unit for you, and says which one it used. If a date lands in 1970 or thousands of years ahead, the unit is wrong.
Type a date like 2026-09-26 14:30 or pick one with the date picker. The converter shows the Unix time in seconds and milliseconds. Dates without a time zone are read as your local time; switch on Read dates as UTC to treat them as UTC. A Z or an offset like +02:00 in the date always wins.
Yes. Switch to Batch and paste log lines, JSON or a plain list, or drop a .log or .txt file. Every 10-digit and 13-digit timestamp gets its date written next to it in brackets, in UTC or your local time. Copy the result or download it as a .txt file.
No. A Unix timestamp always counts from the epoch in UTC, so the same number means the same instant everywhere. Time zones only come in when you display it. That's why the converter shows one timestamp as a local time, as UTC and as the clock time in cities from Los Angeles to Sydney.
Systems that store Unix time as a signed 32-bit integer run out of room at 03:14:07 UTC on January 19, 2038, when the count passes 2,147,483,647 and wraps to a negative number. Most modern systems use 64-bit time and are safe. Paste 2147483647 into the converter to see the last moment.
In JavaScript use Math.floor(Date.now() / 1000). In Python use int(time.time()). In Go use time.Now().Unix(). In Bash run date +%s. In PostgreSQL use extract(epoch from now()), and in MySQL use UNIX_TIMESTAMP(). The live clock at the top of this page shows the current value and copies it in one click.
Everything from model picks to CSV converters, with no account needed.