A cron expression — the compact five-field string that schedules recurring tasks on Unix-based systems — is notoriously easy to get subtly wrong, since the field order and syntax aren't something most people work with often enough to memorize confidently. This builder lets you construct a cron expression visually, and instantly explains in plain language exactly when any given expression will run, entirely in your browser.
Why cron syntax trips people up
A standard cron expression packs five fields — minute, hour, day of month, month, and day of week — into a single terse string, and the meaning of special characters like *, ,, -, and / within each field isn't always intuitive without regular practice. A single misplaced field or misunderstood special character can schedule a task to run at completely the wrong time, or far more often than intended — a mistake that's easy to make and, without a validator, easy to miss until it causes a real problem in production.
How to use it
- Build your schedule visually, selecting specific minutes, hours, days, months, or intervals.
- The tool generates the correct cron expression automatically as you make selections.
- See a plain-language explanation of exactly when the resulting expression will trigger, to confirm it matches what you intended.
Common scheduling patterns
- Every N minutes or hours — using the step syntax (like
*/15for every 15 minutes) rather than manually listing out every value. - Once daily at a specific time — the most common pattern for daily backups, reports, or maintenance tasks.
- Specific days of the week — like running only on weekdays, useful for business-hours-only tasks.
- Monthly on a specific date — for tasks like monthly billing or reporting that need to run on a particular day each month.
Where cron expressions are actually used
Server-side scheduled tasks (backups, cleanup jobs, report generation), CI/CD pipeline scheduling for recurring builds or deployments, and scheduled functions in cloud platforms that use standard cron syntax for their trigger configuration all rely on getting a cron expression exactly right — a mistake here doesn't throw an obvious error, it just silently runs at the wrong time (or not at all), which is exactly why validating an expression before deploying it matters.
Frequently asked questions
What does an asterisk mean in a cron field? It means "every" value for that field — an asterisk in the minute field, for instance, means the task considers every minute as a match for that field.
Do all systems use the exact same cron syntax? Standard five-field cron syntax is widely consistent, though some systems add a sixth field for seconds or support slightly different special syntax — always verify against your specific system's documentation for edge cases.
Is my schedule data sent anywhere? No — the expression is built and explained entirely locally in your browser.
Why did my scheduled task run at the wrong time? Often a timezone mismatch between where the cron expression was written and where the scheduler actually executes it — always confirm which timezone your specific scheduling system uses.