The five fields
| Position | Field | Allowed values | Example |
|---|---|---|---|
| 1 | Minute | 0 to 59 | 30 |
| 2 | Hour | 0 to 23 | 7 |
| 3 | Day of month | 1 to 31 | * |
| 4 | Month | 1 to 12 | * |
| 5 | Day of week | 0 to 6, Sunday is 0 | 1 (Monday) |
Building or checking a schedule
Start from a preset or the builder
Presets cover weekdays at 09:00, every 15 minutes, a nightly 02:30 job, the first of the month and Sundays at 18:00. The builder offers every few minutes, hourly, daily, chosen weekdays or monthly.
Or paste an expression
Type five fields into the expression box. Mistakes such as an hour of 25 are reported in words, for example that 25 is outside 0 to 23 for the hour field.
Check the description and run times
The sentence under the box describes the schedule, and the table lists the next ten runs in the time zone you pick.
Copy it for your platform
Choose the platform to see the right syntax, then copy it, or export the next runs as CSV or a calendar file.
Example: a weekly lead list export on Monday mornings
A sales operations contractor wants a script that exports the week's new leads from a CRM at 07:30 every Monday. She types 30 7 * * 1.
The tool describes it as At 07:30, on Monday, and with Europe/London selected lists the next runs from 16 November 2026. Switching platform shows the crontab line, the GitHub Actions block marked as UTC, cron(30 7 ? * 2 *) for AWS EventBridge, where Monday is day 2, and 0 30 7 ? * 2 for Quartz, which puts seconds first.
Cron expression: 30 7 * * 1 Show times in: Europe/London
At 07:30, on Monday. Next runs: Mon, 16 Nov 2026, 07:30 / Mon, 23 Nov 2026, 07:30 / Mon, 30 Nov 2026, 07:30 AWS EventBridge: cron(30 7 ? * 2 *) Quartz: 0 30 7 ? * 2
Time zones and clock changes
Cron runs in the time zone of the server it is on. GitHub Actions and Vercel always use UTC, so a job set for 07:30 there runs at 08:30 UK time in summer. The run times table lets you check this by switching between UTC and Europe/London.
In the UK, the hour from 01:00 to 02:00 is skipped in March and repeated in October, and cron programs treat it differently. The tool warns against scheduling important jobs in that hour. Test any new schedule with a harmless command first.
Questions people ask
What does * mean in a cron expression?
An asterisk means every possible value for that field. In 30 7 * * 1, the asterisks in the day of month and month fields mean any day and any month, so the job runs whenever the other fields match: 07:30 on Mondays. The tool's description reads the asterisks for you.
How do I run a cron job every 15 minutes?
Use */15 in the minute field and asterisks elsewhere: */15 * * * *. The slash means every so many steps, starting from zero, so it runs at :00, :15, :30 and :45 each hour. Pick the Every 15 minutes preset to see the next run times.
Why is my cron job running an hour out?
Usually because the server, or the platform such as GitHub Actions, uses UTC while you think in UK time. Between late March and late October, UK time is an hour ahead of UTC. Use the time zone selector to see when the job will really run.
Why are AWS and Quartz expressions different?
They use six or more fields and number weekdays from 1 for Sunday to 7 for Saturday. They also need a question mark in either the day of month or day of week field. The tool converts the five-field expression into each format so you can copy the right one.
Where your data goes
Expressions are parsed and run times worked out by the page in your browser, using your device's time zone data. Nothing you schedule is sent to a server.
Checked against the tool on