Unix Timestamp Converter

Convert Unix timestamps to dates and ISO dates to epoch time. Compare seconds and milliseconds, view UTC or IANA time zones, and retain millisecond precision.

Convert
0 characters
Result

Your result will appear here.

How to convert a Unix timestamp

  1. Choose seconds, milliseconds or an ISO date with a time zone as the input format.
  2. Enter the value. For a date, include Z or an offset, such as 2024-01-01T08:00:00+08:00.
  3. Choose an IANA time zone to view local time, then copy the result. The UTC instant and timestamp stay unchanged.

Working with Unix Timestamp Converter

Unix timestamps identify instants, not local wall-clock times. For date input, include Z or an explicit offset such as +11:00. The display time zone changes how the instant is shown, not the timestamp itself.

Timestamp example: the same instant in seconds, milliseconds and UTC

Input
1704067200
Result
ISO 8601 · UTC: 2024-01-01T00:00:00.000Z Unix seconds: 1704067200 Unix milliseconds: 1704067200000

Questions about Unix Timestamp Converter

Is my timestamp in seconds or milliseconds?

Check the system that produced it. Around today's dates, seconds commonly have 10 digits and milliseconds 13, but digit count is not a universal rule. Select the correct unit; 1704067200 seconds equals 1704067200000 milliseconds.

Why is the converted date several hours off?

A timestamp has no local time zone. UTC and local clock displays differ by their offset. Select a zone such as Europe/Paris to apply its date-specific rules, including daylight saving time; do not manually add the offset to the timestamp.

Can I convert a date back to a Unix timestamp?

Yes. Choose date input and use ISO 8601 with Z or an explicit offset. An ambiguous date without a zone is rejected instead of being guessed. The result includes Unix seconds and milliseconds.

Are negative and fractional timestamps supported?

Yes. Negative values represent instants before 1970-01-01T00:00:00Z. Seconds can have up to three meaningful decimal places; millisecond input must resolve to whole milliseconds. Finer precision is rejected, not silently rounded.

Are my files, tokens or text uploaded?

No. These tools process your input in your browser. The website serves the page and its code, but your input is not sent to a conversion server or saved in an account.

  • Cron Expression Parser

    Validate five- or six-field Cron expressions and list upcoming runs in an IANA time zone, including daylight-saving changes.

  • Cron Expression Generator

    Build a Cron expression from time fields or common presets, then preview its next scheduled times in your chosen zone.

  • JWT Decoder

    Read JWT headers and payloads, inspect expiry and activation times, and view claims without sending your token anywhere.

  • UUID & GUID Generator

    Generate random UUID v4 or time-ordered UUID v7 identifiers, individually or in batches.

Common tasks and examples

Explore all developer tools

Encoding & Files

Move between text, bytes, URLs and embedded images without changing your original data.

Data & Text Inspection

Read structured data, inspect tokens and understand exactly what changed.

Hashes, IDs & Schedules

Check file integrity, generate identifiers and make sense of times and recurring schedules.

Your input and files are processed on your device. Keep sensitive results out of shared clipboards and use a trusted device for private keys and tokens.