Convert a Unix epoch (seconds or milliseconds) to human-readable UTC/ISO time, and convert a date back to an epoch — both directions in one tool.
Use responsibly. Use this tool on data from systems you own or are authorized to investigate. It only converts what you paste; it does not fetch remote data or act on a target. How you handle the numbers and the systems they came from remains your responsibility.
A Unix timestamp is the number of seconds since the Unix epoch, 1970-01-01 00:00:00 UTC. It is how computers store and exchange time internally — in logs, JWT exp/iat claims, cookies, databases, and APIs — because it is timezone-free and trivial to compare. This converter runs both directions: paste an epoch to expand it into ISO 8601, a human-readable UTC string, and a relative "time ago / from now" description, and enter a date to get its epoch in both seconds and milliseconds.
Seconds or milliseconds. Unix time appears in two common resolutions: seconds (10 digits for current dates) and milliseconds (13 digits), the latter being JavaScript's Date.now() default. Mixing them up is the number-one timestamp bug — a millisecond value read as seconds lands 50,000× too far in the future. This tool auto-detects the unit by magnitude and tells you which it assumed.
How you'll use it. Paste an epoch from a log line or token to see the real moment it refers to; when auditing a JWT, converting the exp claim tells you at a glance whether a token is long-lived or already expired, and iat shows when it was issued — decode the token's payload segment with the Base64 tool first to read those claims. Going the other way, enter a human date to produce the integer a query filter (created_after), a token exp, or a cron schedule expects. In incident timelines, normalizing every source's epoch to UTC ISO 8601 removes the ambiguity that wrecks correlation. For the fuller picture, read what unix epoch time is and how to read timestamps in logs and JWTs.
Parsing rules and pitfalls. For the date→epoch direction, ISO 8601 with an explicit zone (Z for UTC, or an offset like +05:30) is unambiguous — always prefer it. A date-only string like 2024-01-31 is interpreted as UTC midnight, but a date-time without a zone is read in the browser's local timezone, so two people can get different epochs from the same string. Non-standard formats (31/01/2024 vs 01/31/2024) parse inconsistently across engines. Also remember the "Year 2038 problem": a signed 32-bit seconds counter overflows on 2038-01-19, so long-lived systems must use 64-bit time.
Defensive angle. Security tokens live and die by timestamps. Set short, explicit expiries (exp) and validate them on every request; a token with no expiry is valid forever if leaked. Log in UTC to make cross-system correlation reliable, require an explicit timezone on dates you accept, range-check them, and be suspicious of records whose timestamps are impossibly future-dated or clustered — a sign of clock tampering or forged evidence.
Usage notes (authorized analysis). Convert timestamps while reading logs, JWTs, cookies, or database rows from systems you own or are authorized to investigate; the tool only converts between Unix epochs and human-readable time and does not decode tokens or fetch remote logs by itself. Paste an epoch from a log line or claim to see UTC / ISO 8601 / relative time, or enter a date to get seconds and milliseconds; prefer ISO 8601 with an explicit zone (Z or an offset) when converting dates back to epochs so two analysts get the same integer, and check the tool's unit detection (seconds vs milliseconds) before you trust a comparison — mixing them is the usual bug. When the claim sits inside a JWT, decode the payload first, then convert exp / iat here — see what is a JWT?. Updated October 18, 2026.
Detection & Defense. Require short, explicit exp values and reject tokens with no expiry, converting exp/iat during review so long-lived or already-expired tokens are obvious. Store and correlate logs in UTC, and require an explicit timezone on dates you accept from users. Treat impossible future dates or sudden clusters of identical timestamps as a signal of clock tampering or forged evidence, then verify against an independent time source. No claim is made that this page validates JWTs, signs tokens, or monitors clocks — it only converts the numbers you paste.
Translate a cron expression into plain English and see the next run times, so you can verify a schedule before it ships.
Validate, pretty-print, and minify JSON in your browser, with clear parse errors, configurable indentation, and a minified-size readout.
Count characters, words, and lines in any text instantly, with and without spaces.
Test a regular expression against sample text and get a static ReDoS (catastrophic backtracking) safety review.
Convert text between camelCase, snake_case, kebab-case, PascalCase, CONSTANT_CASE, Title Case, and more.
Compare two blocks of text line by line and see exactly what was added, removed, or unchanged.