Unix Timestamp — Free Online Converter

A Unix timestamp is a single integer counting seconds (or milliseconds in JavaScript) since 1970-01-01T00:00:00Z. Key caveats: leap seconds are not represented — POSIX assumes exactly 86400 seconds per day — and Date.now() in JavaScript returns milliseconds while time.time() in Python returns seconds. As of May 2026, the current timestamp is approximately 1746400000. For the full definition and history of Unix time, see the Unix time Wikipedia article. Paste any value below to convert instantly. Browser-based — nothing uploaded, all logic executes locally.

Understanding Unix Timestamps

Unix time counts the total number of seconds that have passed since January 1, 1970 at 00:00:00 UTC. This moment — called the Unix epoch — was chosen by the early Unix developers at Bell Labs as a convenient integer baseline near the time the system was being built.

Because Unix time is a single integer anchored to UTC, it is completely timezone-independent. The same value means the same instant everywhere on Earth. This makes it the standard format for storing timestamps in databases, log files, APIs, and distributed systems where nodes may be located in different regions.

Historically, Unix timestamps were stored as 32-bit signed integers. This limits their range to values between -2147483648 and 2147483647. The upper bound corresponds to January 19, 2038 at 03:14:07 UTC. On that date, any software still using a 32-bit timestamp will overflow and wrap to a negative number, rolling back to December 13, 1901 — an issue called the Year 2038 problem (also written Y2K38).

Modern systems have largely moved to 64-bit integers. The Linux kernel adopted the time64_t type in version 5.6 (released 2020), extending the representable range to hundreds of billions of years into the future. Most contemporary programming languages and databases store Unix time as a 64-bit value by default, so Y2K38 is primarily a concern for legacy embedded systems and older software still compiled for 32-bit targets.

Unix Timestamp Reference Table

Unix TimestampUTC DateSignificance
0Jan 1, 1970Unix epoch start
1000000000Sep 9, 2001One billion seconds
1234567890Feb 13, 20091234567890 milestone
1700000000Nov 15, 2023Recent reference point
2000000000May 18, 2033Two billion seconds
2147483647Jan 19, 203832-bit signed max — Y2K38 critical moment

Current Unix Timestamp

1777974230

Free — No Limits, No Signup

Convert

or

Results

UTC Time
Local Time
ISO 8601
Relative Time
Unix (seconds)
Unix (milliseconds)
Day of Week
Day of Year
Week Number
Is DST

Unix Timestamp in Different Systems

JavaScript

// Get current epoch in seconds
Math.floor(Date.now() / 1000)  // ~1746400000

// Convert epoch seconds to ISO date
new Date(1746400000 * 1000).toISOString()
// → "2026-05-05T00:26:40.000Z"

Python

import time
from datetime import datetime, timezone

# Get current epoch in seconds
int(time.time())  # ~1746400000

# Convert to UTC datetime
datetime.fromtimestamp(1746400000, tz=timezone.utc).isoformat()
# → '2026-05-05T00:26:40+00:00'

Linux / macOS Terminal

# Get the current Unix timestamp
date +%s

# Convert a Unix timestamp to a human-readable date
date -d @1746400000

Windows PowerShell

# Get the current Unix timestamp
[DateTimeOffset]::UtcNow.ToUnixTimeSeconds()

# Convert a Unix timestamp to a readable date
[DateTimeOffset]::FromUnixTimeSeconds(1746400000).UtcDateTime

MySQL

-- Get the current Unix timestamp (~1746400000)
SELECT UNIX_TIMESTAMP();

-- Convert a stored Unix timestamp to a readable date
SELECT FROM_UNIXTIME(1746400000);
-- → '2026-05-05 00:26:40'

PostgreSQL

-- Get the current Unix epoch seconds (~1746400000)
SELECT EXTRACT(EPOCH FROM NOW());

-- Convert a Unix timestamp to a timestamptz
SELECT TO_TIMESTAMP(1746400000);
-- → '2026-05-05 00:26:40+00'

REST APIs

Many REST APIs return Unix timestamps in response bodies or headers. Common fields include created_at, updated_at, and expires_at in epoch seconds. The HTTP Date header uses RFC 2822 format, but X-RateLimit-Reset commonly carries a Unix timestamp in seconds.

// Parse an epoch seconds field from a JSON API response
const createdAt = new Date(response.created_at * 1000).toISOString();

Frequently Asked Questions

Difference between epoch time and Unix timestamp?

They are the same thing. Both refer to the count of seconds since 1970-01-01T00:00:00Z. "Epoch" refers to the starting reference point, while "timestamp" refers to the current count. The terms are used interchangeably in documentation, APIs, and programming languages.

Are leap seconds counted in Unix timestamp?

No. POSIX Unix time assumes every day has exactly 86400 seconds and does not count leap seconds. As of 2026 there have been 27 leap seconds inserted since 1972, so Unix time is approximately 27 seconds behind true International Atomic Time (TAI).

Why does JavaScript use milliseconds and Python use seconds?

JavaScript's Date object was designed for UI responsiveness where millisecond precision matters. Python's time module follows the POSIX/C convention of returning seconds. To convert: Math.floor(Date.now() / 1000) in JS gives the same value as int(time.time()) in Python.

What is the max Unix timestamp for 64-bit systems?

A signed 64-bit integer maxes out at 9223372036854775807, corresponding to year 292,277,026,596 CE — effectively infinite for any practical purpose. Modern Linux (kernel 5.6+), macOS, and Windows all use 64-bit time_t and are unaffected by the Year 2038 problem.

How do I get Unix time in Windows PowerShell?

Use [DateTimeOffset]::UtcNow.ToUnixTimeSeconds() for seconds, or [DateTimeOffset]::UtcNow.ToUnixTimeMilliseconds() for milliseconds. To convert a stored value: [DateTimeOffset]::FromUnixTimeSeconds(1746400000).UtcDateTime returns 2026-05-05 00:26:40.

Related Tools