Unix Timestamp Converter

Convert Unix seconds or milliseconds into an ISO timestamp and relative time.

ISO Timestamp
Detecting...
Detecting...
Timezone
Detecting...
Detected Unit
Detecting...
Unix time is calculated from the Unix epoch: 1970-01-01T00:00:00.000Z.
Unix seconds count seconds since that moment.
Unix milliseconds count milliseconds since that moment.

About this tool

Unix Time helps developers, SREs, support teams, and analysts convert Unix seconds or milliseconds into ISO, UTC, local, and relative time. Use it for log timestamps, API fields, webhook payloads, cache expiry values, database rows, and timezone-sensitive incident notes.

Use cases

  • Paste a 10-digit or 13-digit epoch value from logs to see whether it represents seconds or milliseconds and translate it into readable UTC and local time.
  • Convert an ISO timestamp into Unix time before testing an API request, signed URL expiry, token expiry, or cache expiration field.
  • Check a webhook or database timestamp during an incident so support can align customer reports with server-side events.
  • Compare local time and UTC output before scheduling jobs, reporting cutoffs, or cross-region maintenance windows.

FAQ

What is Unix Time best used for?

Unix Time is best used to convert epoch seconds or milliseconds into readable timestamps and to convert human-readable times back into Unix values for APIs, logs, and schedules.

What input and output should I expect?

Enter an epoch value, date, or timestamp depending on the selected direction. The tool returns converted seconds, milliseconds, ISO, UTC, local, and relative time details where applicable.

How do I know whether a value is seconds or milliseconds?

Unix seconds are typically 10 digits today, while Unix milliseconds are typically 13 digits. If the converted date is far in the future or far in the past, switch units and verify against surrounding log context.

What edge cases should I watch for?

Timezone display, daylight saving transitions, leap seconds, negative pre-1970 timestamps, and language-specific date limits can affect interpretation. Store canonical values in UTC when possible.