Cron expression `10 0 7 JUN *` runs at 00:10, on day 7 of the month, only in June

What this cron means, field by field

Each field of 10 0 7 JUN * controls one dimension of the schedule. Hover over any value in the editor above to see its tooltip; the table below summarises the same information.

Field	Value	Means	Range / hint
minute	`10`	at minute 10	0-59. The minute(s) of the hour the job will fire.
hour	`0`	at hour 0	0-23. The hour(s) of the day the job will fire (0 = midnight, 23 = 11 PM).
day of month	`7`	at day of month 7	1-31. The day(s) of the month. Use * if you want every day.
month	`JUN`	at month JUN	1-12 or JAN-DEC. The month(s). Use * for every month.
day of week	`*`	every value (wildcard)	0-7 or SUN-SAT (0 and 7 both mean Sunday). Use * for every day of the week.

Next 5 runs

Shown in UTC. Change the timezone in the editor.

Next runs · UTC

Mon 7 Jun · 00:10in 263d 12h
Wed 7 Jun · 00:10
Thu 7 Jun · 00:10
Fri 7 Jun · 00:10
Sat 7 Jun · 00:10

Similar cron expressions

Common variations and tweaks of 10 0 7 JUN *.

10 0 7 JUN 1-5At 00:10, on day 7 of the month, Monday through Friday, only in June

Where else this cron could be used

The same expression 10 0 7 JUN * works in:

Standard Unix crontab (5-field syntax).
AWS EventBridge / Lambda Scheduled (with a 6th field for year, often *).
Vercel cron jobs (declared in vercel.json).
Quartz Scheduler and node-cron, robfig/cron and similar libraries.

Examples

0 18 * * *
Every day at 18:00
0 */5 * * *
Every 5 hours
0 18 * * 1-5
Weekdays at 18:00
0 0 1 * *
Once a month, on the 1st at midnight

Cheatsheet

Full cheatsheet

Field	Req.	Range	Wildcards
minute	yes	0-59	, - * /
hour	yes	0-23	, - * /
day of month	yes	1-31	, - * /
month	yes	1-12 or JAN-DEC	, - * /
day of week	yes	0-6 or names; some dialects use 0-7 or 1-7 — see Dialects	, - * /

Frequently asked questions

What does the cron expression `10 0 7 JUN *` mean?

at 00:10, on day 7 of the month, only in June.

When does `10 0 7 JUN *` run next?

The next runs (UTC): 2027-06-07 00:10; 2028-06-07 00:10; 2029-06-07 00:10; 2030-06-07 00:10; 2031-06-07 00:10.

Is `10 0 7 JUN *` a valid cron expression?

Yes - CronTool's parser accepts this expression and the calendar projects future runs successfully.