Timestamp to date
Enter a Unix timestamp and see the full date and time. The result is shown in your local timezone, in UTC, as an ISO 8601 string, and as a relative time like 2 hours ago.
1785508200ResultJul 31, 2026, 2:30 PM UTCConvert a Unix timestamp to a readable date, and a date back to a timestamp. See the result in your local time, in UTC, and in any timezone, with both seconds and milliseconds. Everything runs in your browser, so your data stays on your device.
Epoch time, also called Unix time, is the number of seconds since midnight UTC on January 1, 1970. That starting point is known as the epoch. Storing a moment as one plain number keeps it simple to compare, sort, and pass between systems, which is why it turns up in server logs, databases, tokens, and APIs. This tool turns that number into a date you can read, and turns a date back into a timestamp.
Enter a Unix timestamp and see the full date and time. The result is shown in your local timezone, in UTC, as an ISO 8601 string, and as a relative time like 2 hours ago.
1785508200ResultJul 31, 2026, 2:30 PM UTCPick a date and time and get the matching Unix timestamp in both seconds and milliseconds. The date is read in whichever timezone you choose.
2026-07-31 14:30Result1785508200The tool reads your number as seconds, milliseconds, microseconds, or nanoseconds based on how many digits it has, so you can paste any of them without converting first.
1785508200000Resultread as millisecondsChoose any timezone to read and display dates in. It defaults to your own timezone, and Daylight Saving Time is handled for you.
America/New_YorkResultshifts with DSTNot every timestamp counts the same unit. The most common ones count seconds, but many systems count milliseconds, and a few count even smaller units. You can usually tell them apart by how many digits they have. This tool checks the digit count for you and reads the number the right way.
| Unit | Digits today | Example |
|---|---|---|
| Seconds | 10 | 1785508200 |
| Milliseconds | 13 | 1785508200000 |
| Microseconds | 16 | 1785508200000000 |
| Nanoseconds | 19 | 1785508200000000000 |
Seconds timestamps are the classic Unix format. Milliseconds are common in JavaScript and many web APIs, since that is what Date.now returns. The result always shows both seconds and milliseconds, so you can copy the one your code expects.
Each of these returns the current time in seconds since the epoch:
| Language | Code |
|---|---|
| JavaScript | Math.floor(Date.now() / 1000) |
| Python | int(time.time()) |
| PHP | time() |
| Java | Instant.now().getEpochSecond() |
| C# | DateTimeOffset.UtcNow.ToUnixTimeSeconds() |
| Go | time.Now().Unix() |
| MySQL | UNIX_TIMESTAMP() |
| PostgreSQL | EXTRACT(EPOCH FROM NOW()) |
| Mac and Linux terminal | date +%s |
To turn a timestamp back into a date in the terminal, use date -d @1700000000 on Linux or date -r 1700000000 on a Mac. In JavaScript, multiply by 1000 first: new Date(1700000000 * 1000).
| Timestamp | Date and time (UTC) |
|---|---|
| 0 | 1 January 1970, 00:00:00 (the epoch) |
| 1,000,000,000 | 9 September 2001, 01:46:40 |
| 1,700,000,000 | 14 November 2023, 22:13:20 |
| 2,000,000,000 | 18 May 2033, 03:33:20 |
| 2,147,483,647 | 19 January 2038, 03:14:07 |
The last one is the largest number a signed 32 bit integer can hold. Older systems that store time that way will overflow one second later and jump back to 1901. This is known as the year 2038 problem. Most modern systems now use 64 bit timestamps, which will not run out for billions of years, but old databases, file formats, and embedded devices can still be affected.
Timestamps show up any time a system needs to record when something happened. Here are the most common reasons people convert them: