Developer Tools

Timestamp Converter

Convert Unix seconds or milliseconds to UTC and browser local time, or turn an ISO date with a timezone into an exact Unix timestamp. Everything happens on your device.

Your content stays on your device Free, with no account
One instant. Clear representations. Local conversion · millisecond precision
Units are explicit; no guessing from the number of digits.
Seconds may include up to three decimal places. Negative timestamps are supported.

ISO dates require seconds and a timezone: 2024-01-01T00:00:00Z or 2024-01-01T05:30:00+05:30. Dates without a timezone are rejected to avoid guessing.

YOUR CONVERSION

Ready. Choose your direction and input unit.

Current time uses your device clock, not a network time service. Local time uses your browser’s timezone settings. Supported UTC years: 0000–9999. No leap seconds, microseconds or nanoseconds.

A FEW SIMPLE STEPS

How to use Timestamp Converter

  1. Choose Unix timestamp to date or ISO date to Unix timestamp. For Unix input, explicitly choose seconds or milliseconds.
  2. Enter your value, use the example or select Use current time. ISO dates require seconds and Z or an explicit numeric timezone offset.
  3. Select Convert time to review UTC ISO format, Unix seconds, Unix milliseconds and browser local time.
  4. Copy the conversion report or download it as a text file. Edits clear old results.
PRIVATE BY DESIGN

Why use this tool?

Your dates and timestamps never leave your browser. Conversion needs no uploads, external API, account or saved input history. Explicit units and required timezone offsets avoid silent guesses about what your input means.

Tool inputs stay in your browser. Only your theme preference is saved on this device.

A few things worth knowing

What is a Unix timestamp?

A Unix timestamp measures time relative to 1970-01-01T00:00:00Z. Seconds and milliseconds are different units for the same instant; one second is 1,000 milliseconds. Negative values represent instants before the epoch. This tool follows JavaScript Date’s Unix-style timeline without leap seconds.

Does the tool guess seconds or milliseconds?

No. Choose the input unit explicitly. Seconds allow up to three decimal places and milliseconds must be whole integers. The output always includes both units, preserving the instant to one millisecond. Scientific notation, grouping separators, microseconds and nanoseconds are not accepted.

Which ISO date format is accepted?

Use YYYY-MM-DDTHH:mm:ss with optional one to three fractional digits, followed by uppercase Z or a numeric ±HH:mm offset. For example, 2024-01-01T05:30:00+05:30. A timezone and seconds are required. Date-only strings, timezone names, ambiguous local times, leap seconds, 24:00 and impossible dates are rejected. Numeric offsets are limited to ±23:59; this does not validate an offset against a real-world timezone.

Are UTC and browser local time different instants?

They display the same instant using different timezone conventions. The UTC ISO result is deterministic. The local display depends on the browser’s timezone, locale and timezone database, including historical or daylight-saving rules. Its human-readable format can omit milliseconds; use UTC and Unix outputs for exact precision. Local time is a display, not an input format.

What range and calendar are supported?

Supported instants are UTC years 0000 through 9999, from 0000-01-01T00:00:00.000Z to 9999-12-31T23:59:59.999Z, using JavaScript’s proleptic Gregorian calendar. Year 0000 is accepted. Offsets that move an otherwise valid input outside that UTC range are rejected. This is a deliberate subset of JavaScript Date’s broader range.

Where does current time come from?

Use current time takes one snapshot of your device clock and converts it. It does not contact a time server or continuously tick, and an incorrect device clock gives an incorrect current time. Inputs and reports are not stored by this tool. Clear keeps your direction and unit settings.