Cron Expression Parser
Translate a cron expression into plain English and list its next runs in any time zone.
Convert an epoch timestamp from a log, database or API into a readable date, or turn a date into a timestamp. The current Unix time updates live.
| Language | Seconds since the epoch |
|---|---|
| JavaScript | Math.floor(Date.now() / 1000) |
| Python | import time; int(time.time()) |
| PHP | time() |
| Go | time.Now().Unix() |
| Java | Instant.now().getEpochSecond() |
| C# | DateTimeOffset.UtcNow.ToUnixTimeSeconds() |
| Ruby | Time.now.to_i |
| Bash | date +%s |
| MySQL | SELECT UNIX_TIMESTAMP(); |
| PostgreSQL | SELECT EXTRACT(EPOCH FROM now())::bigint; |
Send events to SensaCat’s ingest API and get alerted when jobs, webhooks and multi-step flows stall.
The number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is the same everywhere in the world at a given moment, which makes it useful for logs and APIs.
Current timestamps have 10 digits in seconds and 13 in milliseconds. JavaScript’s Date.now() and Java’s System.currentTimeMillis() return milliseconds; PHP’s time() and most Unix tools return seconds.
Systems that store Unix time as a signed 32-bit integer overflow at 03:14:07 UTC on 19 January 2038. Storing timestamps as 64-bit integers avoids it.
No. A timestamp always counts from a moment in UTC. Time zones only matter when you display it as a local date and time.
Translate a cron expression into plain English and list its next runs in any time zone.
Read a JWT’s header and claims, check expiry and verify HMAC signatures locally.
Pretty-print, minify and validate JSON with exact line and column errors.