Convert Unix cron to Quartz

Seconds field, weekday renumbering, the “?” rule and OR-day splits — handled, then checked run-by-run against the original.

Dialect set manually: Unix.
NATIVE exact Unix
0Minuteat minute 0
9Hourthe 09:xx hour
1Day of monthday 1
*Monthevery month
1-5Day of weekMonday through Friday

At 09:00, on day 1 of the month OR on weekdays (Monday–Friday).

  • Times are in UTC.
  • Day rule: OR — a day matching either field runs.
  • Note: Both day-of-month and day-of-week are restricted: the job runs on days matching EITHER field (OR).AMBIGUOUS_SEMANTICS, column 5Fix: To require both, keep one field "*" and test the other in the command, or use a dialect with AND semantics.

Loading the simulator…

Three things change, one can’t

Quartz adds a seconds field at the front, numbers weekdays 1–7 starting with Sunday (so Unix 1-5 becomes 2-6, or keep MON-FRI names), and requires “?” in one day field. The fourth difference cannot be fixed in a single expression: Unix runs when either day field matches, but Quartz cannot restrict both. The example 0 9 1 * 1-5 runs on the 1st and on every weekday, so the converter outputs two Quartz expressions to register as two triggers on the same job.

After converting, CronViewer simulates the source and the result for the next 400 days in your time zone, using each platform’s DST policy, and lists any run that appears on only one side. “Equivalent” is shown only when that check passes.

Try these

Questions

What is the Quartz equivalent of 0 0 * * *?

0 0 0 * * ? — midnight every day. The leading 0 is seconds and “?” goes in day-of-week.

Does Quartz support @daily?

No. Quartz has no macros; the converter expands them.