Loading...
Paste a cron expression and see it explained in plain language, plus the next upcoming execution times computed for you. Supports the standard five-field syntax and the @shorthand forms like @daily and @hourly.
Stop guessing whether "30 4 * * 1" means Mondays or the 1st of the month — the parser tells you, and the next-runs list shows exactly when your job will fire so you can validate schedules before they hit production.
Minute, hour, day-of-month, month, day-of-week — in that order. "30 4 * * 1" = minute 30, hour 4, any day of the month, any month, Monday: 04:30 every Monday.
* means "every unit" (every minute, every hour). */5 means "every fifth unit" — */5 in the minute field fires at 0, 5, 10... Both are step values; */5 is just * with a step.
Usually the server's system time (often UTC for cloud schedulers), but some services let you choose. This parser computes next runs in your browser's local timezone — always confirm the timezone your actual scheduler uses.
Classic traps: day-of-month AND day-of-week are OR-combined when both are restricted, and DST transitions can skip or repeat an hour. Testing the expression here before deploying catches most surprises.
PureKit · cron · Free online tool — files processed locally in your browser, no upload.