Time Converter

Convert Unix timestamps, date strings, and CF Absolute Time to ISO 8601, RFC 2822, UTC, local time, and more directly in your browser. Read more

Convert time formats in your browser

This time converter turns Unix timestamps (seconds or milliseconds), date strings, CF Absolute Time, or a date-time picker value into common display formats. Conversion runs locally in your browser.

Unix timestamps represent seconds or milliseconds since 1970-01-01T00:00:00.000Z. Apple CF Absolute Time counts seconds since 2001-01-01T00:00:00.000Z. Both are absolute and do not depend on the input time zone.

How to use

  1. Choose Input Source: Text or Date Time Picker.
  2. For text, select a Text Format, or leave Auto to detect numeric timestamps versus date strings.
  3. Set Input Time Zone for wall-clock values without an explicit time zone (picker values and date strings without an offset or zone).
  4. Set Output Time Zone for RFC and zoned display fields.
  5. Click Convert, or keep Auto Update enabled.

Text formats

  • Auto — numeric 10-digit values as seconds, 13-digit values as milliseconds; otherwise parse as a date string. Ambiguous digit lengths require an explicit Unix unit. Auto does not guess CF Absolute Time.
  • Unix Timestamp / Unix Timestamp (Milliseconds) — force seconds or milliseconds.
  • Date String — numeric dates, ISO-like strings, RFC-style dates, month-name dates, and common time zone forms. Date strings without an explicit time zone use the selected input time zone. Strings with Z, UTC, GMT, a numeric offset, a supported abbreviation, or an IANA time zone use that zone.
  • CF Absolute Time — seconds since 2001-01-01 UTC (fractional seconds allowed).

Date string parsing is intentionally strict enough to reject trailing junk and ambiguous numeric dates. Year-first numeric dates support leading zeros and long years. Non-year-first numeric dates are accepted only when DD/MM/YYYY and MM/DD/YYYY produce the same result or only one valid result.

Supported time zone inputs include numeric offsets such as +0300, +03:00, UTC+3, GMT+3, RFC-style abbreviations such as EST and CST, common low-ambiguity abbreviations such as JST and KST, and IANA zones such as Asia/Taipei.

Output fields

Numeric values:

  • Input Time Zone (the zone used to interpret the input)
  • Unix Timestamp (Seconds / Milliseconds)
  • CF Absolute Time

Formatted standards (email and SQL use the output time zone; HTTP dates are always GMT):

  • ISO 8601 / RFC 3339 — 2026-07-25T13:45:30+08:00
  • Email (RFC 5322 / RFC 2822) — Sat, 25 Jul 2026 13:45:30 +0800
  • Email (RFC 822) — Sat, 25 Jul 26 13:45:30 +0800
  • HTTP (RFC 9110 / RFC 7231 / RFC 1123) — Sat, 25 Jul 2026 05:45:30 GMT
  • HTTP (RFC 850) — Saturday, 25-Jul-26 05:45:30 GMT
  • HTTP (ANSI C asctime) — Sat Jul 25 05:45:30 2026
  • SQL (ISO 9075) — 2026-07-25 13:45:30
  • UTC Time — fixed YYYY-MM-DD HH:mm:ss UTC
  • Local Time — browser local wall time, with IANA zone name when available (e.g. Local Time (Asia/Taipei))

If you only need epoch values, use Auto or select Unix Timestamp / Unix Timestamp (Milliseconds) directly.

Time converter FAQ

Is my input uploaded?

No. Parsing and formatting run in your browser.

Why did Auto reject my number?

Values that are not clearly 10-digit seconds or 13-digit milliseconds are treated as ambiguous. Choose Unix Timestamp or Unix Timestamp (Milliseconds).

Input
Output
Share Link
Settings
Convert