Your everyday developer toolkit

Cron Explainer

Understand a standard five-field cron schedule.

Numeric five-field cron only. Lists, ranges, wildcards and steps are supported; names, macros and seconds are not.

Processed in your browser; input is not sent to the server.

A practical guide to cron schedules

What is cron?

Cron is a scheduling convention commonly used to run tasks at specified times. A traditional schedule has five fields: minute, hour, day of month, month and day of week. For example, 0 9 * * 1-5 describes 09:00 on weekdays in the scheduler's time zone. The asterisk means every permitted value for that field.

This explainer handles numeric five-field schedules. It accepts individual values, comma-separated lists, ranges, wildcards and steps such as */15. It does not accept a seconds field, month or weekday names, macros such as @daily, or extensions such as L and W. Different cron implementations support different extensions, so consult the scheduler that will actually run your job.

Common developer uses

Developers use cron schedules for routine reports, backups, maintenance tasks and periodic checks. A schedule is only one part of a reliable job: the command also needs appropriate permissions, logging, retry behavior and protection against overlapping runs. A cron expression does not itself guarantee that a task completed successfully.

Enter a schedule to see each field described as you type. Minutes range from 0 to 59, hours from 0 to 23, days of month from 1 to 31, and months from 1 to 12. Days of week range from 0 to 7, where 0 and 7 both mean Sunday. Steps apply within a wildcard or range, so */15 in the minute field selects 0, 15, 30 and 45.

Troubleshooting common errors

If an expression is rejected, count the fields and check for out-of-range numbers, reversed ranges, empty list items or a zero step. A six-field expression may belong to a scheduler that includes seconds; do not remove a field without checking its documentation. This tool explains the specified values but does not calculate next execution times.

Time zones and daylight saving changes can make a valid schedule run at an unexpected local time. Confirm the scheduler's configured zone and test around clock changes. Dates such as the 31st do not occur in every month. Traditional cron treats restricted day-of-month and day-of-week fields as alternatives, but some systems differ; check the target implementation before relying on that behavior.

Privacy and verification

Explanations are generated in your browser and your expression is not submitted by the tool. This page is a learning aid, not a substitute for testing with the actual scheduler. Check your expression against its documentation, monitor the first runs, and avoid exposing sensitive command details through screenshots or shared devices.