Orbitautil
Time debugging workflow

Unix timestamp converter

Understand whether a timestamp is in seconds or milliseconds, convert it to a readable date and document the timezone used for debugging.

How it works

  1. Identify whether the value has 10 digits or 13 digits.
  2. Convert seconds or milliseconds consistently.
  3. Record the timezone used when comparing logs.
Workflow guide

Use this workflow

Convert Unix timestamps carefully by checking seconds, milliseconds and timezone assumptions.

Open related Orbitautil tool

Seconds vs milliseconds

Unix timestamps are often stored in seconds, while JavaScript timestamps commonly use milliseconds. Mixing the two creates dates that are far off.

Timezone note

A timestamp represents an instant. The displayed date depends on the timezone you use to format that instant.

Related date tools

Use the Portuguese date tools for date differences while the English timestamp converter is expanded into a full interactive tool.

Common use cases

  • Debug API timestamps.
  • Compare logs from different systems.
  • Document date conversion rules in integration notes.

Limitations

  • This page is a workflow guide in the first English release.
  • Timezone and daylight-saving rules can change interpretation.
  • Always confirm whether the source uses seconds, milliseconds or another unit.

Frequently asked questions

How do I know if a timestamp is seconds or milliseconds?

A current seconds timestamp usually has 10 digits. A current milliseconds timestamp usually has 13 digits.

Why does the displayed date change by timezone?

The timestamp is one instant, but local formatting changes the calendar date and time shown.

Is this a full converter yet?

This first English page is a workflow guide; a dedicated interactive converter can be added next.

Related English tools