Unix Timestamp
What is a Unix timestamp (epoch time)?
A Unix timestamp — also called Unix time, epoch time or POSIX time — is the number of seconds elapsed since January 1, 1970 at 00:00:00 UTC, a starting point called « the epoch ». It is simply a numeric value that represents a precise date and time.
It is the simplest way for a computer to represent a date and time: a single integer, identical everywhere in the world and independent of the time zone. The Unix timestamp is found in databases, log files, APIs, Linux systems and most programming languages (PHP, JavaScript, Python, Java, SQL…).
Important: a Unix timestamp is always counted in UTC (universal time, close to GMT). It is when displaying it that we translate it into a time zone to get a « human » date and time. The same number 1700000000 is 11:13 PM in Paris, 5:13 PM in New York or 7:13 AM the next day in Tokyo — the exact same instant, read at different local times. Converting a timestamp to a date, or a date to a timestamp, simply means choosing the display time zone.
Why use a Unix timestamp?
Representing a date and time as a simple number — the timestamp — has many advantages for developers, databases and computers:
Seconds or milliseconds?
Depending on the system, the timestamp is expressed in seconds or milliseconds.
Unix/Linux, PHP or MySQL systems usually use seconds (10 digits today, e.g. 1750166400). JavaScript and many web APIs use milliseconds (13 digits, e.g. 1750166400000).
No worries: this converter automatically detects the unit. If you paste 13 digits, it understands milliseconds; otherwise it reads seconds.
Some useful benchmarks
The Year 2038 problem: systems that store the timestamp in a 32-bit integer will not be able to count beyond January 19, 2038 at 03:14:07 UTC. Modern (64-bit) systems are not affected.