Skip to content

Unix time now

The current Unix timestamp in four units, live, with the same moment in ISO 8601.

UnitNowCopy
Seconds10 digits today––––––––––
Milliseconds13 digits–––––––––––––
Microseconds16 digits––––––––––––––––
Nanoseconds19 digits–––––––––––––––––––
ISO 8601, UTCthe same moment as a date and time––––-––-––T––:––:––.–––Z

This is this device’s clock, read once a second: as right as this device’s clock. It is read to the millisecond, so the microsecond and nanosecond rows end in zeros. Copy takes the reading at the moment you press it.

Seconds, milliseconds, microseconds or nanoseconds, told apart by the number of digits.

What the number is

Unix time counts from 1970-01-01T00:00:00Z and leaves out leap seconds, so every day is 86,400 seconds. It has no time zone: the same number is the same moment everywhere. The seconds count has 10 digits until the year 2286; milliseconds have 13, microseconds 16 and nanoseconds 19.

Whose clock

The page reads the clock of the device it is open on, so it is as right as that clock. A phone or computer that sets its time from the network is usually within a fraction of a second. Browsers read the clock to the millisecond, so the microsecond and nanosecond rows are that reading followed by zeros; nothing finer is made up.

Seconds or milliseconds, at a glance

The same moment, 2025-11-17T16:20:30.123Z, in each unit. Count the digits: a timestamp of today has 10 in seconds and three more for each finer unit. Reading one unit as another is the usual mistake: milliseconds read as seconds land tens of thousands of years ahead, and seconds read as milliseconds land in January 1970. Tell seconds from milliseconds goes through it step by step.

UnitDigitsValueWhere it is common
Seconds 10 1763396430 Unix tools, most APIs, databases, JWT claims
Milliseconds 13 1763396430123 JavaScript, Java, Kafka, analytics exports
Microseconds 16 1763396430123000 PostgreSQL internals, Python datetime, tracing
Nanoseconds 19 1763396430123000000 Go, InfluxDB, system clocks

Notable timestamps

SecondsFalls onKnown for
0 Thursday 1 January 1970, 00:00:00 UTC The epoch: where the count starts.
1,000,000,000 Sunday 9 September 2001, 01:46:40 UTC The first ten-digit second, “the billennium”.
1,234,567,890 Friday 13 February 2009, 23:31:30 UTC The digits one to nine and zero, in order.
2,000,000,000 Wednesday 18 May 2033, 03:33:20 UTC The next round billion.
2,147,483,647 Tuesday 19 January 2038, 03:14:07 UTC The last second a signed 32-bit counter can hold: the year 2038 problem.
4,294,967,295 Sunday 7 February 2106, 06:28:15 UTC The last second an unsigned 32-bit counter can hold.

The year 2038

Software that keeps Unix time in a signed 32-bit number can count no further than 2,147,483,647 seconds, which is Tuesday 19 January 2038, 03:14:07 UTC. One second later such a counter wraps around to a negative number and reads as December 1901. Systems that use 64 bits, which is most of what is built today, are not affected; old file formats, embedded devices and database columns declared as 32-bit integers are where it still matters.

Get the current Unix time in code

Each line gives whole seconds. For milliseconds most languages have a sibling call, such as Date.now() in JavaScript or date +%s%3N with GNU date.

WhereSeconds since 1970
Shell (Linux, macOS) date +%s
JavaScript Math.floor(Date.now() / 1000)
Python int(time.time())
PHP time()
Go time.Now().Unix()
Java Instant.now().getEpochSecond()
C# DateTimeOffset.UtcNow.ToUnixTimeSeconds()
Ruby Time.now.to_i
Rust SystemTime::now().duration_since(UNIX_EPOCH)?.as_secs()
PowerShell [DateTimeOffset]::UtcNow.ToUnixTimeSeconds()
PostgreSQL SELECT extract(epoch FROM now())::bigint;
MySQL SELECT UNIX_TIMESTAMP();

Other directions

To turn a timestamp into a date, or a date into a timestamp, in any time zone, use the converter; the field above opens it with your number. How Unix time works, its units and the year 2038 are in the Unix timestamp guide, and seconds or milliseconds tells the units apart.