Convert Unix timestamps to human-readable dates and vice versa.
💡 Tip: Unix timestamp is the number of seconds since January 1, 1970 00:00:00 UTC. Click any timestamp to copy it!
Paste a Unix timestamp (seconds or milliseconds) into the input field. The converter automatically detects whether it is in seconds (10 digits) or milliseconds (13 digits) and converts it to a human-readable date.
Select a date and time from the date picker and the tool will convert it to a Unix timestamp in both seconds and milliseconds — ready to use in your code or database queries.
Copy the converted timestamp or date. Use it in SQL queries, API requests, log analysis, or anywhere you need to work with Unix time.
| Timestamp | Date (UTC) | Significance |
|---|---|---|
| 0 | Jan 1, 1970 00:00:00 | Unix epoch — the starting point of Unix time |
| 1000000000 | Sep 9, 2001 01:46:40 | Unix time hit 1 billion |
| 1234567890 | Feb 13, 2009 23:31:30 | Famous "1234567890" milestone |
| 1700000000 | Nov 14, 2023 22:13:20 | Recent reference point |
| 2000000000 | May 18, 2033 03:33:20 | Unix time will hit 2 billion |
| 2147483647 | Jan 19, 2038 03:14:07 | Maximum 32-bit signed integer — "Year 2038 problem" |
Math.floor(Date.now() / 1000) // seconds Date.now() // milliseconds
import time time.time() # seconds (float) int(time.time()) # seconds (int)
time(); // seconds microtime(true); // microseconds
UNIX_TIMESTAMP() -- current timestamp FROM_UNIXTIME(ts) -- convert to datetime
time.Now().Unix() // seconds time.Now().UnixMilli() // milliseconds
DateTimeOffset.UtcNow.ToUnixTimeSeconds() DateTimeOffset.UtcNow.ToUnixTimeMilliseconds()
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC — a point in time known as the Unix epoch. It is completely timezone-independent, which is why it is the preferred way to store and transmit time in software systems.
Unix timestamps are used everywhere in software: database records store created_at and updated_at as timestamps, API responses include timestamps for events, log files record timestamps for debugging, and JWT tokens use timestamps for expiry (exp) and issue time (iat).
The Year 2038 problem arises because many older systems store Unix timestamps as 32-bit signed integers, which can only hold values up to 2,147,483,647 — corresponding to January 19, 2038. Modern systems use 64-bit integers, which can represent dates billions of years in the future.
Common questions about Timestamp Converter