🖥️ Unix Timestamp Converter
Convert Unix epoch timestamps (seconds or milliseconds) to human-readable UTC dates, and dates back to timestamps.
Quick answer: A Unix timestamp counts seconds since 00:00:00 UTC on January 1, 1970. Timestamp 1700000000 is Tuesday, November 14, 2023 at 22:13:20 UTC (2023-11-14T22:13:20.000Z), and 1700000000000 in milliseconds is the same moment.
Updated · Free · No sign-up · Works on any device
Unix Timestamp Converter inputs
Result
Timestamp read as the current time
Sunday, October 11, 2026, 07:05:39 UTC
| ISO 8601 | 2026-10-11T07:05:39.341Z |
| UTC string | Sun, 11 Oct 2026 07:05:39 GMT |
| Unix seconds | 1791702339 |
| Unix milliseconds | 1791702339341 |
- Relative to now
- now
- Day of the week
- Sunday
What is Unix time?
Unix time (also called epoch or POSIX time) is the number of seconds that have elapsed since the Unix epoch, 00:00:00 UTC on Thursday, January 1, 1970. It is used by databases, APIs, log files and programming languages because a single integer is easy to store, sort and compare.
Date = 1970-01-01T00:00:00Z + timestamp seconds · Days = ⌊timestamp ÷ 86,400⌋
Worked example
1,700,000,000 ÷ 86,400 = 19,675 whole days with 80,000 seconds left over. Day 19,675 after the epoch is November 14, 2023, and 80,000 seconds is 22 h 13 min 20 s – so the timestamp is 2023-11-14T22:13:20Z, a Tuesday.
Notable timestamps
| Timestamp | Date (UTC) |
|---|---|
| 0 | 1970-01-01 00:00:00 |
| 1000000000 | 2001-09-09 01:46:40 |
| 1700000000 | 2023-11-14 22:13:20 |
| 2000000000 | 2033-05-18 03:33:20 |
| 2147483647 | 2038-01-19 03:14:07 (32-bit limit) |
Seconds or milliseconds?
Unix tools, PHP, Python and most databases work in whole seconds, giving 10-digit numbers today. JavaScript, Java and many web APIs use milliseconds, giving 13 digits. Mixing them up is the most common timestamp bug: reading milliseconds as seconds lands tens of thousands of years in the future, while reading seconds as milliseconds lands in January 1970. This converter checks the size of the number and picks the right unit automatically, and always shows both forms so you can copy whichever your system expects.
Time zones and ISO 8601
Results are shown in UTC. The ISO 8601 form ends in "Z" (Zulu time, meaning UTC), so it can be parsed unambiguously by any language. To show local time, add your zone's offset – for example UTC−5 for New York in winter.
Getting the current timestamp in code
- JavaScript:
Math.floor(Date.now() / 1000) - Python:
int(time.time()) - Shell:
date +%s - SQL (PostgreSQL):
extract(epoch from now())
Negative timestamps represent dates before 1970; for example −86400 is December 31, 1969.
Frequently asked questions
Is my timestamp in seconds or milliseconds?
Current timestamps have 10 digits in seconds (e.g. 1700000000) and 13 digits in milliseconds (1700000000000). The converter treats any value of 100 billion or more as milliseconds.
Are Unix timestamps affected by time zones?
No. A timestamp is the same everywhere at a given instant – it is always measured from midnight UTC on January 1, 1970. Only the way you display it changes with the time zone.
What is the year 2038 problem?
Systems that store timestamps as signed 32-bit integers overflow after 2147483647, which is 03:14:07 UTC on January 19, 2038. Modern 64-bit systems are not affected.
Do Unix timestamps include leap seconds?
No. Unix time assumes every day has exactly 86,400 seconds and ignores leap seconds, which keeps date maths simple.