Cron Parser

Standard 5-field format (minute hour day-of-month month day-of-week). Each field supports *, numbers, ranges (N-M), lists (N,M), and steps (*/N).

No, only the standard 5-field format is supported. Extended formats like Quartz (with seconds) are not supported.

Times are displayed in your browser's local timezone. Note that cron daemons on servers typically run in UTC unless configured otherwise — double-check the server timezone with 'timedatectl' or by examining /etc/timezone before relying on the preview.

No. Parsing and next-execution calculation run locally via the cron-parser library in your browser. Expressions from internal job definitions are never transmitted.

Yes, both run every 5 minutes. The step notation (*/5) is simply a shorthand for the explicit list. You can confirm they behave identically by comparing the next-execution previews for both expressions.

In the UNIX cron standard, specifying both fields uses OR logic — the job runs when either condition is met. For example, "0 9 1 * 1" runs at 9 AM on the 1st of every month and also every Monday at 9 AM. To avoid unintended behavior, it is best to leave one of the two fields as "*".

It reads as 'every 15 minutes, every hour, every day, every month, on every weekday' — the */15 in the minute field means 'every 15 minutes starting from 0', so the job runs at :00, :15, :30, and :45 of every hour. Paste it into the input above to confirm the next 10 execution times.

"0 */6 * * *" runs at minute 0 of every 6th hour (00:00, 06:00, 12:00, 18:00). "0 0 */6 * *" runs at 00:00 on every 6th day of the month (the 1st, 7th, 13th, 19th, 25th — and then resets at the next month). The step (*/N) applies to whichever field it appears in, so misplacing it changes the schedule entirely.

No. Linux/UNIX crontab uses the standard 5-field format (minute hour day month weekday). Quartz Scheduler (Java) and Spring's @Scheduled use 6 fields including seconds, and add special characters like L (last), W (weekday nearest), and # (nth weekday). Go's robfig/cron defaults to 6 fields. This tool parses the 5-field Linux format only.

February never has a 30th day. Cron silently skips impossible date combinations rather than throwing an error, which is a common source of jobs that 'mysteriously never run'. The next-execution preview above will show an empty list when this happens, which is a useful sanity check.

Standard UNIX cron does not have a 'last day' indicator. Quartz Scheduler supports L (e.g., 0 0 L * ? for last day at midnight). For UNIX cron, the common workaround is to schedule on the 28th-31st and add a shell check like '[ "$(date -d tomorrow +%d)" = "01" ] && /your/command'. This tool follows the standard 5-field format and does not support L/W/#.

Yes. It works as a cron parser, validator, decoder, and translator in one: it checks your crontab syntax, flags out-of-range or invalid fields, and converts the expression into a plain-English (human-readable) description so you can confirm it runs exactly when you expect.