Cron Parser
Parse five- or six-field schedules and inspect their next UTC runs.
Runs in your browser. Nothing is uploaded.
Run times are computed in UTC.
Read a Unix cron expression
A traditional Unix crontab expression has five fields in this order: minute, hour, day of month, month, and day of week. For example,0 9 * * 1-5 means at 09:00 on weekdays. An asterisk means all allowed values for that field. Lists such as 1,15, ranges such as 1-5, and steps such as */5 make a schedule more specific without writing every value.
This parser also accepts six fields with leading seconds. That format is useful for systems that support second-level schedules, but it is not the five-field format used by many Unix crontab files. Month names from JAN to DEC and day names from SUN to SAT are accepted. Both 0 and 7 mean Sunday for the day-of-week field.
Plain English and upcoming runs
After parsing, the tool shows a short explanation and the next ten run times. Upcoming values are generated from the current moment and displayed as ISO timestamps. The calculation is always in UTC, so the output does not change with the browser's local time zone or daylight saving rules. Use the displayed time zone explicitly when comparing a schedule with a server log.
When both day-of-month and day-of-week are restricted, Unix cron commonly treats a matching value in either field as a run. This detail can make an expression broader than it first appears. Check the next run list and the crontab documentation for the scheduler that will execute the expression. A parser can explain a schedule, but it cannot infer the business meaning of a job.
Supported scope and important limits
The supported nicknames are @yearly,@annually, @monthly, @weekly,@daily, @midnight, and @hourly.@reboot is intentionally rejected because it describes an event rather than a recurring UTC time. Quartz extensions such as a question mark, seven-field year expressions, L, W, and # are not Unix crontab syntax for this tool and are rejected.
Cron Parser is not a job runner, scheduler, alert system, or deployment service. It does not contact a server, save a crontab, trigger commands, inspect a machine, or tell you whether a process will finish on time. Treat the result as a review aid before placing an expression in the scheduler that owns the actual job.
Private schedule checks
The expression and calculated times stay in your browser. Nothing is uploaded while you paste, parse, copy, or inspect a sample. If a schedule is connected to an incident or deployment, remember that the expression itself may reveal operational details. For timestamp arithmetic and ISO values, compare the result with the Unix Timestamp tool.
FAQ
Does the parser contact a scheduler?
No. The expression is interpreted and upcoming dates are calculated in your browser using UTC, without contacting a scheduler. The expression is never uploaded.
How do five-field and six-field expressions differ?
Five fields are minute, hour, day of month, month, and day of week. Six-field input adds seconds at the beginning, followed by those same five fields.
Which names and nicknames are accepted?
Month names JAN through DEC and day names SUN through SAT are accepted, with both 0 and 7 representing Sunday. The supported nicknames are @yearly, @annually, @monthly, @weekly, @daily, @midnight, and @hourly.
How are ranges, lists, and steps interpreted?
Fields accept wildcards, comma-separated lists, numeric or named ranges, and positive steps such as */5 or 1-10/2. Values are checked against each field's allowed range, and day-of-week 7 is normalized to Sunday.
Does Cron Parser support Quartz expressions?
No. This parser accepts Unix-style crontab syntax rather than Quartz syntax. Quartz features such as a seven-field year, question mark, L, W, and # are rejected.
Why are @reboot and command execution not supported?
@reboot describes a system event and does not provide a recurring timestamp. The page only parses expressions and calculates upcoming UTC times, so it does not execute commands or act as a scheduler.
Are the upcoming run times local or UTC?
Upcoming runs are calculated and displayed in UTC. The calculation does not apply the browser's local time zone or daylight saving rules.