Parse any format, decode JWTs, convert timezones, generate code snippets for 10 languages — all instantly, all offline.
Smart Universal Parser
// Paste anything — Unix seconds/ms, ISO 8601, RFC 2822, human date. Auto-detected instantly.
Developer Stack Snippets
// Copy-ready code for your stack — current timestamp injected automatically.
Timestamp Difference Calculator
// Exact duration between two timestamps — including business days.
JWT Expiration Decoder
// Paste a JWT — extracts exp, iat, nbf and checks expiration status.
Multi-Timezone Collaboration View
AI-Friendly Date Formatter
// Copy AI-optimised context — paste directly into ChatGPT, Claude, or Gemini.
Relative Time Engine
// Human-readable translations of the timestamp above.
A Unix timestamp (also called epoch time, POSIX time, or Unix time) is the number of seconds elapsed since January 1, 1970 at 00:00:00 UTC — known as the Unix epoch. It is the universal representation of time in software systems: timezone-independent, easy to compare, and natively supported in every programming language.
Example: the Unix timestamp 1715429912 represents Sunday, May 11, 2026 at 14:38:32 UTC. Paste it in the tool above to see all conversions instantly.
Unix timestamps most commonly represent seconds, but many modern systems use milliseconds for greater precision. JavaScript's Date.now(), Java's System.currentTimeMillis(), and most databases use milliseconds.
| Format | Digits | Example | Language |
|---|---|---|---|
| Unix seconds | 10 | 1715429912 | Python, PHP, Go, Rust, C |
| Unix milliseconds | 13 | 1715429912000 | JavaScript, Java, Kotlin |
| Unix microseconds | 16 | 1715429912000000 | PostgreSQL, ClickHouse |
TimeTrace automatically detects which precision you're using and warns you if a 10-digit number resolves to an unexpected date.
// Unix seconds → Date
const date = new Date(1715429912 * 1000);
// Current Unix timestamp
const now = Math.floor(Date.now() / 1000);from datetime import datetime, timezone
dt = datetime.fromtimestamp(1715429912, tz=timezone.utc)
# 2026-05-11 14:38:32+00:00$dt = new DateTime('@1715429912');
$dt->setTimezone(new DateTimeZone('UTC'));
echo $dt->format(DateTime::ATOM);SELECT TO_TIMESTAMP(1715429912);
-- 2026-05-11 14:38:32+00
SELECT EXTRACT(EPOCH FROM NOW())::BIGINT;exp claim)A JSON Web Token (JWT) encodes time as Unix seconds in three standard claims: iat (issued at), exp (expiration), and nbf (not before). The payload is Base64url-encoded — you can decode it without a secret key to inspect these values.
function decodeJWTPayload(token) {
const base64 = token.split('.')[1]
.replace(/-/g, '+').replace(/_/g, '/');
return JSON.parse(atob(base64));
}
const { exp, iat, nbf } = decodeJWTPayload(token);
const isExpired = Math.floor(Date.now() / 1000) > exp;
const expiresIn = exp - Math.floor(Date.now() / 1000); // secondsEpoch time refers to the Unix epoch — January 1, 1970 00:00:00 UTC, the reference point from which Unix timestamps are calculated. "Epoch time" and "Unix timestamp" are used interchangeably.
If your timestamp shows a date near 1970, you likely have a Unix timestamp in milliseconds but are treating it as seconds. A 13-digit number like 1715429912000 divided by 1000 gives the correct 10-digit Unix seconds 1715429912. TimeTrace detects this automatically.
The 32-bit Unix timestamp limit is January 19, 2038 at 03:14:07 UTC (timestamp 2147483647), known as the Year 2038 problem. Modern systems use 64-bit integers, which extend the range to the year 292 billion.
No. ISO 8601 is a format standard for representing dates and times (e.g. 2026-05-11T14:38:32Z). UTC is a timezone. An ISO 8601 string can include timezone information — the trailing Z means UTC, while +02:00 means UTC+2.
Unix timestamps are always in UTC and are not affected by DST. The DST conversion only happens when you display the timestamp in a local timezone. Always store and compare timestamps in Unix seconds or UTC — never in local time.
RFC 2822 is the date format used in email headers: Mon, 11 May 2026 14:38:32 +0000. It is also produced by JavaScript's Date.toString() and Date.toUTCString() methods. TimeTrace parses and converts RFC 2822 dates automatically.
After converting any timestamp in TimeTrace, a Shareable link row appears in the results. Copy that URL — it includes a ?t= parameter. When your colleague opens it, the same timestamp is auto-loaded and converted. Works for JWT tokens too with ?jwt=.
No. TimeTrace runs entirely in your browser using native JavaScript APIs. No data — timestamps, JWT tokens, dates — is ever sent to any server. There is no backend, no analytics, and no tracking of any kind.