Utilities

Epoch time converter

Unix time ↔ local date & time. All in your time zone.

Unix time in logs, tokens, and databases

Incident timelines mix ISO-8601 strings with raw epoch fields from Redis, Postgres, or CloudWatch. A quick converter prevents off-by-one-hour mistakes when correlating deploy times with error spikes.

JWT and session expiry

JWT exp and iat claims are numeric epoch seconds. Decoding a token shows the integer; converting here tells you whether a 401 is simply clock skew or a genuinely expired refresh window.

Milliseconds in JavaScript stacks

Front-end frameworks often log performance.now() offsets or store created_at as 13-digit integers. Dividing by 1,000 before conversion is the usual fix when dates land in the year 50000+.

FAQ

Seconds or milliseconds?
Unix time is usually seconds since 1970-01-01 UTC. JavaScript Date.now() and many mobile SDKs use milliseconds. A 13-digit value is almost certainly ms; 10 digits are seconds.
Which time zone is shown?
Human-readable output follows your browser's local offset. UTC labels are not implied—compare against server logs that may be Zulu or a fixed region.
Why does my timestamp look wrong?
Double-check unit scale, sign, and whether the source clock was UTC. Daylight saving transitions can surprise you when converting wall-clock strings back to epoch.