Make sense of stubborn log timestamps

When an incident report only shows 1704067200000, this page tells you the actual moment.

Built for debugging logs, API payloads, and database events without scrolling through timezone offsets or mental math.

Raw epoch numbers are perfect for machines but useless during triage—you can’t eyeball whether that spike was before or after deploy without converting it.

Drop the timestamp below to see the real date, your local time, and the exact offset so you can answer “when did this happen?” confidently.

No accounts. Runs locally. No nonsense.

Tip: 10 digits = seconds, 13 digits = milliseconds. You can also suffix s or ms.

Uses your local timezone (your browser's).

Share links via ?e= (epoch) or ?d= (datetime-local).


Results

Copy buttons are per-result. URL updates happen without reloading the page.

What this tool surfaces fast

During log reviews you need to know whether that alert pinged before deploy, after deploy, or smack in the middle of quiet hours. Paste an epoch value and you instantly see the exact date, the UTC reading, and how it lands in your own timezone.

How to use it well

Common mistakes

Quick answers

How do I know if it was seconds or milliseconds?

10 digits usually means seconds, 13 means milliseconds. You can override via the Epoch mode dropdown or suffix timestamps with s/ms.

Which timezone powers the date input?

Your browser’s local timezone. The results panel shows both UTC and your local reading so you can compare.

Can I share a conversion with the incident channel?

Yes. The URL updates with ?e= or ?d= so pasting the link reproduces the same values for everyone.

What about historical or negative epochs?

They work. Use them to refer to pre-1970 events or offsets before “epoch zero.”

Related tools