Cron Expression Parser
Decode cron expressions with the next run times, in your local timezone.
Open toolEpoch to date and back. UTC, local, ISO 8601, and relative time, with a live clock.
Runs locally in your browser
Logs, JWT exp claims, Kafka offsets, and created_at columns often store raw epoch numbers. Paste one in to see the actual date in UTC and your local time, plus whether it was recorded in seconds or milliseconds.
Unix tools use seconds (date +%s); JavaScript and many APIs use milliseconds. Mixing them is a classic off-by-1000 bug. This tool detects which one you pasted by its magnitude and shows both, so a cron schedule or a TTL never lands a thousand times too early or too late.
The number of seconds since 1970-01-01 00:00:00 UTC (the Unix epoch), ignoring leap seconds. `date +%s` prints the current one.
Unix tools use seconds (10 digits until the year 2286). JavaScript, Java, and many APIs use milliseconds (13 digits). This tool auto-detects which you pasted by its length.
A signed 32-bit timestamp overflows on 2038-01-19 03:14:07 UTC. The fix is 64-bit time, which most modern systems already use.
No. All conversion happens locally in your browser.
Tools are ported from DevOps Daily under the MIT license.View original
Decode cron expressions with the next run times, in your local timezone.
Open toolParse CIDR blocks, compute ranges, split into smaller subnets, and check whether an IP lives inside a network.
Open toolInspect any JWT in your browser. Nothing is sent to a server.
Open tool