WhatTimeIsIt.zone

Unix timestamp converter

Unix time (epoch time) is the number of seconds since 1 January 1970, 00:00:00 UTC. Convert a timestamp to a date or a date to a timestamp, in seconds or milliseconds.

Current Unix time

1794521274

In milliseconds: 1794521274000

Timestamp to date

Date to timestamp

Notable timestamps

The next round number, 1,800,000,000, is on Friday, January 15, 2027, 08:00:00 UTC, in

TimestampDate (UTC)
0The Unix epochThursday, January 1, 1970, 00:00:00 UTC
1,000,000,000One billion secondsSunday, September 9, 2001, 01:46:40 UTC
1,234,567,8901234567890: celebrated by programmers around the worldFriday, February 13, 2009, 23:31:30 UTC
1,500,000,000A round numberFriday, July 14, 2017, 02:40:00 UTC
1,700,000,000A round numberTuesday, November 14, 2023, 22:13:20 UTC
1,800,000,000A round numberFriday, January 15, 2027, 08:00:00 UTC
2,000,000,000Two billion secondsWednesday, May 18, 2033, 03:33:20 UTC
2,147,483,647The year 2038 problem: the end of signed 32-bit timeTuesday, January 19, 2038, 03:14:07 UTC
4,294,967,295The end of unsigned 32-bit timeSunday, February 7, 2106, 06:28:15 UTC

Current Unix time in code

JavaScript
Math.floor(Date.now() / 1000)
Python
import time int(time.time())
PHP
time()
Java
Instant.now().getEpochSecond()
C#
DateTimeOffset.UtcNow.ToUnixTimeSeconds()
Go
time.Now().Unix()
Rust
std::time::SystemTime::now() .duration_since(std::time::UNIX_EPOCH).unwrap().as_secs()
Ruby
Time.now.to_i
MySQL
SELECT UNIX_TIMESTAMP();
PostgreSQL
SELECT EXTRACT(EPOCH FROM now())::bigint;
Bash
date +%s
PowerShell
[DateTimeOffset]::UtcNow.ToUnixTimeSeconds()

Frequently asked questions

What is Unix time?

The number of seconds since 1 January 1970, 00:00:00 UTC (the Unix epoch), not counting leap seconds. It is the same everywhere in the world, whatever the time zone, which is why computers and databases store time this way.

What is the year 2038 problem?

Systems that store Unix time as a signed 32-bit number reach the largest value, 2,147,483,647, on 19 January 2038 at 03:14:07 UTC. One second later the number overflows and the date becomes 13 December 1901. Modern systems use 64-bit time and do not have this problem.

Does Unix time count leap seconds?

No: every day in Unix time is exactly 86,400 seconds. When a leap second happens, Unix time repeats a second (or smears it), so the difference between two Unix times can be a few seconds less than the real one.

Seconds or milliseconds?

Classic Unix time is in seconds (10 digits today), while JavaScript and Java use milliseconds (13 digits). The converter detects it: numbers from 100,000,000,000 up are read as milliseconds.