Regex and cron

Cron Expression for Every Monday

At 00:00 every Monday, once a week. Copy it, check the next runs in your time zone and grab a snippet for your platform.

  • Free foreverNo trial, no paywall, no usage limits.
  • No sign-upOpen the page and start. We never ask for an email to use a tool.
  • PrivateEverything runs in your browser. Your input is never uploaded or stored on our servers.
  • Works offlineOnce the page has loaded, the tool keeps working without a connection.

Cron expression

0 0 * * 1
Customize
0minuteMinute: at minute 0 (on the hour)0hourHour: at hour 0 (midnight)*day (month)Day of month: every day of the month*monthMonth: every month1day (week)Day of week: only on Monday

At 00:00 every Monday, once a week.

Time zone
Run times, the week view and the snippets use this zone. It starts as your device's zone.
Show times as 9:00 AM instead of 09:00.

Next runs

Each run in your selected time zone, with the same moment in UTC. Daylight saving changes follow cronie, the cron on most Linux servers.
Copy run times (ISO 8601)

Next 7 days

Each square is one hour of local time in your selected zone. Darker squares have more runs. Daylight saving changes are not drawn.

Use it on your platform

Copy-ready config for each scheduler. Dialects differ: some only run in UTC, some can't do seconds, Cloudflare and AWS number weekdays from 1 = Sunday. The snippet handles the conversion and says what changed.
A line for crontab -e on Linux or macOS (Vixie cron, cronie).on.schedule for a workflow, with the timezone field GitHub added in March 2026 (UTC when omitted).A CronJob manifest with the timeZone field (Kubernetes 1.27+).Cron Triggers in wrangler.toml for a Worker. Runs in UTC and numbers weekdays from 1 = Sunday.crons in vercel.json plus the route it calls. Runs in UTC.EventBridge Scheduler (any time zone, recommended by AWS) and a legacy EventBridge scheduled rule (UTC).A .timer unit with OnCalendar=, the systemd replacement for cron.
Runs as writtenRuns in your time zone
crontab -e
Copy crontab -eDownload my-job.crontab
# ┌───────────── minute (0–59)
# │ ┌─────────── hour (0–23)
# │ │ ┌───────── day of month (1–31)
# │ │ │ ┌─────── month (1–12)
# │ │ │ │ ┌───── day of week (0–6, Sunday = 0)
# │ │ │ │ │
# * * * * *  command
CRON_TZ=UTC
0 0 * * 1  /path/to/my-job.sh >> /var/log/my-job.log 2>&1
  • CRON_TZ=UTC is honored by cronie (Fedora, RHEL, Arch). Other cron daemons ignore it and use the server's time zone, so check timedatectl first.
  • Edit with crontab -e. Cron starts the next run even if the last one is still going; wrap the command in flock -n /tmp/my-job.lock to prevent overlaps.

Need scheduled jobs, queues and monitoring that never miss a run? Talk to our team

Quick answer

The cron expression for every Monday is 0 0 * * 1. The 1 in the day-of-week field is Monday, and 0 0 sets the time to 00:00, so the job runs once a week as Monday begins. Change the first two fields to pick another time, such as 0 9 * * 1 for 9 AM on Mondays, and leave the day-of-month and month fields as asterisks.

  • Live next runs
  • Any time zone
  • Field-by-field breakdown
  • Seven platform snippets
  • Daylight saving aware

How to use this schedule

  1. 1Copy 0 0 * * 1 with the Copy expression button.
  2. 2Check Next runs in your time zone to confirm it fires when you expect, including around daylight saving changes.
  3. 3Pick your platform under Use it on your platform and copy the ready-made crontab line, workflow, manifest or timer.
  4. 4Need a different time or day? Click Customize to open it in the cron expression generator and change any field.

What is a Monday cron job good for?

Monday is the natural start of the working week, so a Monday schedule is where weekly housekeeping lives: resetting weekly quotas, generating last week's analytics, rotating an on-call roster or archiving the previous week's logs. Running at 0 0 means the previous week (Monday through Sunday) is complete when the job starts, as long as the job works out "last week" from the run date rather than from the current time minus seven days.

If the output is for people rather than for other systems, an hour like 0 8 * * 1 delivers a fresh report at the start of the day instead of at midnight, when nobody reads it and the job competes with every other nightly task.

How is Monday written in cron and in other schedulers?

In crontab, Monday is 1 or MON in any letter case. Day numbering is where tools disagree, so check before you copy an expression across:

SchedulerMondaySunday
crontab (Vixie cron, cronie)10 or 7
Kubernetes, GitHub Actions10
AWS EventBridge, Quartz21
Cloudflare Workers21
systemd OnCalendarMonSun

Where names are supported, MON means Monday everywhere, which makes names the safest way to share a weekly schedule between tools that number days differently.

What does each field in 0 0 * * 1 mean?

