Timestamp Converter

Convert Unix timestamps to readable dates and convert dates back to Unix time. Paste a timestamp in seconds or milliseconds to see UTC time, local time, ISO 8601, relative time, day of week, Unix seconds and Unix milliseconds. Switch to Date → Timestamp mode to parse a date string and generate timestamp values for APIs, databases, logs and debugging.

Input
0 chars · 0 bytes
Try:
Result
✓ Converts timestamps and dates entirely in the browser ✓ Shows UTC, local, ISO 8601, relative time and more ✓ Client-side processing only
Examples
Unix Epoch
Input 0
Output 1970-01-01T00:00:00.000Z

Every Unix timestamp counts seconds from this moment — midnight UTC on 1 January 1970.

JavaScript milliseconds
Input 1700000000000
Output 2023-11-14T22:13:20.000Z

JavaScript's Date.now() returns milliseconds. The tool auto-detects 13-digit timestamps as milliseconds.

Date to timestamp
Input 2024-01-01T00:00:00Z
Output 1704067200

Paste an ISO 8601 date to get the Unix timestamp in seconds — useful when building API calls or database queries.

Year 2038 limit
Input 2147483647
Output 2038-01-19T03:14:07.000Z

The maximum value of a 32-bit signed integer. After this moment, systems that store timestamps as 32-bit integers will overflow (Y2K38 problem).

What is a Unix timestamp?

A Unix timestamp, also called Unix time, POSIX time or epoch time, is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970. It represents one exact instant and does not store a timezone, which makes it practical for databases, APIs, logs, schedulers, tokens and cross-system integrations.

Millisecond timestamps follow the same epoch but count milliseconds instead of seconds, so the value is 1000 times larger. JavaScript's Date.now(), Java's System.currentTimeMillis() and many event streams return millisecond timestamps by default.

Seconds vs milliseconds

The converter can auto-detect whether an input timestamp is in seconds or milliseconds. Numbers with an absolute value above 100 billion (10¹¹) are treated as milliseconds; smaller numbers are treated as seconds. Use the Input unit setting to force seconds or milliseconds when you already know the source format.

A quick rule of thumb: a 10-digit value is usually Unix time in seconds, while a 13-digit value is usually Unix time in milliseconds. The result table always shows both Unix seconds and Unix milliseconds, so you can copy the exact unit your code or database expects.

What the converter shows

In Timestamp → Date mode, the result includes UTC time, your browser's local time, ISO 8601, relative time, day of week, Unix seconds and Unix milliseconds. Each row has its own copy button, which is useful when comparing log entries, API payloads, JWT claims, cron schedules or database records.

In Date → Timestamp mode, the converter parses the date string in your browser and returns Unix time in seconds and milliseconds, plus normalized ISO, UTC and local representations for verification.

UTC, local time and ISO 8601

Unix timestamps are based on UTC, but humans often read dates in local time. This tool displays both: UTC for server-side consistency and local time for the timezone configured in your browser. That makes it easier to check whether an event happened at the expected moment for a user, server or integration partner.

ISO 8601 output, such as 2024-01-15T12:00:00.000Z, is a portable date-time format commonly used in JSON APIs, logs and configuration files. When converting a date back to a timestamp, prefer ISO 8601 with an explicit timezone when accuracy matters.

Common use cases

Use this timestamp converter when debugging application logs, checking API response times, reading database fields, validating JWT exp, iat and nbf claims, preparing test data, converting webhook event times or comparing timestamps from different programming languages.

The conversion runs in your browser, so pasted values are not sent to the server by the converter logic. This is convenient for routine development work, troubleshooting and quick timestamp lookups.

FAQ

Click the <strong>Now</strong> button to instantly fill the input with the current time. In Timestamp → Date mode it inserts the current Unix timestamp in seconds; in Date → Timestamp mode it inserts the current date-time string. You can also use <code>date +%s</code> on Linux/macOS, <code>Get-Date -UFormat %s</code> in PowerShell, <code>Math.floor(Date.now() / 1000)</code> for JavaScript seconds, or <code>Date.now()</code> for JavaScript milliseconds.

The converter accepts date strings that the browser's JavaScript engine can parse, including ISO 8601 (<code>2024-01-15T12:00:00Z</code>), simple dates (<code>2024-01-15</code>), date-time without timezone (<code>2024-01-15 12:00:00</code>) and some locale-specific formats. For reliable results across browsers, use ISO 8601 with an explicit timezone, such as <code>2024-01-15T12:00:00+03:00</code> or <code>2024-01-15T09:00:00Z</code>.

The Year 2038 problem (Y2K38) affects systems that store Unix timestamps as a 32-bit signed integer. Such systems can only represent times up to 03:14:07 UTC on 19 January 2038 (timestamp 2147483647). After that the value overflows and wraps to a large negative number, representing a date in 1901. Modern 64-bit systems are not affected, as they can represent dates billions of years into the future.

A Unix timestamp represents an instant counted from the Unix epoch in UTC. It does not contain a timezone or locale. Local time is only a display choice: the same timestamp can appear as different clock times in different timezones, but it still points to the same moment.

Current Unix timestamps in seconds are usually 10 digits, while millisecond timestamps are usually 13 digits. This tool auto-detects values above 100 billion (10¹¹) as milliseconds. If you are working with legacy data, future dates, negative timestamps or a known API format, use the <strong>Input unit</strong> setting to choose seconds or milliseconds manually.

UTC is the global reference time used by Unix timestamps. Local time is calculated from the timezone settings in your browser or operating system, including daylight saving time rules where they apply. The UTC and local rows can therefore show different clock times for the same timestamp.

Yes. Dates before 00:00:00 UTC on 1 January 1970 are represented by negative Unix timestamps. Support for very old or very far future dates depends on the browser's JavaScript date range, but ordinary pre-1970 dates work in modern browsers.

The timestamp conversion logic runs in your browser. Pasted timestamp and date values are processed locally by JavaScript, which is helpful when checking development logs, API payloads or token claims.
Related tools

Binary Converter Online

Convert text into 8-bit binary groups and decode binary bytes back into readable text.

ASCII Converter

Convert ASCII characters and numeric codes for protocol and parser workflows.

JWT Decoder Online

Decode JWT tokens in-browser and inspect header, payload, claims, and expiration data.