Cron expression parser

How to read a cron expression

Cron expressions are short and easy to misread. Paste one, such as 0 9 * * 1-5, and get a clear sentence like 'At 09:00 AM, Monday through Friday', with the next run times below it. Confirm a schedule does what you meant before you deploy it to a crontab, a CI pipeline or a cloud scheduler.

See the next runs

The parser also lists the next five run times in your local time zone. Each one has a hint like 'tomorrow' or 'in 3 days'. It's the fastest way to sanity-check a job.

Standard 5-field syntax

It supports the classic minute, hour, day of month, month and day of week fields, with ranges, lists and steps like */15. Preset buttons give you common schedules to start from.

Cron field reference

The five fields are minute (0 to 59), hour (0 to 23), day of month (1 to 31), month (1 to 12) and day of week (0 to 6, with 0 as Sunday). An asterisk means every value, a comma separates a list such as 1,15, a hyphen gives a range such as 1-5, and a slash sets a step such as */15 for every 15 minutes. The examples above the box cover common schedules.

Before you start

Cron Expression Parser works on the text or values you enter. Output: Schedule. The settings appear before anything runs, so you can check them first. Your original file is never changed.

The value you enter is processed in your browser. Still test the output where it will be used. Clean formatting does not prove the data is safe or correct.

Keep the original until you have opened and checked the result. The work happens in this browser tab, so the size you can handle depends on your device's memory, your browser and the file itself.

How to use the cron expression parser

1. Enter a 5-field cron expression, or pick a preset.
2. Read the plain English description.
3. Check the next five run times.
4. Adjust the fields until the schedule is right.