FieldValueAllowedMeaning
Minute00–59at minute 0 (on the hour)
Hour00–23at hour 0 (midnight)
Day of month*1–31every day of the month
Month*1–12, JAN–DECevery month
Day of week10–7 (0 and 7 are Sunday), SUN–SATonly on Monday

Read together: At 00:00 every Monday, once a week.

How do I adjust 0 0 * * 1 to my own schedule?

Small edits to 0 0 * * 1 cover most real-world needs:

ExpressionWhat it does
0 9 * * 1Mondays at 9 AM
30 6 * * 1Mondays at 06:30, before the working day starts
0 0 * * MONThe same schedule written with the day name
0 0 * * 1,4Mondays and Thursdays at midnight
0 0 * * 2-5Tuesday through Friday, the rest of the working week

Need something else? Click Customize at the top of the page to open this schedule in the cron expression generator and change any field.

Related schedules: Every week · Every Sunday · Every weekday · First Monday of the month

Browse all schedules in the cron schedule library.

How do I run 0 0 * * 1 in crontab, GitHub Actions, Kubernetes and the cloud?

PlatformWrite it asTime zone
Linux crontab0 0 * * 1Server's time zone; CRON_TZ= in cronie
GitHub Actions- cron: "0 0 * * 1"UTC by default; add timezone: (IANA name)
Kubernetes CronJobschedule: "0 0 * * 1"Set timeZone: (1.27+)
Cloudflare Workers0 0 * * MONUTC only; numbers weekdays from 1 = Sunday, so use names
Vercel Cron Jobs0 0 * * 1UTC only; Hobby runs it within the hour (±59 min)
AWS EventBridge Schedulercron(0 0 ? * MON *)Takes a time zone; legacy scheduled rules are UTC only
systemd timerOnCalendar=Mon *-*-* 00:00:00Add a zone after the time, e.g. Europe/London

In a crontab (crontab -e), the full line looks like this:

0 0 * * 1  /path/to/job.sh >> /var/log/job.log 2>&1

The live panel at the top of the page builds complete, copy-ready files for each platform (workflow, CronJob manifest, wrangler.toml, vercel.json, AWS CLI and systemd units) and can shift the schedule to UTC for platforms that need it.

What can go wrong with 0 0 * * 1?

  • A Monday 00:00 run on a UTC server happens on Sunday evening in the Americas. If the job's idea of "this week" depends on local dates, compute them in the right time zone.
  • There is no first-Monday-of-the-month in standard cron. 0 0 1-7 * 1 looks right but runs on days 1–7 and on every Monday, because the two day fields are combined with OR. See first Monday of the month for the fix.
  • AWS EventBridge and Cloudflare Workers number Monday as 2. Copying the 1 from 0 0 * * 1 into either of them schedules Sunday.
  • Weekly jobs are easy to forget when they fail. Alert on failure, because the next chance to notice is seven days away.
  • On UTC-only platforms (Cloudflare Workers, Vercel, legacy EventBridge rules), the local time this runs at moves by an hour when daylight saving time starts or ends. Use GitHub's timezone:, Kubernetes timeZone, EventBridge Scheduler or cronie's CRON_TZ to pin it to local time.

Frequently asked questions

0 0 * * 1 runs at 00:00 every Monday. Use 0 9 * * 1 for 9 AM, or any other minute and hour in the first two fields.
Monday is 1. Sunday is 0, and Vixie cron and cronie also accept 7 for Sunday. AWS EventBridge, Quartz and Cloudflare Workers are different: they count Sunday as 1 and Monday as 2.
Standard cron can't express it directly, because 0 0 1-7 * 1 means days 1 to 7 or any Monday. Schedule 0 0 1-7 * * and have the job exit unless the day of the week is Monday.
Yes, list the days: 0 0 * * 1,4 runs at midnight on Mondays and Thursdays.

Last updated by the Playxoft engineering team.

From the engineers who built this tool

Need scheduled jobs that never miss a run?

Cron is the easy part. Retries, overlapping runs, time zones, queues and alerts when a job silently stops are where schedules break. We build background job systems you can trust, and we will review your setup for free.

Get a free job-scheduling reviewSee backend services

More free tools

See all tools

Regex Tester

Test regex live with highlighted matches, plain-English explanations and code export.

Open tool

Cron Expression Generator

New

Build and explain cron schedules, see the next runs in any time zone, copy platform snippets.

Open tool

SQL Formatter

Beautify or minify SQL in 12 dialects, with keyword case, indent and line:column errors.

Open tool

cURL to Python Converter

New

Convert cURL commands into Python requests or httpx code with params, json, files and auth.

Open tool

cURL to Fetch Converter

New

Turn any cURL command into JavaScript fetch() code with headers, JSON, forms and auth.

Open tool

cURL to Axios Converter

New

Convert cURL commands into an Axios request config with params, data, auth and timeouts.

Open tool