Unix Timestamp Converter
A Unix timestamp converter: see the current epoch time, turn a timestamp into a readable date, or a date into a timestamp.
Current Unix timestamp
Seconds
…
Milliseconds
…
Timestamp to date
- Unitdetected
- seconds
- ISO 8601UTC
- …
- UTC
- …
- Local
- …
- Relative
- …
- Seconds
- …
- Milliseconds
- …
Date to timestamp
YYYY-MM-DD HH:MM:SS — add Z or +02:00 for an explicit offset
- SecondsUnix timestamp
- …
- MillisecondsJavaScript Date
- …
- ISO 8601UTC
- …
How to convert a Unix timestamp
- Paste a timestamp into Timestamp to date. The unit — seconds, milliseconds, microseconds or nanoseconds — is detected from its length.
- Read the date in UTC, in your time zone, as ISO 8601 and relative to now.
- To go the other way, type a date such as
2026-01-01 09:30into Date to timestamp and pick your time zone or UTC.
Seconds, milliseconds or microseconds?
Different systems count in different units, which is the most common reason a converted date lands in 1970 or the year 50,000. The number of digits tells you which one you have:
1760436000 10 digits seconds Unix, PHP, Python, JWT exp
1760436000000 13 digits milliseconds JavaScript Date.now(), Java
1760436000000000 16 digits microseconds PostgreSQL internals, some APIs
1760436000000000000 19 digits nanoseconds Go UnixNano(), InfluxDBNotable Unix timestamps
| Moment | Timestamp | UTC (ISO 8601) |
|---|---|---|
| Unix epoch | 0 | 1970-01-01T00:00:00Z |
| 1 billion seconds | 1000000000 | 2001-09-09T01:46:40Z |
| Start of 2026 | 1767225600 | 2026-01-01T00:00:00Z |
| Start of 2030 | 1893456000 | 2030-01-01T00:00:00Z |
| 32-bit overflow (2038 problem) | 2147483647 | 2038-01-19T03:14:07Z |
Unix timestamps in code
Math.floor(Date.now() / 1000); // now, in seconds
new Date(1760436000 * 1000).toISOString(); // "2025-10-14T10:00:00.000Z"
Date.parse("2026-01-01T00:00:00Z") / 1000; // 1767225600import time, datetime
int(time.time())
datetime.datetime.fromtimestamp(1760436000, datetime.timezone.utc)Related developer tools
The exp, iat and nbf claims of a token are Unix timestamps — the JWT decoder converts them for you. Timestamps in query strings show up in the URL decoder, and time-ordered IDs come from the UUID v7 generator.
Frequently asked questions
- What is a Unix timestamp?
- The number of seconds since 1 January 1970, 00:00:00 UTC, also called epoch time or POSIX time. It is the same everywhere in the world at a given moment, which makes it ideal for storing and comparing times.
- Is my timestamp in seconds or milliseconds?
- Count the digits. Current timestamps have 10 digits in seconds (Unix, PHP, Python time.time) and 13 in milliseconds (JavaScript Date.now, Java). 16 digits are microseconds and 19 nanoseconds. The converter detects the unit automatically, and you can override it.
- Why does the local time differ from UTC?
- The timestamp is the same moment everywhere; only the way it is displayed changes. UTC shows the time in London without daylight saving, and Local uses the time zone of your device, including daylight saving time.
- What happens in 2038?
- Systems that store timestamps as signed 32-bit integers overflow on 19 January 2038 at 03:14:07 UTC (timestamp 2147483647). Modern systems use 64-bit numbers, which last for billions of years. This converter handles dates far beyond 2038.
- How do I get the current timestamp in code?
- JavaScript: Math.floor(Date.now() / 1000). Python: int(time.time()). PHP: time(). Shell: date +%s. SQL (PostgreSQL): extract(epoch from now()).