Unix Timestamp Converter
Epoch to date and back. UTC, local, ISO 8601, and relative time, with a live clock.
Open toolDecode cron expressions with the next run times, in your local timezone.
Runs locally in your browser
// human readable
At 09:00, Monday to Friday.
Working it out.
Want to know why a schedule behaves the way it does? The cron expression simulator runs the same engine with the traps laid out: uneven steps, the two day fields, and what daylight saving does to a job in the small hours.
* * * * * ┬ ┬ ┬ ┬ ┬ │ │ │ │ └─ day of week (0-7, Sun=0 and 7) │ │ │ └─── month (1-12) │ │ └───── day of month (1-31) │ └─────── hour (0-23) └───────── minute (0-59)
* any value, list of values, e.g. 1,15,30- range, e.g. 1-5/ step, e.g. */15 every 15JAN-DEC and SUN-SATWhen both the day-of-month and day-of-week fields are set, cron combines them with or, not and. 0 9 1 * MON runs on the 1st of the month and on every Monday, not only on Mondays that fall on the 1st. A monthly job written that way quietly runs weekly. If only one of the two is set, it behaves as you would expect.
Every minute of every hour of every day. The five fields are minute, hour, day-of-month, month, day-of-week. An asterisk in any field means "any value".
Use `*/15 * * * *`. The slash introduces a step value; `*/15` means every 15 minutes starting at minute 0.
Your local timezone, as reported by the browser. If your server runs cron in UTC, remember to adjust before scheduling.
Yes. `@daily` and `@midnight` are shortcuts for `0 0 * * *`. This parser expands them automatically when computing the next run times.
Tools are ported from DevOps Daily under the MIT license.View original
Epoch to date and back. UTC, local, ISO 8601, and relative time, with a live clock.
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