ToolAtlas
FavoritesRecent

Timestamp converter

Processed in this browser

Text limit: 256 characters

This tool never uploads your input.

A log line that says 1725446400. We treat the integer as UTC epoch and show it against this browser. Zone conversion is the sibling page.

A stack trace with ts=1725446400. This page is epoch ↔ human. JavaScript’s Date is millisecond-based; paste the right width.

Wall-clock meetings: timezone converter. Age and date spans: age / date difference. Cron next-runs: cron parser (UTC).

Seconds vs milliseconds

Ten digits are usually seconds; thirteen are milliseconds. Mix them and you get 1970 or year 50,000. Wall-clock city names are the timezone page. Cron next-runs are the five-field UTC parser. JWT exp is often seconds — decode-only, no verify.

How to use it

  1. Paste seconds or milliseconds, or pick “now.”
  2. Read UTC and local.
  3. If the year looks absurd, you swapped s/ms.

Honest limits

Not GPS time. Not a forensic clock. Not IANA conversion by itself.

FAQ

Seconds or milliseconds?

10 digits are usually seconds. 13 digits are usually ms. Mixing them lands you in the 1970s or the year 50,000.

Is the result UTC or local?

We show both when the form does. ‘Now’ is this device’s clock — wrong if the OS zone is wrong.

Can I convert America/New_York to Tokyo?

That is the timezone converter. This page is epoch ↔ display.

Leap seconds?

Unix time as used in JS ignores leap seconds. Do not use this for telescope scheduling.

Is the number uploaded?

No.

Related tools