Debug logs
Convert numeric timestamps from logs and monitoring tools into readable values during incident review.
Time tool
Convert Unix timestamps into readable local time, UTC time, ISO strings, seconds, and milliseconds.
Use cases
Convert numeric timestamps from logs and monitoring tools into readable values during incident review.
Inspect timestamp fields in API responses, webhook payloads, database rows, and scheduled jobs.
Seconds and milliseconds are easy to confuse. A 10-digit value is usually seconds, while 13 digits is usually milliseconds.
Basics
A Unix timestamp counts time from the Unix epoch: January 1, 1970 at 00:00:00 UTC. It is a compact and language-agnostic way to represent time in logs, databases, APIs, and auth claims. Seconds are the traditional format. Milliseconds are also common when systems need more precision.
This converter is especially useful with JWT claims such as exp, iat, and nbf, with API payloads that use numeric time fields, and with logs that need to be compared across time zones. Pair it with the JWT Decoder when you are reading token claims, the JSON Formatter when the timestamp is inside a payload, and the SQL Formatter when you are reviewing database queries that store time values.
Examples
In JavaScript, Date.now() returns milliseconds since the epoch. In Python, the time and datetime modules are the usual helpers. Those values are easy to convert into readable strings when a bug report includes only a raw number or when a JWT expires sooner than expected.
If a token seems valid in JSON but still fails, compare the time fields against the current browser clock and the server clock. A small clock skew can produce a visible failure. That is why time conversion is one of the fastest ways to debug authentication issues in practice.