Unix timestamp

Converts Unix timestamp ↔ date (both directions). Seconds, milliseconds, local and UTC representation, weekday, relative time. Plus a reference of iconic timestamps.

01Converter02Milestones03About epoch04Related
01

Timestamp ↔ date converter

Timestamp
10 digits — seconds, 13 digits — milliseconds. Detected automatically.
Date (local)
YYYY-MM-DDTHH:MM:SS (browser datetime-local)
02

Famous Unix timestamps

click a row to load into the converter
Timestamp
Date
Event
0
01.01.1970 00:00:00 UTC
Unix Epoch — the starting point
1 000 000 000
09.09.2001 01:46:40 UTC
The first 'round' billion seconds
1 234 567 890
13.02.2009 23:31:30 UTC
Sequential digits 1–9
1 500 000 000
14.07.2017 02:40:00 UTC
One and a half billion seconds
2 000 000 000
18.05.2033 03:33:20 UTC
Two billion seconds
2 147 483 647
19.01.2038 03:14:07 UTC
Y2K38 — 32-bit integer overflow
03

About the Unix epoch

Unix epoch

POSIX
1970-01-01 00:00:00 UTC
The reference point — 1 January 1970, 00:00:00 UTC. A timestamp is the number of seconds since that moment. The format is timezone- and language-independent, which is why it was chosen as universal. It's used in all Unix-like systems, JavaScript, Python and virtually every API.

Seconds vs milliseconds

10 vs 13
1 741 434 000 = sec · ...000 = ms
The classic Unix timestamp is in seconds — a 10-digit number until year 2286. JavaScript uses milliseconds (Date.now()), 13 digits. Microseconds (16 digits) — in high-precision systems. Our converter detects the scale automatically by the length.

Y2K38 problem

2038-01-19
2 147 483 647 → int32 overflow
At 03:14:07 UTC on 19 January 2038 a 32-bit signed int will overflow, and systems storing timestamps in int32 will 'roll over' to 1901. Affects C, old Unix, embedded systems. Modern OSes and databases use 64-bit ints — enough for 292 billion years.

UTC — universal

Timezones
timestamp identical worldwide
The same timestamp in Moscow, Tokyo and New York denotes the same moment in time — only the local representation differs. That's why timestamps are ideal for logs and databases: no timezone juggling when comparing.
«» added to favorites