Is 0 Sunday or Monday?

Sunday. Day of week runs 0 to 6 from Sunday, and most implementations also accept 7 for Sunday, which is why you see both. Monday is 1. If a week must start on Monday for you, write 1 and not 0.

Does it work in GitHub Actions, Kubernetes and the cloud schedulers?

The five fields do. What differs is everything around them: some accept names like @daily, Kubernetes CronJobs take the same five, and GitHub Actions runs scheduled workflows late under load. Paste the expression, but do not assume the promptness.

Can I read an expression I already have?

Yes — the cron parser page does that. Paste an expression and it lists the dates it will next run and the values each field allows, which is the check worth doing before you trust one somebody else wrote.

What time zone does a weekly cron job run in?

The one of the machine or service that runs it: a server’s crontab uses the server’s time zone, and GitHub Actions reads schedules in UTC. So 0 9 * * 1 on a UTC scheduler runs at 9:00 UTC, not at 9:00 where you are.

Can cron run every other week?

Not with the five fields alone: there is no field for weeks, and */2 in the day-of-week field means days 0, 2, 4 and 6, not every second week. Run the job weekly and let the script skip odd or even week numbers.

Is anything sent anywhere?

No. The expression is built and read back in your browser, and nothing is uploaded. It is free, with no account.

Cron once a week

It is 0 0 * * 0 — Sunday at midnight.

Examples temporarily replace the input and settings. You can restore your previous work.

Input0 characters

Or pick a common one

cron: • • • • •

Output

• • • • •

  •••••••••• •••••• ••••••
  • •••••••• •••• ••••••
  • • •••••• ••• •• ••••• ••••••
  • • • •••• ••••• ••••••
  • • • • •• ••• •• •••• ••••• •••••• •• • • ••• • •• •••• ••••••••
  • • • • •

  •• •••• •••
    ••••••        •
    ••••          •
    ••• •• •••••  •••••
    •••••         •••••
    ••• •• ••••   •

  •••• •••• •••• •••••••••••••• ••••••
    •••••••••• •••••  •••
    •••••••••• •••••  •••
    •••••••••• •••••  •••
    •••••••••• •••••  •••
    •••••••••• •••••  •••

Your files stay on your device

This tool runs entirely in your browser. What you paste is processed on your device and is never sent to a server, so it is safe to use with tokens, keys and unpublished text.

Example

Example: weekly schedules in words, and the cron expressions they become

The preset on this page, Every Sunday, is 0 0 * * 0. For another day or time, set the menu to “Describe it below instead” and type the schedule in words: it is built into five fields and read back field by field.

The last field is the day of the week, 0 for Sunday to 6 for Saturday; the first two are the minute and the hour, on a 24-hour clock.
Two days make a list: 1,4 is Monday and Thursday.
Paste the line into crontab -e, a CI schedule or a cloud scheduler.

You type	Cron	Runs
(preset: Every Sunday)	0 0 * * 0	Sunday at 00:00
every Sunday at 2am	0 2 * * 0	Sunday at 02:00
every Monday at 9am	0 9 * * 1	Monday at 09:00
every Friday at 5:30pm	30 17 * * 5	Friday at 17:30
at 9am on Monday and Thursday	0 9 * * 1,4	Monday and Thursday at 09:00

0 9 * * 1 runs at 9:00 every Monday, in the time zone of the machine or service that runs it — the same five fields in crontab and in most schedulers.

How it works

The expression is already there: 0 0 * * 0. The five fields under it are minute, hour, day of month, month and day of week, in that order.
Copy it into your crontab, your CI schedule or your cloud scheduler. The same five fields mean the same thing in all of them.
To change it, set the menu back to none and describe the schedule in your own words — "every 2 hours", "at 5pm on weekdays" — and it is built and read back to you.
Check the reading, not the expression. What the page shows underneath comes from parsing what was built, so it is what a machine would do with it rather than what we meant.

Frequently asked questions

Is 0 Sunday or Monday?: Sunday. Day of week runs 0 to 6 from Sunday, and most implementations also accept 7 for Sunday, which is why you see both. Monday is 1. If a week must start on Monday for you, write 1 and not 0.
Does it work in GitHub Actions, Kubernetes and the cloud schedulers?: The five fields do. What differs is everything around them: some accept names like @daily, Kubernetes CronJobs take the same five, and GitHub Actions runs scheduled workflows late under load. Paste the expression, but do not assume the promptness.
Can I read an expression I already have?: Yes — the cron parser page does that. Paste an expression and it lists the dates it will next run and the values each field allows, which is the check worth doing before you trust one somebody else wrote.
What time zone does a weekly cron job run in?: The one of the machine or service that runs it: a server’s crontab uses the server’s time zone, and GitHub Actions reads schedules in UTC. So 0 9 * * 1 on a UTC scheduler runs at 9:00 UTC, not at 9:00 where you are.
Can cron run every other week?: Not with the five fields alone: there is no field for weeks, and */2 in the day-of-week field means days 0, 2, 4 and 6, not every second week. Run the job weekly and let the script skip odd or even week numbers.
Is anything sent anywhere?: No. The expression is built and read back in your browser, and nothing is uploaded. It is free, with no account.