Timestamp Converter – Unix Timestamp to Date & Back
Convert Unix timestamps to human-readable dates and dates back to timestamps. Auto-detects seconds and milliseconds, supports UTC and local time, and shows relative time like "2 months ago". Free, private, and runs entirely in your browser.
Convert
Timestamp → DateResult
Waiting for input| Timestamp | Date (UTC) |
|---|
What is a Unix timestamp?
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It's a single integer that represents a specific moment in time, independent of timezone or calendar system — which is why virtually every programming language and database uses it internally.
For example, the timestamp 1706745600 corresponds to 1 February 2024 00:00:00 UTC. Negative timestamps represent dates before 1970, and the format continues to work for dates far into the future.
Everything runs locally in your browser. The values you enter never leave your device, there's no signup, and there are no usage limits.
Seconds vs milliseconds
Unix timestamps come in two common precisions, and getting them confused is one of the most frequent sources of bugs:
| Precision | Digits | Example | Typical use |
|---|---|---|---|
| Seconds | 10 | 1706745600 | Unix/POSIX time, most APIs, databases |
| Milliseconds | 13 | 1706745600000 | JavaScript Date.now(), Java System.currentTimeMillis() |
This converter auto-detects the precision based on the number of digits: 10 digits is treated as seconds, 13 digits as milliseconds. You can also force a specific precision if the auto-detection gets it wrong.
UTC vs local time
UTC (Coordinated Universal Time) is the global time standard that doesn't change with seasons or location. Local time is your device's timezone, which may be offset from UTC by a number of hours.
| Timezone | Offset from UTC | Example (1706745600) |
|---|---|---|
| UTC | ±0 | 2024-02-01 00:00:00 |
| IST (India) | +5:30 | 2024-02-01 05:30:00 |
| EST (New York) | −5:00 | 2024-01-31 19:00:00 |
| JST (Tokyo) | +9:00 | 2024-02-01 09:00:00 |
When you convert a timestamp, the underlying value is always the same — only the display changes. Switch between UTC and Local to see the same moment in different timezones.
The Year 2038 problem
Older systems that store Unix time as a signed 32-bit integer will overflow on 19 January 2038 at 03:14:07 UTC, because that's the largest value a 32-bit signed integer can represent as seconds. After that moment, the value wraps around to a negative number, and dates appear to jump back to 1901.
This converter uses JavaScript numbers, which are 64-bit IEEE 754 doubles. They can safely represent integer seconds well beyond the year 2038 — up to roughly 9,007,199,254,740,991, which is about 285 million years from now. So this tool is not affected by the Year 2038 problem.