Cron Expression Parser

Decode cron expressions into plain English, see a field-by-field breakdown, and preview the next 10 execution times. Click a preset or type any standard 5-field cron expression - perfect for debugging crontab entries and CI/CD schedules.

FAQ

From left to right: Minute (0�59), Hour (0�23), Day of Month (1�31), Month (1�12), and Day of Week (0�7 where both 0 and 7 are Sunday). Use * for "every", commas for lists, hyphens for ranges, and / for step values.

Standard Unix cron uses 5 fields. Some implementations (like Amazon CloudWatch Events, certain Quartz schedulers) add a 6th field for seconds or years. This tool parses the classic 5-field format used by crontab, GitHub Actions, and most Linux systems.

* means every (e.g., * in hour = every hour). */N means every N intervals. , separates values in a list. - defines a range. In some implementations, ? means no specific value (used in Quartz), L means last, W means weekday, and # means nth occurrence.

Common issues: the server's timezone doesn't match expectations, the cron daemon isn't running, permissions on the script file are wrong, PATH environment variables aren't set (use absolute paths), or the cron expression itself has a syntax error. Always test cron expressions before deploying.

The predictions are based on your browser's local timezone and use the standard cron matching algorithm. They are accurate for most use cases but don't account for DST transitions (some cron implementations skip or repeat jobs around DST changes).