Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenPaste an epoch value or ISO date and read it as seconds, milliseconds, ISO, UTC and local time.
Unix seconds, Unix milliseconds or an ISO 8601 string.
Or press Now to load the current Unix second.
Seconds, milliseconds, ISO, UTC and local time fill in together.
Use Copy ISO, or select any field and copy it.
A JWT's exp claim says 1767225600, the token was rejected, and you need to know whether it had already expired. Timestamp Converter turns that number into a date in UTC and in your local time, so the comparison takes seconds.
Choose the input type (Unix seconds, Unix milliseconds or an ISO 8601 string) and type the value. Five read-only fields fill in at once: seconds, milliseconds, ISO 8601 in UTC, the UTC string, and your local time as formatted by the browser. A live clock at the top ticks every second with the current time in both units, the Now button loads the current second, and Copy ISO puts the ISO value on your clipboard.
The most common mistake is the wrong unit. A 13-digit value is milliseconds; read as seconds, it lands tens of thousands of years in the future. A 10-digit value read as milliseconds lands in January 1970. If the result looks absurd, switch the input type first. ISO mode uses the browser's date parser, so a string without an offset, such as 2026-03-01T09:00, is read as your local time. To check token lifetimes directly, the JWT expiry checker reads exp and iat for you, and converting between time zones helps when the question is about a city rather than an epoch.
All conversion uses the JavaScript Date object in your browser, and the local time shown reflects your device's timezone setting.
Related: JWT Decoder · JWT Expiration Checker
Keyboard shortcut
Turn epoch fields into human dates during outages.
Convert a calendar time into Unix seconds for filters.
Cross-check JWT exp values against wall-clock time.
Answers for this tool. For site-wide help, open the FAQ hub.
Count the digits. Current Unix time has 10 digits in seconds and 13 in milliseconds. JavaScript's Date.now() and Java's currentTimeMillis() produce milliseconds, while Unix tools and most JWT claims use seconds.
Local time is formatted with the timezone of the device viewing the page. The seconds, milliseconds and ISO fields are identical everywhere, so share those when you compare notes.
Yes. Negative timestamps count backwards from the epoch, so -86400 is 31 December 1969 in UTC. ISO strings for older dates work as well.