Skip to content

Unix Time Now

The current Unix timestamp — seconds elapsed since 1970-01-01 00:00:00 UTC. Paste any timestamp or date below to convert it; seconds, milliseconds, microseconds and nanoseconds are detected automatically.

1792683654
ms 1792683654000 UTC 2026-10-22T15:40:54Z

Timestamp or date converter

Date → Unix timestamp

Batch convert

One timestamp or date per line — log lines are fine, the first number or date on each line is used.

InputUnitUTC (ISO 8601)Relative

Start and end timestamps

Handy for database queries — the first and last second of the current period, in your time zone and in UTC.

PeriodStart (local)End (local)Start (UTC)End (UTC)

Notable Unix timestamps

TimestampDate and time (UTC)Why it matters
01970-01-01T00:00:00ZThe Unix epoch
10000000002001-09-09T01:46:40ZFirst 10-digit timestamp (the “billennium”)
12345678902009-02-13T23:31:30ZCelebrated by developers worldwide
15000000002017-07-14T02:40:00Z1.5 billion seconds
17000000002023-11-14T22:13:20Z1.7 billion seconds
20000000002033-05-18T03:33:20Z2 billion seconds
21474836472038-01-19T03:14:07ZLargest signed 32-bit value — the Year 2038 problem
42949672952106-02-07T06:28:15ZLargest unsigned 32-bit value
-21474836481901-12-13T20:45:52ZSmallest signed 32-bit value

The next round-number milestone, 1,800,000,000, falls on 2027-01-15T08:00:00Z.

What is Unix time?

Unix time (also called POSIX time or epoch time) counts the seconds since the Unix epoch, 00:00:00 UTC on 1 January 1970. It ignores leap seconds — every day is exactly 86,400 seconds — so a timestamp maps to one UTC instant without needing a time zone or calendar. That is why databases, APIs and log files use it.

Seconds, milliseconds, microseconds or nanoseconds?

Present-day timestamps have 10 digits in seconds (Unix, PHP, Python's int(time.time())), 13 in milliseconds (JavaScript Date.now(), Java System.currentTimeMillis()), 16 in microseconds (PostgreSQL internals, many tracing tools) and 19 in nanoseconds (Go UnixNano(), InfluxDB). The converter uses the digit count to pick the unit.

The Year 2038 problem

Systems that store Unix time in a signed 32-bit integer overflow after 2,147,483,647 — at 03:14:07 UTC on 19 January 2038 — and wrap around to 13 December 1901. Modern 64-bit systems are not affected, but embedded devices and old file formats still are.

Get and convert Unix time in code

LanguageCurrent timestamp (s)Timestamp → date
JavaScriptMath.floor(Date.now() / 1000)new Date(ts * 1000).toISOString()
Pythonimport time; int(time.time())datetime.fromtimestamp(ts, tz=timezone.utc)
PHPtime()gmdate('c', $ts)
Gotime.Now().Unix()time.Unix(ts, 0).UTC()
JavaInstant.now().getEpochSecond()Instant.ofEpochSecond(ts)
C#DateTimeOffset.UtcNow.ToUnixTimeSeconds()DateTimeOffset.FromUnixTimeSeconds(ts)
RubyTime.now.to_iTime.at(ts).utc
RustSystemTime::now().duration_since(UNIX_EPOCH)?.as_secs()UNIX_EPOCH + Duration::from_secs(ts)
MySQLSELECT UNIX_TIMESTAMP();SELECT FROM_UNIXTIME(ts);
PostgreSQLSELECT extract(epoch FROM now())::bigint;SELECT to_timestamp(ts);
SQLiteSELECT strftime('%s', 'now');SELECT datetime(ts, 'unixepoch');
Shell (GNU / macOS)date +%sdate -d @ts / date -r ts

More date math — durations, business days, adding time — is in the time calculator. ISO week numbers are on the week number page.