Skip to content

Choose your path

Built around the job you need to finish

Convert a numeric epoch value with an explicit or disclosed inferred unit into one instant and multiple IANA-zone displays, and convert timezone-free form input only under a user-selected local or UTC basis.

Developer reconciling API and log timestamps

Distinguish seconds from milliseconds and preserve one UTC instant across displays.

Select or inspect the resolved unit, compare ISO/RFC/UTC/IANA output, then save the unit and timezone assumptions.

Can reproduce the instant without a hidden 1,000× unit shift.

Operations or incident reviewer across regions

Avoid ambiguous EST/PST/CST labels and browser-local date parsing surprises.

Use UTC for exchange, inspect named IANA zones with actual offset abbreviation, and record the host Intl/IANA dependency.

Correlates events without treating a seasonal abbreviation as a fixed zone.

User entering a wall-clock date

Choose whether a timezone-free `datetime-local` value means browser local time or UTC and keep edits stable.

Enter the date, choose basis, inspect seconds/milliseconds, and confirm the live clock does not overwrite input.

Gets a stable, explicit conversion even across a live clock update.

Was this tool helpful?

Reference & details

How it works

Unix Epoch

Unix time counts seconds (or milliseconds) since January 1, 1970 00:00:00 UTC — the Unix epoch. Negative values represent dates before 1970.

Timestamp (seconds) = (Date − Epoch) ÷ 1000

Seconds vs Milliseconds

The same instant has a millisecond value 1,000× its second value. The page offers explicit seconds and milliseconds choices; Auto uses a documented magnitude threshold and always displays the resolved unit, so digit length is never treated as proof.

ISO 8601 Output

ISO 8601 represents dates as YYYY-MM-DDTHH:mm:ss.sssZ (UTC) or with a numeric timezone offset (+05:30). It is the standard interchange format for APIs, logs, and databases.

Updated: July 2026

Example Scenarios

Convert a Unix timestamp from a JSON API response to a readable date.

Timestamp: 1704067200

2024-01-01 00:00:00 UTC

A developer converts a millisecond timestamp from browser console output.

Timestamp: 1704067200000

Same date — detected as milliseconds automatically

Convert a Unix epoch stored as an INTEGER in a database row to verify the record creation date.

Timestamp: 1672531200

2023-01-01 00:00:00 UTC

Common Mistakes to Avoid

Confusing seconds and milliseconds

Do not infer a unit from digit count alone. Select seconds or milliseconds from the producer's contract, or record the page's displayed Auto inference before using the result.

Ignoring timezone when comparing timestamps

Unix timestamps are always UTC. Displaying in local time adds your timezone offset. When comparing logs from different regions, convert all values to UTC first.

FAQ

A Unix timestamp is the number of seconds (or milliseconds) since January 1, 1970 00:00:00 UTC. It provides a timezone-independent way to store and compare dates in software systems.

Use the producing API, database, or log schema. This page lets you select seconds or milliseconds explicitly and displays the resolved unit when Auto is used; magnitude is only a fallback heuristic.

A numeric epoch value represents an instant relative to UTC. ISO output is UTC (Z); additional displays use the selected IANA zone and the browser runtime's time-zone data. A timezone-free date input is interpreted only under the Local or UTC basis you select.

ISO 8601 is an international date-time standard: YYYY-MM-DDTHH:mm:ss.sssZ (UTC) or with timezone offset (+05:30). It is widely used in APIs, logs, and JSON payloads.

32-bit systems store Unix timestamps as signed 32-bit integers, which overflow on January 19, 2038 at 03:14:07 UTC. Modern 64-bit systems and languages are unaffected, but legacy embedded systems may still be vulnerable.

About Timestamp Converter

Convert between Unix epoch timestamps and readable dates in seconds or milliseconds. Essential for debugging API responses, log files, database records, and any system that stores time as a numeric epoch value.