Unix Timestamp Converter
Convert epoch Unix timestamps (seconds & milliseconds) to human-readable dates, or pick a date to generate corresponding Unix timestamps instantly.
Current Unix Epoch Time
0
Timestamp to Human Date
Auto-detects seconds (10 digits) vs milliseconds (13 digits).
Human Date to Timestamp
What is a Unix Timestamp?
The Unix epoch (or POSIX time) tracks time as the total number of elapsed seconds since 00:00:00 UTC on 1 January 1970 (excluding leap seconds). Because it represents a uniform scalar number independent of time zones, it is widely used across operating systems, database fields, and API payloads.
Common Code Examples
| Language / Environment | Get Seconds Epoch | Get Milliseconds Epoch |
|---|---|---|
| JavaScript / Node.js | Math.floor(Date.now() / 1000) |
Date.now() |
| C# / .NET | DateTimeOffset.UtcNow.ToUnixTimeSeconds() |
DateTimeOffset.UtcNow.ToUnixTimeMilliseconds() |
| Python | import time; int(time.time()) |
import time; int(time.time() * 1000) |
| SQL (PostgreSQL / MySQL) | SELECT EXTRACT(EPOCH FROM NOW()); |
SELECT UNIX_TIMESTAMP() * 1000; |
Frequently Asked Questions
On January 19, 2038, 32-bit signed integer timestamps will overflow, causing systems using 32-bit Unix time to wrap around to 1901. Modern systems mitigate this by using 64-bit integer values, which can store dates far into the future.
Timestamps with 10 digits (e.g. 1,700,000,000) are evaluated as seconds, while timestamps with 13 digits (e.g. 1,700,000,000,000) are treated as milliseconds.
Unix time is strictly relative to UTC and does not change based on timezones or daylight saving time. Leap seconds are ignored in standard Unix epoch counts, with every day treated as exactly 86,400 seconds.