Convert between Unix timestamps and human-readable dates
Current Unix Timestamp
Thu, 30 Jul 2026 03:49:17 GMT
Accepts seconds or milliseconds (auto-detected)
The Timestamp Converter turns Unix epoch values into human-readable dates and back again. Paste a raw epoch number (in seconds, milliseconds, microseconds, or nanoseconds) to see the equivalent calendar date and time in both UTC and your local browser timezone, or enter a date to get the epoch integer that databases, logs, and APIs expect.
It is built for developers, sysadmins, and data engineers who run into bare numbers like 1753142400 in log files, JSON payloads, JWT exp/iat claims, database columns, and API responses. Instead of guessing whether a value is seconds or milliseconds, the tool detects the likely unit by digit length and shows the resulting date immediately.
A Unix timestamp counts the number of seconds elapsed since the Unix epoch, midnight UTC on 1 January 1970 (1970-01-01T00:00:00Z), ignoring leap seconds. Because it is a single integer in UTC, it is unambiguous across timezones, which is why it is the default time representation in Linux, most databases, and network protocols. Converting seconds to a date is simply: add the seconds to the epoch; converting back subtracts the epoch from the target date.
The main source of confusion is the unit. JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds (13 digits today), while C's time() and PostgreSQL's extract(epoch) return seconds (10 digits). This tool inspects the number of digits to guess the unit: a value around 1.75 billion is seconds, around 1.75 trillion is milliseconds. Note the classic 32-bit signed limit: values stored in a signed 32-bit integer overflow at 2147483647 seconds, which is 2038-01-19T03:14:07Z, the well-known Year 2038 problem. Everything runs on 64-bit math in the browser, so dates far beyond 2038 convert correctly.
Yes, it is completely free with no sign-up. All conversion happens locally in your browser using JavaScript, so your timestamps and dates are never uploaded to a server.
Count the digits. A present-day timestamp in seconds has 10 digits (around 1.7 billion), while milliseconds has 13 digits (around 1.7 trillion). The tool auto-detects this, but you can override the unit if needed.
It shows every result in two forms: UTC in ISO 8601 format, and your local timezone as detected from your browser and operating system settings. The stored epoch value itself is always UTC-based.
Yes. Some systems store timestamps in microseconds (16 digits) or nanoseconds (19 digits), common in high-resolution logging and databases. The tool recognizes these lengths and scales them down to a date accordingly.
Systems that store the timestamp in a signed 32-bit integer can only reach 2147483647 seconds, which is 03:14:07 UTC on 19 January 2038. Past that they overflow. This tool uses 64-bit math, so it converts dates well beyond 2038 without issue.
You are almost certainly reading milliseconds as seconds. Dividing a 13-digit millisecond value by 1000 gives the correct 10-digit seconds value. Switch the input unit to milliseconds and the date will look correct.
No. Unix time deliberately ignores leap seconds and assumes every day is exactly 86400 seconds, so its arithmetic stays simple. This tool follows the same standard convention.