Timestamp Converter

1735689600 is 2025-01-01T00:00:00.000Z (1735689600 seconds since the Unix epoch).

How it works

• Interpreted the value as seconds.
• Rendered the instant in ISO-8601 and as Unix seconds/milliseconds.
• Compared it with the reference instant to produce a relative time.

• Unix time is UTC and ignores leap seconds.

Methodology

1. Interpret an integer or ISO 8601 instant as seconds or milliseconds and convert it to a UTC instant.
2. Auto-detect the unit from magnitude (1e12 or more is milliseconds); an explicit unit always overrides the heuristic.
3. Render the instant as RFC 3339 with an explicit UTC offset so the value is unambiguous.

Time model

• Time source: an explicit reference supplied by the visitor.
• Timezone: Epoch values are absolute instants. ISO-8601 is rendered in UTC (Z); the relative time is measured against the visitor's current instant when no reference is supplied.
• Locale: ISO-8601 numeric output only; no locale-specific date formatting or month names are used.
• Daylight saving: UTC has no daylight-saving transitions; the values are absolute instants and are DST-independent.
• Reference date: Optional reference instant. When omitted, the current instant is read from the visitor's environment at runtime; a supplied instant fixes the comparison.

Usage

1. Enter a numeric timestamp or an ISO-8601 instant.
2. Choose the unit or leave it on auto-detect.
3. Read the ISO-8601 value, Unix seconds/milliseconds, and relative time.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Epoch seconds at the 2025 boundary

{
  "value": 1735689600,
  "unit": "s",
  "reference": "2026-01-01T00:00:00.000Z"
}

ISO instant in the future

{
  "value": "2030-06-01T12:00:00.000Z",
  "reference": "2026-01-01T00:00:00.000Z"
}

Limitations

Seconds, milliseconds, and the 1e12 line

Unix seconds for current dates are around 1.7e9 and milliseconds around 1.7e12. Auto-detect uses that gap: a magnitude of 1e12 or more is treated as milliseconds, anything smaller as seconds. Always set the unit explicitly when precision matters.