UtilityPilot.Find a tool

Developer Tools

Unix Timestamp Converter

Convert a whole-number Unix timestamp to UTC, or convert an explicitly zoned date and time to epoch seconds and milliseconds. Choose the input units instead of relying on a guess.

Processed in your browserPrivacy details ↗

Whole seconds/milliseconds, or YYYY-MM-DDTHH:mm:ss[.SSS]Z / explicit offset

Adjust your options

No sign-up. No upload.

How to convert a Unix timestamp

  1. Choose Timestamp to date or Date to timestamp.
  2. For a timestamp, paste an integer and select seconds or milliseconds.
  3. For a date, use a value such as 2023-11-14T22:13:20Z or 2023-11-15T03:13:20+05:00.
  4. Select Convert timestamp. The result shows UTC, Unix seconds and Unix milliseconds together.
  5. Copy the JSON result or download timestamp.json.

The input-unit option applies only when the input is a timestamp. Date conversion always returns both units.

What Unix time represents

Unix time measures elapsed time from 1970-01-01T00:00:00Z using the conventional epoch representation that does not count leap seconds. The same instant can be written as seconds or milliseconds. A millisecond value is one thousand times the seconds value; mixing the units can produce a date near 1970 or far into the future.

A timestamp is an instant, not a local calendar label. Output is shown in UTC using ISO notation. The tool does not use your browser timezone to guess the meaning of a date without an offset. For a local appointment or a daylight-saving transition, establish the intended timezone and offset before conversion.

Seconds, milliseconds and offsets

Input

1700000000 seconds
1700000000000 milliseconds
2023-11-15T03:13:20+05:00

Result

UTC: 2023-11-14T22:13:20.000Z
Unix seconds: 1700000000
Unix milliseconds: 1700000000000

These three inputs identify the same instant when the correct mode and unit are selected. Timestamp zero is the epoch itself. Negative values represent instants before the epoch; negative one millisecond is 1969-12-31T23:59:59.999Z, with Unix seconds -0.001.

Validation and precision rules

Timestamp inputs must be whole decimal integers. They are read using BigInt before range checking, so a large value is not silently rounded on input. Milliseconds must fit the JavaScript Date range of plus or minus 8,640,000,000,000,000. Output seconds can have a fractional part when the instant is not a whole second. Both exported epoch values are decimal strings so even milliseconds near the supported range boundary retain every digit.

Date input uses a documented subset: a four-digit year, calendar date, T separator, hours/minutes/seconds, optional one-to-three millisecond digits, then Z or a numeric offset. Impossible dates such as February 30 are rejected instead of rolling into March. Leap-second values, 24:00, fractional precision finer than milliseconds and an unspecified -00:00 offset are not supported.

Common timestamp mistakes

Do not infer units only from the number of digits: older dates, negative values and small test fixtures can defeat that rule. Check the originating API’s specification. A database may also use microseconds or nanoseconds, which this interface does not accept as a separate unit.

A displayed date does not tell you whether a token or record is valid. The JWT Decoder can expose NumericDate claims, but neither decoding nor converting them verifies a signature or application policy. Use JSON Viewer to find the relevant timestamp field in a response. For numeral-system changes rather than date interpretation, use the Number Base Converter.

The converter provides no current-time clock, named-zone database, date arithmetic or calendar scheduling. These are separate tasks with different ambiguity rules.

Seconds, milliseconds and the supported range

The Unix epoch is 00:00:00 UTC on 1 January 1970. Seconds and milliseconds are the same instant at different scales: a ten-digit value is normally seconds and a thirteen-digit value is normally milliseconds, but the converter uses the unit you select rather than guessing from length. Enter whole numbers only; no separators or exponents.

Negative values represent instants before the epoch. The supported range is the range of a JavaScript Date, about ±8.64 × 1015 milliseconds, which is far wider than the 32-bit seconds range associated with the year 2038 problem. Values outside that range are rejected instead of being silently wrapped.

UTC output is not your local clock

The converter reports one instant in UTC and returns epoch values as decimal strings so large integers keep every digit. Whether that instant is Monday or Tuesday depends on the viewer timezone. A date input with an explicit offset is converted to the same instant; the tool does not assume the visitor timezone and does not guess a missing offset.

Leap seconds and the ambiguous 24:00 notation are not supported. Fractional seconds are accepted in date input only, not in numeric epoch input. For scheduling work, store the UTC instant and format it for display separately.

Processing and privacy

Unix Timestamp Converter performs date arithmetic locally; the timestamp and resulting date are not sent anywhere. Input stays in browser memory until you reset or leave the page. Copy and download run only when you choose them. No tool input is sent to a processing service. Website pages and scripts still make ordinary hosting requests; the privacy policy separates those from tool processing.

Frequently asked questions

Are Unix timestamps always seconds?

Many specifications use seconds, but APIs also use milliseconds or other units. Select the unit documented by the source.

Can I paste a date without a timezone?

No. Supply Z for UTC or an explicit numeric offset so the result does not depend on your browser timezone.

Does this handle leap seconds?

No. Seconds must be 00–59; the tool uses the conventional JavaScript/Unix epoch timeline.

Is a ten-digit number always seconds?

Usually, but the converter does not guess. Select seconds or milliseconds explicitly; the wrong unit produces a date thousands of years away.

Does the tool use my local timezone?

No. Numeric epochs are treated as UTC and date input requires Z or an explicit offset.

How this tool was checked

Unix Timestamp Converter was checked with seconds and milliseconds, fractional seconds, negative epochs, the Date range boundary and impossible calendar dates. See the testing method or report a failure.