Build and parse cron expressions visually. Fast, secure, and completely free. All processing happens in your browser — no data is sent to any server.
A Cron Expression Builder translates a plain description of a schedule — 'every day at 2:30 AM', 'every 15 minutes', 'every Monday at 9 AM' — into the five-or-six-field cron syntax (minute, hour, day-of-month, month, day-of-week) that scheduling systems like crontab, Kubernetes CronJobs, and CI/CD pipelines actually use. Cron syntax is compact but genuinely easy to get subtly wrong by hand — mixing up which field is which, or misunderstanding how day-of-month and day-of-week interact when both are specified.
Deploying a scheduled job with a subtly wrong cron expression is a specific, annoying failure mode: the syntax is valid, so there's no error, but the job runs at 2 PM instead of 2 AM, or every minute instead of every hour, and you might not notice until the job runs at the wrong time in production. Building the expression visually and previewing the next few actual run times catches that class of mistake before you deploy, which is much cheaper than debugging it after a job has been silently misfiring.
In order: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, where 0 is Sunday). Getting the field order wrong is one of the most common cron mistakes.
Standard cron treats this as an OR condition — the job runs if either the day-of-month or the day-of-week matches, which is a common source of confusion since many people expect it to require both to match (an AND).
It depends entirely on the system running the cron job — most traditional crontabs use the server's local system timezone, while cloud schedulers often let you specify a timezone explicitly, so always confirm which one applies to your environment.
It means 'every value' for that field — an asterisk in the hour field means the job is eligible to run every hour, subject to the other fields' constraints.
No, standard Unix cron uses five fields without seconds; some systems (like Spring's scheduler or certain cloud schedulers) support an optional sixth leading field for seconds, so check what your specific scheduler expects.